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 |
---|---|---|
.tx | Loading commit data... | |
cms | Loading commit data... | |
common | Loading commit data... | |
conf/locale | Loading commit data... | |
docs | Loading commit data... | |
lms | Loading commit data... | |
openedx | Loading commit data... | |
pavelib | Loading commit data... | |
requirements | Loading commit data... | |
scripts | Loading commit data... | |
test_root | Loading commit data... | |
vendor_extra/tinymce | Loading commit data... | |
.gitattributes | Loading commit data... | |
.gitignore | Loading commit data... | |
.jshintrc | Loading commit data... | |
.ruby-gemset | Loading commit data... | |
.ruby-version | Loading commit data... | |
AUTHORS | Loading commit data... | |
CHANGELOG.rst | Loading commit data... | |
CONTRIBUTING.rst | Loading commit data... | |
Gemfile | Loading commit data... | |
Gemfile.lock | Loading commit data... | |
LICENSE | Loading commit data... | |
README.rst | Loading commit data... | |
manage.py | Loading commit data... | |
package.json | Loading commit data... | |
pavement.py | Loading commit data... | |
pylintrc | Loading commit data... | |
pylintrc_tweaks | Loading commit data... | |
setup.cfg | Loading commit data... | |
setup.py | Loading commit data... |