You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing that would make life easier in my situation would be to be able to set the equivalent of QUnit.module("some-module-name") as a commandline arg, e.g.
qunit -t mytest.js -m mytest
where -m <somename> sets the module name
Anyway, thanks for a great lib and let me know if I'm missing anything obvious.
The text was updated successfully, but these errors were encountered:
Well, there are a lot of strategies for structuring files, it depends on the architecture of a product, I don't want to force someone using one of them, therefor one will need either to write a files finder or reference them manually in some config file. It is possible to make this less ugly f.e. by using node-qunit js api directly without cli. Write your own bin/testrunner.js script and pass the files from there. Also you can use some high level nodejs modules to find your files.
Why do you want to set the module name from outside of the module. Normally your module should know its name or it will be auto detected using file name.
Hi, I find this library very useful for running javascript unit tests. However, I had to do some ugly stuff to get it working for my situation:
To run all tests in specific directory against corresponding JS files:
https://github.com/frontlinesms/frontlinesms2/blob/master/plugins/frontlinesms-core/do/js_unit_test
To parse output of node-qunit and convert it to JUnit XML reports (for use with Jenkins):
https://github.com/frontlinesms/frontlinesms2/blob/master/plugins/frontlinesms-core/do/js_unit_test_xml
One thing that would make life easier in my situation would be to be able to set the equivalent of
QUnit.module("some-module-name")
as a commandline arg, e.g.where
-m <somename>
sets the module nameAnyway, thanks for a great lib and let me know if I'm missing anything obvious.
The text was updated successfully, but these errors were encountered: