I try to build an run through various Qunit-tests in various pages
generated by a CMS..
After a page with its unit-tests worked out, the browser should load via
AJAX the next testpage with other Qunit-Tests.
I choose that way of testing, because I can develop the tests in small
portions for special situations.
I missed the documentation of QUit.load(), because I need that function
to restart the Unittest after loading a new Page with new tests.
I used the following sequence to restart the QUnit-tests after
AJAX-loading of the next test-part and its Unittests.
None of those methods are supported anymore, both "init" and
"load" never were. The setup you describe is at best a neat
hack. I highly recommend restructing your setup to use multiple modules
within a single file, or multiple separate files for each module. For
the latter, you can use qunit-composite to still run them all at once: https://github.com/jquery/qunit-composite
Thanks for the tipandthe link. Yourproposalis certainlyideal formany test
cases. But your proposal with iframs comesto their limits in some cases.. I want to makesure
runningreliablyafter the update.Further, theCMSgeneratessome individual
only solution for this test-scene. At the moment,the
hackworks and QUnitis definitelya really goodframework. A Plugin for QUnit would be ideal, which supports
sequential testing on several pages in test series. Or I have to
look for an other testing-framework.
Leave a comment on info111193030308's reply
Change topic type
Link this topic
Provide the permalink of a topic that is related to this topic