[...]
+ python manage.py test lists
.................................
---------------------------------------------------------------------
Ran 33 tests in 0.229s
OK
Creating test database for alias 'default'...
Destroying test database for alias 'default'...
+ python manage.py test accounts
..................
---------------------------------------------------------------------
Ran 18 tests in 0.078s
OK
Creating test database for alias 'default'...
Destroying test database for alias 'default'...
[workspace] $ /bin/sh -xe /tmp/hudson2967478575201471277.sh
+ phantomjs superlists/static/tests/runner.js lists/static/tests/tests.html
Took 32ms to run 2 tests. 2 passed, 0 failed.
+ phantomjs superlists/static/tests/runner.js accounts/static/tests/tests.html
Took 47ms to run 11 tests. 11 passed, 0 failed.
[workspace] $ /bin/sh -xe /tmp/shiningpanda7526089957247195819.sh
+ pip install selenium
Requirement already satisfied (use --upgrade to upgrade): selenium in /var/lib/
Cleaning up...
[workspace] $ /bin/sh -xe /tmp/shiningpanda2420240268202055029.sh
+ python manage.py test functional_tests
.......
---------------------------------------------------------------------
Ran 7 tests in 76.804s
OK
Nice to know that, no matter how lazy I get about running the full test suite on my own
machine, the CI server will catch me. Another one of the Testing Goat’s agents in cy‐
berspace, watching over us…
More Things to Do with a CI Server
I’ve only scratched the surface of what you can do with Jenkins and CI servers. For
example, you can make it much smarter about how it monitors your repo for new
commits.
Perhaps more interestingly, you can use your CI server to automate your staging tests
as well as your normal functional tests. If all the FTs pass, you can add a build step that
384
|
Chapter 20: Continuous Integration (CI)