Name |
Last commit
|
Last update |
---|---|---|
.. | ||
paver_tests | ||
utils | ||
__init__.py | ||
acceptance_test.py | ||
assets.py | ||
bok_choy.py | ||
docs.py | ||
i18n.py | ||
js_test.py | ||
prereqs.py | ||
quality.py | ||
servers.py | ||
tests.py |
This would allow a user to set up and run servers, with an open prompt for killing them. Likewise a user could open a different terminal session and run tests only. How-to: * At a terminal/ssh session, start bok-choy servers with `paver test_bokchoy --serversonly` (or, if you've already run collectstatic on your system: `paver test_bokchoy --serversonly --fasttest`) * When the above is running, you can now open a separate terminal/ssh session and run: `paver test_bokchoy -t my_tests --testsonly` Keep in mind, the 'testsonly' flag does no setup. There is some minimal teardown; however, such as clearing mongo and flushing the lms database. (Some tests have non-unique identifiers and could not be run more than once.)
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
paver_tests | Loading commit data... | |
utils | Loading commit data... | |
__init__.py | Loading commit data... | |
acceptance_test.py | Loading commit data... | |
assets.py | Loading commit data... | |
bok_choy.py | Loading commit data... | |
docs.py | Loading commit data... | |
i18n.py | Loading commit data... | |
js_test.py | Loading commit data... | |
prereqs.py | Loading commit data... | |
quality.py | Loading commit data... | |
servers.py | Loading commit data... | |
tests.py | Loading commit data... |