QUnit and Sinon.js under continous integration -


i using qunit+sinon.js works natively. problem occured when tried build continous integration process. using js-test-driver framework able run in continous integration enviroment. in past used without sinon.js , wasn't problem that. after included sinon.js plugin, doesn't work @ all. when tried run tests says: 

d:/my/project/url/contenttest.js:60: typeerror: qtest not function total 0 tests (passed: 0 fails: 0 errors: 0)(0.00 ms)

my js-test-driver configuration:

server: http://localhost:9879  load:     # qunit related files   - qunit/lib/equiv.js   - qunit/lib/qunitadapter.js   - qunit/plugin/sinon-1.6.0.js   - qunit/plugin/sinon-qunit-1.0.0.js    # dependencies   - external/jquery/1.7.2/jquery.min.js    # files under test   - content.js    # tests   - contenttest.js

the interesting thing there qunit index.html file works (when open html, every tests passes):

<!doctype html> <html> <head>   <meta charset="utf-8">   <title>my tests</title>   <link rel="stylesheet" href="./qunit/lib/qunit-1.11.0.css"> </head> <body>   <div id="qunit"></div>   <div id="qunit-fixture"></div>    <!-- core -->   <script src="./qunit/lib/qunit-1.11.0.js"></script>   <script src="./qunit/plugin/sinon-1.6.0.js"></script>   <script src="./qunit/plugin/sinon-qunit-1.0.0.js"></script>    <!-- dependencies -->     <script src="./external/jquery/1.7.2/jquery.min.js"></script>    <!-- under test  -->   <script src="./content.js"></script>    <!-- tests -->   <script src="./contenttest.js"></script> </body> </html>

so seems there conflict js-test-driver , sinon.js. if remove related sinon.js tests , included sinon plugins, works. if remove sinon related tests, still failes. if don't remove sinon.js remove tests , create emty test "ok(true)" assert, still fails same error message (contenttest.js:60: typeerror: qtest not function), test file consists 10 row (how error in 60.th line when file consists 10 line?).

thank helps in advance!

not solution, perhaps approach more information: can run js-test-driver scripts locally shell? produce similar error details? @ least, give more information , shorter feedback loop.


Comments

Post a Comment