I have a project for which I write unit tests and then run them with code coverage report.
The setup on the Windows 10 machine is: PHP 7.0.2, xDebug 2.4.1, PhpUnit 5.6.1, Code coverage 4.0.1. Everything works fine, code coverage show relevant results.
Then I've cloned the same project on Mac Book with MacOs Sierra installed. Firstly I run the project on PHP 7.0.12, all other versions are the same. And as a result code coverage failed - it showed 0 in all categories.
I thought, that xDebug 2.4.1 and Php 7.0.12 are incompatible, that's why I've switched to code coverage with PhpDbg instead. With no luck unfortunately.
At last, I managed to get an old (7.0.2) PHP version through homebrew-php repository and installed it. So I got PHP 7.0.2, xDebug 2.4.1, PhpUnit 5.6.1, Code coverage 4.0.1 on MacOs Sierra. I ran the tests and got 0 in code coverage again.
So, I have completely the same setup with one difference - host OS. Can MacOs be the reason of failing code coverage? Maybe, I've missed anything else?
Related
Using: VS Code
Working on: Running automation test scripts for WebdriverIO.
Error facing:
because of this error, my test specs are not executing. Is there any way to get rid of this??
Please follow the below steps to resolve this issue
Uninstall the current version of node.js.
Go to https://nodejs.org/en/blog/release/
Install the previous version of node.js (I installed from here 4.
https://nodejs.org/dist/v14.17.3/node-v14.17.3-x64.msi)
Restart your system
Try building the project using npm install
I hope this will solve your problem
The error here is coming from the Fibers npm package. Fibers only supports node versions before version 16. I had the same error message and switched the node version to 14.20.0 ,which is the newest LTS before version before 16 at the moment, and that solved the problem for me.
I am setting up Browser Test with Laravel 5.7. Install Laravel Dusk. My very beginning php artisan dusk command return errors
My Chrome is version 76. Initially, I see "Chrome version must be between 70 and 73". So I download Chrome Driver for my corresponding browser version. Then Run the command again, and I see a new error Facebook\WebDriver\Exception\UnrecognizedExceptionException: invalid argument
I didn't change any code after running initial php artisan dusk:install
Make sure host and Dusk are using the same Chromium driver:
# linux box
chromium-browser --version
# install specific version on dusk
php artisan dusk:chrome-driver 78
I was running dusk through homebrew and I found that I needed to reload vagrant as well:
vagrant reload --provision
I've found some interesting Issues on Github that should be your problem.
https://github.com/laravel/dusk/issues/651
I think that is a problem with the Driver. Perhaps you can find a solutions and check some of the mentioned problems in that issue to find your problem. It's bit difficult to help you without having the code and having the same problem to test.
Some of them have reinstalled dusk and it was working. So you can test do install the newest driver first and then install the dusk package after that.
I have the latest PhpStorm (2016.2) and PHPUnit phar (5.5.4). For some reason when I run a PHPUnit test in my project in PhpStorm, it is adding on --teamcity to the run command, resulting in a failure:
Testing started at 12:52 PM ...
Unit test suite invoked with a path to a non-unit test: --teamcity
Process finished with exit code 1
I have no idea where this --teamcity option is coming from, it happens no matter what test I run, and even when starting from a blank configuration. I also do NOT have the TeamCity plugin installed, I don't even use TeamCity.
Here's what the full command appears as:
/usr/local/Cellar/php70/7.0.9/bin/php /Users/name/bin/phpunit-5.5.4.phar --configuration /path/to/config/my-phpunit.xml ClassNameTest /Users/name/PhpstormProjects/path/to/tests/unit/app/ClassNameTest.php --teamcity
(sensitive information swapped out)
All I want to do is get rid of this --teamcity option, everything works if I run in a separate terminal window without that option. This only recently started happening, maybe after a PhpStorm update.
tl;dr
I only could resolve this by removing the system installed phpunit instance from my system (Linux):
sudo apt remove phpunit-*
Details
Even if the setting in PhpStorm was to use composer autoloader:
for some reason it ended up using TeamCity from /usr/share/php/PHPUnit/Util/Log/TeamCity.php:
Project's local PHPUnit was 6.2 while the system default was 5.1 -> they're incompatible.
I spent half a day struggling with this. The underlying issue is switching between PHPUnit versions (6.x.x -> 4.x.x). (Happened to me by switching branches)
A click on the refresh button in the PHPUnit preferences fixes it.
(Languages & Frameworks > PHP > PHPUnit)
Make sure the version of PHPUnit it thinks you have matches the one it reports.
This --teamcity option is used by PHPStorm to output tests result.
What you're facing is an issue caused by PHP7 and an old version of PHPUnit.
Remove your PHPUnit 5 and install the latest one (currently 6.2) with composer and use PHPUnit namespaces instead.
More info on this bug: https://github.com/sebastianbergmann/phpunit/issues/2460
Problem was internal to the project. PHPUnit does not contain that error message. Sorry!
I cannot run NCover. I get the error:
NCover couldn't create a coverage report
I'm running it via TestDriven.net. I am using MSTest and also have resharper 4.2 installed. There isnt a problem with the tests, as it works on collegues machines. Any ideas what the problem is?
Do you have an old version of NCover installed? If you do, could you try uninstalling it. Could you also let me know which version you had installed.
I'm trying to install Qt-4.6.0-wince on XP and Vista. I read the instructions and follow it to install.
However, I can't install it successfully due to some fatal errors on all of the two machines. I think the problem is that qconfig.[h cpp] files are not created automatically during the configuration.
I already report about this problem, so you can see the more information here. However, it is still remained as unresolved.
Anybody here who has been installed it successfully?
#KernelJ I believe the original poster is using the correct install distro - the final product will be cross compiled from Win32 to WinCE; as is pointed out in the Qt for Windows CE Requirements.
#Brian, Unfortunately, I can't answer your original question - I have had unrelated trouble with the WinCE distribution myself and am working the issues now. However, I can provide some help: I was able to get the Qt Everywhere 4.6 to cross compile on my Win32 (XP) host for WinCE. I used the commercial version, but here is a link to the Open Source Qt Everywhere 4.6 package. As is pointed out in the nokia instructions, make sure to use the Visual Studio command prompt, get your environment variables ironed out, create a custom mkspec (if you have to), and keep a close eye during the configuration for any warnings.
Good luck.
Qt-4.6.0-wince, as is implied in the name and said explictly on the page you linked, is for Windows CE, NOT for Windows XP and Vista!!!
Nokia have released a nice software development kit for Qt which you can download here. It is very impressive and powerful!
I got things running as compilable (and running on emulator) with VS 2008, so your milage may vary:
Make sure the PATH variable points to \bin
Open a command prompt (using the Visual Studio Command Prompt)
Run the vcvars32.bat file (in C:\Program Files\Microsoft Visual Studio 9\VC\bin) folder
Cd into the qt folder
Run this: configure -no-sql-sqlite -no-qt3support -platform win32-msvc2008 –xplatform wincewm50pocket-msvc2008 -no-phonon -no-phonon-backend -no-webkit (building for WINCE 5.0, and all the '-no-...' makes it build faster, removing stuff we don’t want)
The setccepaths script provided sometimes doesn’t work. I used checksdk.exe –script temp_script.bat (It creates a script, the default is for Pocket PC SDK 5)
Run that script you just created (the temp_script.bat thing. It sets up environment variables.
Run nmake
*whew*
and good luck.