I am trying to use netbeans (7.2.1) for unit testing. But it is giving me this error. anyone can tell me what is wrong in it?
PHPUnit 3.7.14 by Sebastian Bergmann. unrecognized option --skeleton-test
I stumbled upon this problem too. It's solved in NetBeans 7.3, but if you are still using 7.2, here is the solution:
Install phpunit-skelgen as mentioned in the other answers. If you are using pear: sudo /opt/lampp/bin/pear install phpunit/PHPUnit_SkeletonGenerator
In NetBeans, open the unit testing options: Tools > Options > PHP > Unit Testing
Click on the Search button for the skeleton generator field (or you can just browse of course)
That solved it for me.
This issue is documented in the NetBeans issue tracker right here: http://netbeans.org/bugzilla/show_bug.cgi?id=218675
The newer PHPUnit does not use the --skeleton-test option. You call an external script, phpunit-skelgen to do the same thing.
Verify that the phpunit-skelgen file exists in the same directory as the phpunit binary (eg. /opt/lampp/bin/).
If not, install the PHPUnit SkeletonGenerator the same way you installed PHPUnit, eg. from PEAR:
$ sudo /opt/lampp/bin/pear install phpunit/PHPUnit_SkeletonGenerator
Related
I am trying to include sqlite3 in an electron project I am getting my hands dirty with. I have never used electron, nor Node before, excuse my ignorance. I understand that to do this on Windows, I need Python installed, I need to download sqlite3, and I need to install it.
As per the NPM sqlite3 page, I am trying to install it using npm install --build-from-source
It always fails with
unpack_sqlite_dep
'python' is not recognized as an internal or external command,
operable program or batch file.
I have Python 2.7 installed and the path has been added to environment variable PATH. I can verify that if I type 'python' in cmd, I get the same response. BUT, if I type 'py', it works....
So, my question is: how can I make node-gyp use the 'py' command instead of 'python' when trying to unpack sqlite3?
If this is not possible, how can I make 'python' an acceptable command to use?
I am using Windows 10 if this helps. Also, please let me know if I can do this whole procedure in a different way.
Thanks for any help!
This has been resolved....
Uninstalled Python 2.7.13. Reinstalled, added path to PATH variable again, now command 'python' works just fine...
I've got a very small and simple github project which I would like to integrate with travis-ci.org (.travis.yml file). Unfortunately, compilation fails (travis console log), the compiler cannot find cppunit even though I run sudo apt-get ... to install it.
The test/list_test.h file has got the following line:
#include <cppunit/TestFixture.h>
As I said, travis compiler cannot find cppunit headers. Can anyone point me out what am I doing wrong?
CMake was OK. Travis Script was also OK. But the cppunit package was mistaken. It should be libcppunit-dev instead of libcppunit-1.12-1
i installed jetty (distribution-9.0.2) on ubuntu server 12.04
from these links step by step
http://degreesofzero.com/article/19
http://pietervogelaar.nl/ubuntu-12-04-install-jetty-9/
at last when i start jetty with the following command:
sudo /etc/init.d/jetty start
or
sudo service jetty start
i get the following error
Starting Jetty: grep: /var/run/jetty.state: No such file or directory
I'm facing with the same problem but on Debian 6 server. Workaround for this problem and articles above, from my perspective, is:
use JETTY_ARGS=jetty.port=8080 instead JETTY_PORT
Add property to /etc/init.d/jetty: JETTY_PID=/opt/jetty/jetty.state
Please, let me know if you have any questions
I've tested this thoroughly with the latest release of jetty and it's working fine. There's been some changes recently in the jetty.sh script. However the changes look good to me and it's working fine for me with the latest release.
Evgenly is right, that JETTY_PORT is deprecated (see comments in jetty.sh for details), however it also works fine for me using JETTY_PORT instead of JETTY_ARGS to define a non standard port.
Please try the latest release from here in case you didn't do already:
http://download.eclipse.org/jetty/
If jetty.sh reports that the start failed, you'll usually find the reason in stderrout.log inside the JETTY_HOME/logs directory (unless you've changed the logging config).
I'm trying to run yeoman build on a project that uses requireJS and the require-handlebars-plugin. I'm am getting this error when running the rjs task:
<WARN> Error: ENOENT, no such file or directory '/Users/tkrell/Sites/pathrabbit-marionette-require/temp/scripts/template/schedules/day-jobs -past.js'
In module tree:
main
schedules/schedule-layouts
schedules/schedule-jobs-view
hbs
at Object.fs.openSync (fs.js:338:18)
Use --force to continue. </WARN>
I believe this is the same as this issue which appears to simply need the latest version of r.js to be resolved. When I use a newer version of r.js manually, I don't get the error and everything works fine. How can I force the yeoman build task to use the latest version r.js?
The advice given on the issue I created on Yeoman's github page worked for me:
Yeoman uses 2.0.2 (see it's package.json).
You could go into the directory yeoman is installed and run npm install -f requirejs to force install a newer version. No promises it won't break though.
However, in yeoman 1.0 (which is imminent), we'll be using grunt-requirejs instead.
I am trying to run Fix8 at Fix8.org. I am following the README instructions as explained at:
https://github.com/dakka/fix8
I am getting an error when running the ./configure command? It results in:
configure: error: cannot find install-sh, install.sh, or shtool in "." "./.." "./../.."
Does anyone have experience in fixing this? I m running both latest versions of Debian and Ubuntu Linux.
Thanks
The files mentioned in the error are placed in the source directory by autoconf and should be distributed in the release tarball. If they are not it's a bug, so please report it to the author.
If you have autoconf installed, you can get the files by running ./bootstrap (or whatever script it has; the usual name is ./autogen.sh), but you are not supposed to need autoconf to run configure script.
Yeah sorry about that - you need libtool. I have supplied configure - as this was missing. Check the FAQ. If you have any more problems please email on the support group.