Testing Django with Travis CI

A talk I gave on testing Django and using Travis CI for Pycon Canada

Transcript

1. TESTING DJANGO WITH TRAVIS CI 1 Sunday, November 11, 12
2. • Python Developer at • Twitter: @adammckerlie • Everywhere else: silent1mezzo ABOUT ME 2 Sunday, November 11, 12
3. SLIDES bit.ly/UhvbjV 3 Sunday, November 11, 12
4. • Definitions • Why you should test your code • What parts of your code you should test • Writing your first test • Integrating Travis CI to automatically run your tests OVERVIEW 4 Sunday, November 11, 12
5. UNIT TEST • Tests one small section of code • Focuses your code • Fast 5 Sunday, November 11, 12
6. INTEGRATION TEST • Tests that the whole system works (views, forms, etc...) • Slow • Gives you a full picture of what’s happening 6 Sunday, November 11, 12
7. • Gives you confidence in your code • Allows you to iterate faster • Provides beginners an easy spot to code-dive • Untested code is expensive WHY YOU SHOULD WRITE TESTS 7 Sunday, November 11, 12
8. “CODE NOT TESTED IS BROKEN BY DESIGN” JACOB KAPLAN-MOSS 8 Sunday, November 11, 12
9. • Don’t test Django or Python’s built-in stuff • Test your views, models, forms, management commands, etc... WHAT YOU SHOULD TEST 9 Sunday, November 11, 12
10. • Tests can go in models.py or tests.py • Must subclass django.test.TestCase • python manage.py test <app_name> WRITING YOUR FIRST TEST 10 Sunday, November 11, 12
11. • Every view should have this test 11 Sunday, November 11, 12
12. • Fixtures are serialized data that you can load. • python manage.py dumpdata app_name > app_name/fixtures/file.json USING FIXTURES 12 Sunday, November 11, 12
13. 13 Sunday, November 11, 12
14. • After every commit • Before you merge your branches into master • Once you’ve deployed your code WHEN SHOULD YOU TEST 14 Sunday, November 11, 12
15. WHAT IS TRAVIS-CI? • Continuous Integration Testing • Open Source • https://github.com/travis-ci 15 Sunday, November 11, 12
16. + = 16 Sunday, November 11, 12
17. HOW DOES IT WORK? • Sign up with your github account • Specify repositories • Include a .travis.yml file • Change/commit/push code • Tests run automagically 17 Sunday, November 11, 12
18. 18 Sunday, November 11, 12
19. .travis.yml 19 Sunday, November 11, 12
20. Environment Variables 20 Sunday, November 11, 12
21. Using Databases 21 Sunday, November 11, 12
22. PULL REQUESTS • Test Pull Requests before they’re merged to master • Notifications of running tests • Notifications of successful tests 22 Sunday, November 11, 12
23. 23 Sunday, November 11, 12
24. 24 Sunday, November 11, 12
25. before/after_script 25 Sunday, November 11, 12
26. NOTIFICATIONS 26 Sunday, November 11, 12
27. Email Notifications 27 Sunday, November 11, 12
28. IRC Notifications 28 Sunday, November 11, 12
29. Webhook Notifications 29 Sunday, November 11, 12
30. FINAL TIPS • [ci skip] • https://secure.travis-ci.org/[YOUR_GITHUB_USERNAME]/ [YOUR_PROJECT_NAME].png • travis-lint 30 Sunday, November 11, 12
31. QUESTIONS? 31 Sunday, November 11, 12