I have installed, via Composer, the latest versions of PHPUnit and the Skeleton Generator, 4.1.3 and 2.0.1, respectively. I have installed it to my project directory and confirmed that I can test all files. I cannot, however, run the skeleton generator to create new tests. I am using Netbeans and its PHPUnit integration to create the tests. When I attempt to generate the tests, I get the following:
"C:\xampp\php\php.exe" "C:\Users\Bob\Projects\[myProject]\website\vendor\phpunit\phpunit-skeleton-generator\phpunit-skelgen" "--test" "--" "Security\SecureAPI" "C:\Users\Bob\Projects\[myProject]\website\src\Security\SecureAPI.php" "Security\SecureAPITest" "C:\Users\Bob\Projects\[myProject]\website\test\phpunit\src\Security\SecureAPITest.php"
phpunit-skelgen 2.0.1 by Sebastian Bergmann.
[InvalidArgumentException]
Command "Security\SecureAPI" is not defined.
Done.
I had the Netbeans 'Use Bootstrap for Creating New Unit Tests' option selected prior to this, and got this error:
"C:\xampp\php\php.exe" "C:\Users\Bob\Projects\[myProject]\website\vendor\phpunit\phpunit-skeleton-generator\phpunit-skelgen" "--bootstrap" "C:\Users\Bob\Projects\[myProject]\website\test\phpunit\bootstrap.php" "--test" ...
[InvalidArgumentException]
There are no commands defined in the "C" namespace.
Generating tests with version 1.2.1 worked fine on my old development machine. I'm wondering if the issues are specific to version 2.0.1 of the skelgen. It seems to be viewing the C: as a namespace, whereas 1.2.1 did not. I've confirmed that Netbeans produced identical command line instructions for 1.2.1 and 2.0.1, so it appears that the way they are being interpreted has changed.
Has anyone else seen this? Any ideas? I'm running a Win7 machine with Netbeans 8.0. Thanks in advance.
Try to download Dev build of NetBeans from here, the issue with changes in Skeleton Generator 2.x was fixed few days ago
Related
Context:
I am following the guide for the open source project OpenSC https://github.com/OpenSC/OpenSC to compile the solution on Windows and get the opensc-pkcs11.dll module to use it for communications (such as OpenSSH) with HSM's via PKCS#11 standard. Currently I am using the latest stable release 0.21.0 (msi installer) and it works perfectly. However when I use https://github.com/OpenSC/OpenSC/wiki/Compiling-on-Windows guide to compile the solution using Visual Studio Developer Command Prompt I can successfully build the libraries however the opensc-pkcs11.dll always returns pkcs11: 0x5: CKR_GENERAL_ERROR when I try to use it and I am not sure what am I missing here.
Setup:
git clone https://github.com/OpenSC/OpenSC.git
git checkout 30180986a08cf71fe4af4b50251a8bb5b1ab95af (0.21.0 commit for the right version)
Manually Creating Built Source Files
nmake /f Makefile.mak
Building it for x64, with x64 Native Tools Command Prompt for VS 2019.
That should be it according to the guidelines as I do not need openpace/openssl/zlib to compile the opensc-pkcs11 as far as I understand.
Problem summary:
If I download from releases https://github.com/OpenSC/OpenSC/releases version OpenSC-0.21.0 the compiled opensc-pkcs11.dll works as expected
If I compile it from source code based on v0.21.0 commit I get 0x5: CKR_GENERAL_ERROR when trying to use the library for e.g. OpenSSH, tested that this happens for other/previous commits as well, there for I suspect that I am missing something here.
Has anyone experienced the same issue? Maybe there is some build config anyone could share so I can understand what am I missing here?
Having configured NUnit step using a bundled NUnit tool like that:
I am having difficulties with following message appearing at the beginning of the log once step is executed:
The TeamCity NUnit runner requires the following NUnit extensions to be installed: NUnit.Engine.Listeners.TeamCityEventListener, NUnit.Engine.Services.ProjectLoaders.NUnitProjectLoader. Please follow our instructions at: https://confluence.jetbrains.com/display/TCDL/NUnit#NUnit-NUnit3Extensions
The tests are running fine, as well as dotCover coverage. But, the process itself ends with a -100 exitcode, causing whole step to be failed. I checked if the extensions on TeamCity agent are installed along with the bundle and it looks like they're - dlls are in the addins folder. Running nunit3-console with --list-extensions also displays that extensions are installed.
I also tried to install NUnit.Console bundle NuGet package (and making sure that extensions are installed as well) and run it with specified nunit console executable path, but no luck - the error message was the same. As before, running nunit3-console from command line results in installed extesions.
Unfortunately, I don't know what's the logic behind that check and I don't know how to reproduce it. I assume that there's some mismatch, because the plugins are clearly running as TeamCity recognizes the results and put them on the interface.
TeamCity version: 2018.1.2 Enterprise (build 58537)
NUnit Version: 3.9.0 (bundled)
This was a bug, which is fixed in TeamCity 2018.1.3. See https://github.com/nunit/nunit-console/issues/468
Summary: TeamCity was reading the console output of --list-extensions to determine which extensions were installed. The format of this output changed in the NUnit 3.9 Console, which broke the TeamCity parsing.
Afraid I'm not sure if there's a workaround - I'm not a TeamCity user myself.
I´m trying to build paraview from source, therefore using:
Windows 7
Visual Studio 2010
Qt 4.8.7
Python 2.7.8
msmpi 7
paraview source, version 5.1.0
In CMake I can choose different options to specify what functionality to include into the build process. I tried different combinations, like setting BUILD_EXAMPLES or PARAVIEW_USE_MPI, respectively. Now I have got following questions:
When I set BUILD_SHARED_LIBS and PARAVIEW_ENABLE_PYTHON as well (besides others), configuring and generating the project with CMake is successful, but compiling in VS fails; it keeps freezing right after starting the compilation. Did anybody experience the same problem and how did you solve it? (By the way, if I unset BUILD_SHARED_LIBS it works, but I don´t want a static build of Paraview).
By using the combination BUILD_EXAMPLES, BUILD_TESTING, PARAVIEW_BUILD_QT_GUI, PARAVIEW_ENABLE_CATALYST, PARAVIEW_ENABLE_PYTHON and PARAVIEW_USE_MPI the same problem as described in 1.) occurs, but that is more or less what I need to use Catalyst to perform in-situ analysis of my FEM simulation. (Incidentally, if I unset BUILD_TESTING in the above combination it works, but I need CTest to test the Catalyst examples as described here. Does anybody now how to fix that problem?
As shown at GitHub, some examples have been updated to work properly in Paraview 4.4. Is my version of Paraview (5.1.0) unsuitable for the Catalyst examples? Is that the reason why VS is always hanging up for particular variable settings in CMake and which version of Paraview is most suitable to get the Catalyst examples going?
I'd appreciate any help!
That's odd! There's no known reason for this. Although I haven't used VS2010 explicitly, we do have dashboards testing with 2013 and I build with VS2015 with no issue.
I'd recommend using the Ninja as the builder rather than the IDE, however. Just run cmake-gui.exe from appropriate VS studio command prompt and pick Ninja as the build generator. Then, to build, just run ninja in the build directory.
I have been trying to run simple PHPUnit tests with Netbeans 7.1 and PHPUnit 3.6.10 on Xampp 1.7.7
I have downloaded PHPUnit using PEAR and when I type the following, I get the output below
C:\xampp\php\PEAR>phpunit --version
PHPUnit 3.6.10 by Sebastian Bergmann.
Netbeans 7.1 is my problem. I have configured the following
Tools -> Options ->PHP (PHP 5 Interpreter) is C:\xampp\php\php.exe
Tools -> Options ->PHP (Unit Testing) C:\xampp\php\phpunit.bat
I keep getting the dreaded
Selected PHPUnit (version ?.?.?) is too old, upgrade it if possible (the minimum version in 3.3.0)
displayed.
Has ANYONE solved this issue?
PS the irony is, it was working at one stage!
Stephan
Yes...
I'm a WAMP guy, so I don't know XAMPP paths, but this is what you need to do:
Your PEAR path is wrongly set to C:\php5\pear. This is the development setting. Wamp/Xampp should have changed it, but they didn't.
The Solution:
Edit every php.ini file, change INCLUDE_PATH to your path where WAMP Server is installed(e.g. C:\WAMP\bin\php\php5\includes).
Now run go-pear.bat, and follow all the instructions. If everything is fine then its OK. You can check it by running http://localhost/phpinfo(). Else if go to Step 3.
Right Click My Computer->Advanced Tab->Environment Variables->Add New User Variable->PHP_PEAR_INCLUDE_PATH->Add new value->The path where PEAR is installed(e.g. C:\WAMP\bin\php\php5\PEAR).
I have just fixed by adding c:\xampp\php into the PATH environment.
Guessing Netbeans, check phpUnit via the cmd:
C:\>phpunit --version
PHPUnit 3.6.11 by Sebastian Bergmann.
We want to add command-line support to Netbeans, as in being able to run any program (using the full path of the current file as the argument) directly from the IDE. The same way you can do it already on Notepad++ with the Run tool.
Apparently there is a plugin called VCS Generic Command-Line Support that offers this functionality, but when we try to install it we get this error message:
Some plugins require Master Filesystem to be installed
The plugin Master Filesystem is
requested in version >= 1.1 but only
2.15.2 was found.
Any ideas?
EDIT
I Did some googling as you got me interested pretty much everything i found was in refernce to NetBeans 5.x or below... Im thinking maybe its not compatible with 6 - but thats just a guess.
Looks like a version incompatability with "Master Filesystem". Maybe they are checking the version improperly or perhaps they really mean it needs to be 1.x >= 1.1. Do you have the newest version of VCS Plugin?
As an aside if Im going to have to chek this out... ive been dying for external tool support like in my beloved Eclipse :-)