On 03/23/2011 03:59 PM, Benjamin Dreux wrote: > I've found the cause of my problem but not a solution. As I've > noticed, the #assert has no effect in the test app. > > If i modify the test job, then my external lib are added two time. > There are called from testrunner.js, and from tests.js. Unfortunalty > with the same path. Unfortunatly testrunner.js and tests.js are not > called from the same page. So i can etheir have one call correct, or > the other. > > Then as Thron7 emtionned it, we can use the > testrunner::source-tests-script or testrunner::build-tests-script. > But if i do so, the script are not added called neither in tests.js > or testrunner.js > > Is there another job that i can use to add my script file to the test > app??
No, the testrunner::* jobs you mention are the right places. The script should only show up in tests.js or tests-source.js, depending on the job you chose, not in testrunner.js. I don't get the sentence "the script are not added called...". Is there no reference to the external script file in the generated code? Or is it not loaded when you run the Testrunner in your browser? Scripts are not "called" anyway ... T. ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
