KEMBAR78
Continuous Integration Testing in Django | PDF
Kevin Harvey, profile picture
Uploaded byKevin Harvey
13,594 views

Continuous Integration Testing in Django

The document outlines a presentation by Kevin Harvey on continuous integration (CI) testing with Django, discussing its significance, practical implementations using Travis and Jenkins, and essential best practices. It emphasizes the importance of running tests frequently to catch bugs early and includes code examples and tool configurations to set up CI environments. Key tools covered include coverage.py for measuring test coverage and various Jenkins configurations to facilitate automated testing workflows.

Downloaded 162 times
1 / 109
2 / 109
3 / 109
4 / 109
5 / 109
6 / 109
7 / 109
8 / 109
9 / 109
10 / 109
11 / 109
12 / 109
13 / 109
14 / 109
15 / 109
16 / 109
17 / 109
18 / 109
19 / 109
20 / 109
21 / 109
22 / 109
23 / 109
24 / 109
25 / 109
26 / 109
27 / 109
28 / 109
29 / 109
30 / 109
31 / 109
32 / 109
33 / 109
34 / 109
35 / 109
36 / 109
37 / 109
38 / 109
39 / 109
40 / 109
41 / 109
42 / 109
43 / 109
44 / 109
45 / 109
46 / 109
47 / 109
48 / 109
49 / 109
50 / 109
51 / 109
52 / 109
53 / 109
54 / 109
55 / 109
56 / 109
57 / 109
58 / 109
59 / 109
60 / 109
61 / 109
62 / 109
63 / 109
64 / 109
65 / 109
66 / 109
67 / 109
68 / 109
69 / 109
70 / 109
71 / 109
72 / 109
73 / 109
74 / 109
75 / 109
76 / 109
77 / 109
78 / 109
79 / 109
80 / 109
81 / 109
82 / 109
83 / 109
84 / 109
85 / 109
86 / 109
87 / 109
88 / 109
89 / 109
90 / 109
91 / 109
92 / 109
93 / 109
94 / 109
95 / 109
96 / 109
97 / 109
98 / 109
99 / 109
100 / 109
101 / 109
102 / 109
103 / 109
104 / 109
105 / 109
106 / 109
107 / 109
108 / 109
109 / 109
Continuous Integration Testing Django Boston Meetup 24 April 2014 Kevin Harvey @kevinharvey kevin@storyandstructure.com
Who is this guy?
Who is this guy? Fast Slow Unit Functional • Chief Technologist at Story+Structure • Djangonaut since 2007 (0.96)
Here’s the best $24 I ever spent.
What are we doing?
Agenda • What is Continuous Integration? • Why use Continuous Integration? • CI in Practice: Travis • Coverage Thresholds with coverage.py • CI in Practice: Jenkins • Best Practices & Further Exploration
What is CI?
Continuous Integration is like having a tireless robot that cleans up after you.
What is CI? 1. Checkout out the latest copy of your code 2. Install the dependencies 3. Run the tests 4. Report the outcome Some server somewhere checks out your code, installs all your dependencies, runs your tests, and let’s you know if it worked or not.
Testing in Django # jmad/tunes/tests/test_views.py from django.test import TestCase class TunesViewTestCase(TestCase): def test_index_view(self): response = self.client.get('/') self.assertEqual(response.status_code, 200) self.assertTemplateUsed(response, 'index.html') Here’s a quick primer on Django tests, for the uninitiated.
Testing in Django # jmad/tunes/views/__init__.py from django.views.generic import TemplateView class IndexView(TemplateView): template_name = "index.html" # jmad/jmad/urls.py from django.conf.urls import patterns, url from tunes.views import IndexView urlpatterns = patterns('', url(r'^$', IndexView.as_view(), name='index'), ) Here’s the code to make that test pass (assuming there’s an index.html in a template directory somewhere).
Testing in Django $ python manage.py test . --------------------------------------------------------------- ------- Ran 1 test in 0.029s OK Destroying test database for alias 'default'... $ And here’s how you’d run the test suite for the project.
Why CI?
Why CI? Drink more beer. How can I drink more beer if the client calls me on Saturday night because the site is down?Bugs should show up fast, and you should fix them before your code is deployed.
Why CI? Your test suite is only useful if you run it. You will forget to run your tests. Your collaborators will forget to run your tests. If you don’t run the tests, you won’t know your code is busted when it’s time to deploy.
Why CI? I run tests with SQLite, d@&$#t. It’s fast. It’s there. If I want to build my project on my mom’s Mac Mini I don’t have to install homebrew. Plus, running a test suite creates a new database everytime. Let the m1.small sitting in Northern Virginia wait around for TestCase to create the PostgreSQL database. It doesn’t even like beer.
Why CI? Your project is not getting deployed to a Macbook. Having said that, you need to run your tests in an environment like your production environment. Your project may have wacky dependencies that you installed a long time ago on your Macbook.
Why CI? Know immediately if you can’t install a package
Why CI? # requirements.txt ... PIL=1.1.7 # need to redeploy? The time to learn about a neat new package replacing an old clunky one is NOT when you’re trying to do an emergency redeployment.
Our example project
JMAD The Jazz Musicianship Archive and Database http://jmad.us code: https://github.com/kcharvey/jmad The Jazz Musicianship Archive and Database
http://jmad.us I’m a bass player, I play some jazz.
http://www.scu.edu/profiles/?p=5184 More importantly, I know Bill Stevens. He’s jazz faculty at Santa Clara University. He wrote a book called “Jazz Musicianship”. It’s a guide for jazz improvisation based on patterns that exists in many different jazz tunes.
While we read headings like “Adding Callables to ModelAdmin Classes”...
... his headings are like “Engaging the Bebop Principle”.
Screenshot JMAD is an archive of jazz music that’s been tagged with these different musical concepts. Basically you search by concept, instrument, difficulty, etc., and you get back solos with those parameters
CI in Practice: Travis
Travis • http://travis-ci.org • It’s where all these come from:
Travis: Setup 1. Sign in with your Github account 2. Select the repos you want Travis to work on 3. Add a .travis.yml file to the root of the repo 4. Commit
Travis: Basic .travis.yml language: python python:   - "3.3"   - "2.7" # command to install dependencies install:   - "pip install -r requirements/ci.txt" # command to run tests script: "python manage.py test"
Travis: Egg .travis.yml language: python python:   - "3.3"   - "2.7" # command to install dependencies install:   - "pip install -r requirements/ci.txt"   - "pip install ." # command to run tests script: "cd testproject;python manage.py test myapp"
Travis: Pros SaaS No server to set up, no apt-getting anything ever. It’s just there.
Travis: Pros Free as in “free beer” (for public repos)
Travis: Pros Config is maintained very obviously in Git Explicit, no implicit.
Travis: Pros Cool little badgy thingy. Impress your hacker friends with your TDD prowess.
Travis: Pros Unbelievably, stupidly easy.
Travis: Pros Just do it, even if you don’t have any tests. It will still check your requirements and build your app.
Travis: Cons Hope you’re using GitHub. Maybe there’s a way to use non-GitHub repos, but I’ll be damned if it’s documented anywhere.
Travis: Cons You’re stuck with their architecture. For instance, when I was putting this app together they didn’t have Python 3.4 yet.
coverage.py coverage.py is a utility created by Boston’s own Ned Batchelder.
coverage.py How much of my code is not covered by tests? It answers this question.
coverage.py $ coverage run --source='.' manage.py test --settings=jmad.settings.base Creating test database for alias 'default'... ...E ... ---------------------------------------------------------- Ran 4 tests in 3.353s FAILED (errors=1) Destroying test database for alias 'default'... Run your tests with coverage...
coverage.py $ coverage report --omit=*test*,*settings* Name Stmts Miss Cover ------------------------------------------------- jmad/__init__ 0 0 100% jmad/urls 6 0 100% jmad/wsgi 4 4 0% manage 6 0 100% people/__init__ 0 0 100% people/admin 1 0 100% people/models 1 0 100% people/views/__init__ 4 0 100% tunes/__init__ 0 0 100% tunes/admin 1 0 100% tunes/models 1 0 100% tunes/templatetags/__init__ 0 0 100% tunes/templatetags/add_css 5 0 100% tunes/urls 3 0 100% tunes/views/__init__ 5 0 100% ------------------------------------------------- TOTAL 37 4 89% ... then generate a report to see what’s not being tested.
coverage.py $ coverage report --omit=*test*,*settings* So let’s take a closer look at the report command
coverage.py $ coverage report --omit=*test*,*settings* --omit tells coverage to not report on a few things. Since we have multiple settings files, and we don’t test our tests, we omit them both.
coverage.py $ coverage report --omit=*test*,*settings* --fail-under=85 --fail-under take an integer, and compares that to the total percentage of coverage, and makes this command return a 2 (anything but 0 is failure).
Travis and coverage.py language: python python:   - "3.3"   - "2.7" # command to install dependencies install:   - "pip install -r requirements/ci.txt" # command to run tests script:   - "coverage run source=’.’ manage.py test"   - "coverage report --omit=*settings*,*test* --fail-under=85" # 85% coverage minimum Swap out your script with these two lines: one to run the tests with coverage, and the other to run a report that can fail. Now if we’re at 85% coverage and someone pushes new code without test coverage, we’ll drop below 85% and get a failed build.
coverage.py “Code without tests is broken by design.” -- Jacob Kaplan-Moss This is a good thing.
CI in Practice: Jenkins
Jenkins • http://jenkins-ci.org/ • Django’s Jenkins: http://ci.djangoproject.com/
Installing Jenkins $ wget http://mirrors.jenkins-ci.org/war/latest/jenkins.war $ java -jar jenkins.war http://localhost:8080 Just get the .war file, run it, and hit port 8080 on your machine. You could deploy it behind Tomcat or the like.
Or grab a VM Installing Jenkins I used a TurnKey Linux prebuilt VM.
Configuring Jenkins You’ll need some plugins: - Jenkins Violations Plugin - Jenkins Git Plugin - Jenkins Cobertura Plugin Install a few plugins.
Configuring Jenkins Got Selenium tests? So, if you’re like me, you’ve got Jenkins on a headless version of Linux. We’ll have to do some magic to get our Selenium tests to run.
Configuring Jenkins # on the Jenkins box $ sudo apt-get install iceweasel # install firefox $ sudo apt-get install xvfb # frame buffer emulator Install firefox (the package is called iceweasel for some reason).
Configuring Jenkins # /etc/init.d/xvfb #!/bin/bash if [ -z "$1" ]; then echo "`basename $0` {start|stop}" exit fi case "$1" in start) /usr/bin/Xvfb :99 -ac -screen 0 1024x768x8 & ;; stop) killall Xvfb ;; esac Configure xvfb to run when the server starts
Configuring Jenkins $ sudo chmod 755 /etc/init.d/xvfb $ sudo shutdown -r now make that file executable, and restart the server
Configuring Jenkins $ pip install django-jenkins INSTALLED_APPS = ( ... 'django_jenkins', ) ... JENKINS_TASKS = ( 'django_jenkins.tasks.run_pylint', 'django_jenkins.tasks.with_coverage', 'django_jenkins.tasks.run_pep8', # there are more of these ) $ python manage.py jenkins # Jenkins will run this command django-jenkins is a plugin that runs out tests and outputs the files Jenkins needs to show our build stats. pip install and add some stuff to your settings.py
Configuring Jenkins 1. Configure a new test (name, description) 2. Give it your repo URL 3. Tell it how often to build 4. Tell it the commands to run 5. Configure where to save the reports 6. Click “Build Now” Check out the tutorials in the “Resources” section of this slide deck for more on configuring your repo. It’ll take about 15 minutes the first time.
Configuring Jenkins #!/bin/bash virtualenv -p python3.4 env env/bin/pip install -r requirements/ci.txt export SECRET_KEY='dnqsj22jdv9wjsldfub9' export DISPLAY=:99 env/bin/python manage.py jenkins --settings=jmad.settings.ci here’s what that command really should be
So what did we get? Jenkins I used a TurnKey Linux prebuilt VM.
Here’s a list of all the projects Jenkins knows to build
The project page for JMAD. Note the historic list of builds at the bottom left.
An individual build. That’s a list of commit messages under ‘changes’. And the link to the console output.
Logged output
The workspace it built.
Latest test result
Free as in beer and speech Jenkins: Pros Open. Extensible. Good for the spirit.
Plugins install like Wordpress Jenkins: Pros And by that I mean, it’s almost *too* easy. Just search for them from your installation and click “install”.
Distributed builds Jenkins: Pros I haven’t done any work with this at all, but Jenkins supports a ‘master/slave’ mode, allowing a single Jenkins instance to control many others. This would allow you to test a project on a bunch of different platforms simultaneously. You can see how that would benefit the Django project itself, or other large Python packages.
It’s your architecture. Jenkins: Pros Need to run Python compiled with some magical incantation? Need a special server utility installed? Jenkins runs on an OS you control, so do what you gotta do.
It’s nobody else’s architecture. Jenkins: Cons That, of course, leads to our first con.
To paraphrase Uncle Ben, “With great power can come a whole lot of bullshit.”
15 apt-get update 16 sudo apt-get install build-essential 17 apt-get install build-essential 18 apt-get install libsqlite3-dev 19 apt-get install sqlite3 20 apt-get install bzip2 libbz2-dev 21 ls 22 ls .. 23 mkdir src 24 cd src/ 25 wget http://www.python.org/ftp/python/3.4.0/Python-3.4.0.tar.xz 26 tar xJf ./Python-3.4.0.tar.xz 27 cd Python-3.4.0/ 28 ./configure --prefix=/opt/python3.4 29 make && make install 30 python3.4 31 ln -s /opt/python3.4/bin/python3.4 ~/bin/python3.4 32 ls ~ 33 mkdir bin 34 ln -s /opt/python3.4/bin/python3.4 ~/bin/python3.4 35 ls Jenkins: Cons Here’s the first twenty lines of me fumbling through installing Python 3.4, pip, and virtualenv
36 ls bin 37 rm -rf bin 38 mkdir ~/bin 39 ln -s /opt/python3.4/bin/python3.4 ~/bin/python3.4 40 python2.4 41 python3.4 42 virtualenv 43 ls /opt/python3.4/bin/ 44 cd 45 ls 46 ls bin/ 47 bin/python3.4 48 python3.4 49 ls /usr/bin/ 50 ln -s /opt/python3.4/bin/python3.4 /usr/bin/python3.4 51 python3.4 52 rm -rf bin/ 53 wget https://raw.github.com/pypa/pip/master/contrib/get-pip.py 54 python3.4 get-pip.py 55 apt-get install zlib 56 apt-get install zlib1g Jenkins: Cons ... and here’s the next twenty lines...
57 python3.4 get-pip.py 58 apt-get install zlib1g 59 apt-get install zlib-dev 60 apt-get install zlibc 61 python3.4 get-pip.py 62 apt-get install zlib1g-dev 63 python3.4 get-pip.py 64 apt-get install zlib-bin 65 python3.4 get-pip. 66 python3.4 get-pip.py 67 cd src/ 68 ls 69 cd Python-3.4.0/ 70 history 71 ./configure --prefix=/opt/python3.4 72 make && make install 73 apt-get install libssl-dev openssl 74 make && make install 75 which pip 76 cd ~ 77 ln -s /opt/python3.4/bin/pip3.4 /usr/bin/pip3.4 78 pip3.4 install virtualenv Jenkins: Cons ... and the next. So you’ll need some sysadmin chops.
And I still need to set up a mail server. Jenkins: Cons
Git is a plugin Jenkins: Cons Again, it’s not hard to install plugins, but other tools are Git-centric, so it’s worth mentioning.
Best Practices
Best Practices Use multiple settings.py and requirements.txt files
Best Practices # jmad/settings/ci.py INSTALLED_APPS = ( ... ‘django_jenkins’ ) ... JENKINS_TASKS = ( ‘django_jenkins.tasks.run_pylint’, ‘django_jenkins.tasks.with_coverage’, ‘django_jenkins.tasks.run_pep8’ ) Keep this stuff out of your production app (and your dev environment, for that matter).
Best Practices # requirements/ci.txt ... coverage==3.7.1 # duped in dev.txt django_jenkins==0.15.0 pep8==1.5.6 (and your dev environment, for that matter).
Best Practices Rebuild your env in Jenkins
Best Practices #!/bin/bash rm -rf env virtualenv -p python2.7 env env/bin/pip install -r requirements/ci.txt export SECRET_KEY='dnqsj22jdv9wjsldfub9' env/bin/python manage.py jenkins --settings=jmad.settings.ci Toss the old env before you recreate it.
Further Exploration
“Just-in-time Jenkins” a.k.a. “The AWS Miser” a.k.a “Big Testing” Further Exploration You could imagine a scenario in which, using one of the many DevOps tools available, you spin up and AWS instance, install and configure Jenkins, set up your tests, report and then tear down the box. This would be particularly useful if you wanted to test on a multidtude of platforms but didn’t want to pay to keep them all up all the time.
Alternatives to Travis • https://circleci.com/ • https://drone.io/ Further Exploration Travis is not the only SaaS CI game in town. Drone.io works with BitBucket.
tox Further Exploration It’s a tool to test your project in multiple version of Python in one go, and can act as a front end to a CI server. Has anyone here used tox?
django-jenkins Tasks There are a number of tasks available in django-jenkins that I haven’t showed you yet.
django_jenkins.tasks.run_jshint django_jenkins.tasks.run_csslint django-jenkins Tasks Runs jshint or csshint tools of your static directory, and produces reports that work in Jenkins. You’ll need to install jshint/csslint on the box that Jenkins is running on.
django_jenkins.tasks.run_pyflakes django-jenkins Tasks If you’re using Pyflakes, django-jenkins has you covered. Add Pyflakes to you requirements/ci.txt file.
django_jenkins.tasks.run_flake8 django-jenkins Tasks Same deal with flake8. You’re beginning to see how jenkins is trying to fit in with whatever testing tools you’re already using.
django_jenkins.tasks.run_sloccount django-jenkins Tasks SLOCCount is a utility for counting lines of code. The developer missed a big opportunity to call his project SLOCConut, IMHO. Install SLOCCount on the server to get this one going.
django_jenkins.tasks.run_sloccount django-jenkins Tasks SLOCCount is a utility for counting lines of code. The developer missed a big opportunity to call his project SLOCConut, IMHO. Install SLOCCount on the server to get this one going.
django_jenkins.tasks.run_graphmodels django-jenkins Tasks You can also let Jenkins graph your models for you.
You need django-extensions and pygraphviz in your CI requirements for this one to work.
django_jenkins.tasks.with_local_celery django-jenkins Tasks Django Jenkins also provides a test runner to run your tests with Celery, if you’re in to that sort of thing.
Thanks! @kevinharvey github.com/kcharvey
Questions? @kevinharvey github.com/kcharvey Show of hands: if your boss/client/conscience dictated that you had to implement CI tomorrow, would you use one of the hosted/SaaS tools or go with Jenkins?
Resources Setting up Jenkins for Selenium tests • http://www.labelmedia.co.uk/blog/setting-up- selenium-server-on-a-headless-jenkins-ci-build- machine.html • http://www.installationpage.com/selenium/how- to-run-selenium-headless-firefox-in-ubuntu/ • Just Google it

More Related Content

PDF
Towards Continuous Deployment with Django
byRoger Barnes
 
PDF
DjangoCon 2013 - How to Write Fast and Efficient Unit Tests in Django
byCasey Kinsey
 
PPTX
Django strategy-test
byRoyce Haynes
 
PDF
Drupalcamp Simpletest
bylyricnz
 
ZIP
Drupal Deployment
byJeff Eaton
 
PDF
Capybara testing
byFutureworkz
 
PDF
DevOps叢林裡的小隊游擊戰術 (@ iThome DevOps 2015)
byChen Cheng-Wei
 
PDF
How do I write Testable Javascript - Presented at dev.Objective() June 16, 2016
byGavin Pickin
 
Towards Continuous Deployment with Django
byRoger Barnes
 
DjangoCon 2013 - How to Write Fast and Efficient Unit Tests in Django
byCasey Kinsey
 
Django strategy-test
byRoyce Haynes
 
Drupalcamp Simpletest
bylyricnz
 
Drupal Deployment
byJeff Eaton
 
Capybara testing
byFutureworkz
 
DevOps叢林裡的小隊游擊戰術 (@ iThome DevOps 2015)
byChen Cheng-Wei
 
How do I write Testable Javascript - Presented at dev.Objective() June 16, 2016
byGavin Pickin
 

What's hot

ZIP
Five Easy Ways to QA Your Drupal Site
byMediacurrent
 
PDF
Unit testing @ WordPress Meetup Tilburg 7 januari 2014
byBarry Kooij
 
KEY
Continuous Integration & Drupal
byLimoenGroen
 
PDF
Midwest PHP 2017 DevOps For Small team
byJoe Ferguson
 
PDF
Node.js vs Play Framework
byYevgeniy Brikman
 
PDF
Das Frontend richtig Testen – mit Jest @Developer Week 2018
byHolger Grosse-Plankermann
 
PDF
How do I Write Testable Javascript so I can Test my CF API on Server and Client
byColdFusionConference
 
PDF
How Testing Changed My Life
byNikolay Bachiyski
 
ODP
Building JBoss AS 7 for Fedora
bywolfc71
 
PDF
Jest: Frontend Testing leicht gemacht @EnterJS2018
byHolger Grosse-Plankermann
 
PDF
Selenium RC: Automated Testing of Modern Web Applications
byqooxdoo
 
PDF
Testing Automaton - CFSummit 2016
byOrtus Solutions, Corp
 
PPTX
JavaLand - Integration Testing How-to
byNicolas Fränkel
 
PDF
Night Watch with QA
byCarsten Sandtner
 
PPTX
Unit testing plugins: The 5 W's and an H
byTom Jenkins
 
PPT
Getting Started With Jenkins And Drupal
byPhilip Norton
 
PDF
Django Best Practices
byAbdullah Çetin ÇAVDAR
 
PPT
Django, What is it, Why is it cool?
byTom Brander
 
PDF
Testing nightwatch, by David Torroija
byDavid Torroija
 
PDF
Testing Django Applications
byHonza Král
 
Five Easy Ways to QA Your Drupal Site
byMediacurrent
 
Unit testing @ WordPress Meetup Tilburg 7 januari 2014
byBarry Kooij
 
Continuous Integration & Drupal
byLimoenGroen
 
Midwest PHP 2017 DevOps For Small team
byJoe Ferguson
 
Node.js vs Play Framework
byYevgeniy Brikman
 
Das Frontend richtig Testen – mit Jest @Developer Week 2018
byHolger Grosse-Plankermann
 
How do I Write Testable Javascript so I can Test my CF API on Server and Client
byColdFusionConference
 
How Testing Changed My Life
byNikolay Bachiyski
 
Building JBoss AS 7 for Fedora
bywolfc71
 
Jest: Frontend Testing leicht gemacht @EnterJS2018
byHolger Grosse-Plankermann
 
Selenium RC: Automated Testing of Modern Web Applications
byqooxdoo
 
Testing Automaton - CFSummit 2016
byOrtus Solutions, Corp
 
JavaLand - Integration Testing How-to
byNicolas Fränkel
 
Night Watch with QA
byCarsten Sandtner
 
Unit testing plugins: The 5 W's and an H
byTom Jenkins
 
Getting Started With Jenkins And Drupal
byPhilip Norton
 
Django Best Practices
byAbdullah Çetin ÇAVDAR
 
Django, What is it, Why is it cool?
byTom Brander
 
Testing nightwatch, by David Torroija
byDavid Torroija
 
Testing Django Applications
byHonza Král
 

Viewers also liked

ODP
Integration Testing in Python
byPanoptic Development, Inc.
 
PDF
Testing Microservices Architectures
byRenan Martins
 
PDF
Unit and integration Testing
byDavid Berliner
 
PPTX
Django: инструкция по применению
byIvan Kolodyazhny
 
PDF
Django dev-env-my-way
byRobert Lujo
 
PPT
Selenium
byjagdishdevabhaipatel
 
PDF
TestArena Instrukcja obsługi dla wersji 3.0.929
byRadoslaw Smilgin
 
PDF
Введение в Python и Django
byTaras Lyapun
 
PPTX
Achieving Balanced Agile Testing
byCprime
 
PDF
Acceptance & Integration Testing With Behat (PHPNw2011)
bybenwaine
 
PDF
Testing & Integration (The Remix)
byInes Sombra
 
PDF
Automating Django Functional Tests Using Selenium on Cloud
byJonghyun Park
 
PDF
Jenkins & Selenium
byadamcarmi
 
PPT
Exploratory Testing As A Quest
byChrishoneybee
 
PDF
Integration Testing Practice using Perl
byMasaki Nakagawa
 
PDF
A Taste of Exploratory Testing
byAnne-Marie Charrett
 
KEY
Testing with Jenkins, Selenium and Continuous Deployment
byMax Klymyshyn
 
PPTX
What is this exploratory testing thing
bytonybruce
 
PPTX
Tips for Writing Better Charters for Exploratory Testing Sessions by Michael...
byTEST Huddle
 
PDF
Play Framework + Docker + CircleCI + AWS + EC2 Container Service
byJosh Padnick
 
Integration Testing in Python
byPanoptic Development, Inc.
 
Testing Microservices Architectures
byRenan Martins
 
Unit and integration Testing
byDavid Berliner
 
Django: инструкция по применению
byIvan Kolodyazhny
 
Django dev-env-my-way
byRobert Lujo
 
Selenium
byjagdishdevabhaipatel
 
TestArena Instrukcja obsługi dla wersji 3.0.929
byRadoslaw Smilgin
 
Введение в Python и Django
byTaras Lyapun
 
Achieving Balanced Agile Testing
byCprime
 
Acceptance & Integration Testing With Behat (PHPNw2011)
bybenwaine
 
Testing & Integration (The Remix)
byInes Sombra
 
Automating Django Functional Tests Using Selenium on Cloud
byJonghyun Park
 
Jenkins & Selenium
byadamcarmi
 
Exploratory Testing As A Quest
byChrishoneybee
 
Integration Testing Practice using Perl
byMasaki Nakagawa
 
A Taste of Exploratory Testing
byAnne-Marie Charrett
 
Testing with Jenkins, Selenium and Continuous Deployment
byMax Klymyshyn
 
What is this exploratory testing thing
bytonybruce
 
Tips for Writing Better Charters for Exploratory Testing Sessions by Michael...
byTEST Huddle
 
Play Framework + Docker + CircleCI + AWS + EC2 Container Service
byJosh Padnick
 

Similar to Continuous Integration Testing in Django

PDF
Making the most of your Test Suite
byericholscher
 
PPTX
Continuous Testing and New Tools for Automation - Presentation from StarWest ...
bySauce Labs
 
PPTX
Testing Django APIs
bytyomo4ka
 
PDF
Let’s start Continuous Integration with jenkins
byTomohide Kakeya
 
PDF
Python testing like a pro by Keith Yang
byPYCON MY PLT
 
PDF
The Journey Towards Continuous Integration
bySebastian Marek
 
PDF
Release with confidence
byJohn Congdon
 
PDF
Continuous Integration with Open Source Tools - PHPUgFfm 2014-11-20
byMichael Lihs
 
KEY
PHP to Python with No Regrets
byAlex Ezell
 
PPTX
Experiences Bringing CD to a DoD Project
byGene Gotimer
 
PDF
Dominik Veselý - Vše co jste kdy chtěli vědět o CI a báli jste se zeptat
bymdevtalk
 
PDF
Testdriven Development With Python 1st Edition Harry J W Percival
byykvfacwe5221
 
PPTX
Continuous integration for open source distros v 3.0
bySriram Narayanan
 
PDF
Into The Box 2018 CI Deep Dive
byOrtus Solutions, Corp
 
PDF
Show an Open Source Project Some Love and Start Using Travis-CI
byJoel Byler
 
PDF
Survival of the Continuist
byPaul Blundell
 
PDF
Portable CI wGitLab and Github led by Gavin Pickin.pdf
byOrtus Solutions, Corp
 
PDF
Testing Django Applications
byGareth Rushgrove
 
PDF
Summit 16: Stop Writing Legacy Code!
byOPNFV
 
PDF
TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools
byMichael Lihs
 
Making the most of your Test Suite
byericholscher
 
Continuous Testing and New Tools for Automation - Presentation from StarWest ...
bySauce Labs
 
Testing Django APIs
bytyomo4ka
 
Let’s start Continuous Integration with jenkins
byTomohide Kakeya
 
Python testing like a pro by Keith Yang
byPYCON MY PLT
 
The Journey Towards Continuous Integration
bySebastian Marek
 
Release with confidence
byJohn Congdon
 
Continuous Integration with Open Source Tools - PHPUgFfm 2014-11-20
byMichael Lihs
 
PHP to Python with No Regrets
byAlex Ezell
 
Experiences Bringing CD to a DoD Project
byGene Gotimer
 
Dominik Veselý - Vše co jste kdy chtěli vědět o CI a báli jste se zeptat
bymdevtalk
 
Testdriven Development With Python 1st Edition Harry J W Percival
byykvfacwe5221
 
Continuous integration for open source distros v 3.0
bySriram Narayanan
 
Into The Box 2018 CI Deep Dive
byOrtus Solutions, Corp
 
Show an Open Source Project Some Love and Start Using Travis-CI
byJoel Byler
 
Survival of the Continuist
byPaul Blundell
 
Portable CI wGitLab and Github led by Gavin Pickin.pdf
byOrtus Solutions, Corp
 
Testing Django Applications
byGareth Rushgrove
 
Summit 16: Stop Writing Legacy Code!
byOPNFV
 
TYPO3 Camp Stuttgart 2015 - Continuous Delivery with Open Source Tools
byMichael Lihs
 

Recently uploaded

PPTX
Cyber-Security-Essentials (21AK1A0217).pptx
byGaganGagan44
 
PPSX
Domain Centered Architecture for complex business domains
byRob Vens
 
DOCX
Best Tableau Alternatives for Data Analytics and Reporting.docx
byVarsha Nayak
 
PPT
Evolution of the Major Programming Languages
bymjmansoori54
 
PDF
The 50+ First-Timer: It’s never too late for Open Source!
byImma Valls Bernaus
 
PDF
Driving Stress Detection Using Multimodal CNN with Nonlinear Representation o...
byPranjal Kumar
 
PPTX
Java Modern Puzzlers, a guide to new programming features
bySimon Ritter
 
PPTX
Oracle_AWS_Azure_GCP_Comparison_ModernTech.pptx
byVITS184D1
 
PDF
The new Volto Form Block, Plone Conference 2025
byRob Gietema
 
PDF
Metrics, logs, traces, and mayhem_ introducing an observability adventure gam...
byImma Valls Bernaus
 
PPTX
Systems Programming Lecture Compute.pptx
byAdekunle25
 
PPTX
Moving Plone Blob Storage to S3 Object Storage - Plone Conference 2025
byAlin Voinea
 
PDF
Ensuring Regulatory Excellence with Insurance Compliance Software
byInsurance Tech Services
 
PPTX
Financial Literacy for Software Developers
byBalanathanVirupasan
 
PDF
Best Tableau Alternatives for Data Analytics and Reporting.pdf
byVarsha Nayak
 
PPT
SAP ERP Training For Senior Managers.ppt
byBalanathanVirupasan
 
PDF
Dreamforce 2025: Welcome to the Agentic Enterprise
byDele Amefo
 
PDF
Scraping Amazon Prime Watchlist Data for Viewing Patterns.pdf
byyashpatric
 
PPT
preliminaries, concepts of programming languages
bymjmansoori54
 
DOCX
What Is the Best BI Software Other Than Tableau.docx
byVarsha Nayak
 
Cyber-Security-Essentials (21AK1A0217).pptx
byGaganGagan44
 
Domain Centered Architecture for complex business domains
byRob Vens
 
Best Tableau Alternatives for Data Analytics and Reporting.docx
byVarsha Nayak
 
Evolution of the Major Programming Languages
bymjmansoori54
 
The 50+ First-Timer: It’s never too late for Open Source!
byImma Valls Bernaus
 
Driving Stress Detection Using Multimodal CNN with Nonlinear Representation o...
byPranjal Kumar
 
Java Modern Puzzlers, a guide to new programming features
bySimon Ritter
 
Oracle_AWS_Azure_GCP_Comparison_ModernTech.pptx
byVITS184D1
 
The new Volto Form Block, Plone Conference 2025
byRob Gietema
 
Metrics, logs, traces, and mayhem_ introducing an observability adventure gam...
byImma Valls Bernaus
 
Systems Programming Lecture Compute.pptx
byAdekunle25
 
Moving Plone Blob Storage to S3 Object Storage - Plone Conference 2025
byAlin Voinea
 
Ensuring Regulatory Excellence with Insurance Compliance Software
byInsurance Tech Services
 
Financial Literacy for Software Developers
byBalanathanVirupasan
 
Best Tableau Alternatives for Data Analytics and Reporting.pdf
byVarsha Nayak
 
SAP ERP Training For Senior Managers.ppt
byBalanathanVirupasan
 
Dreamforce 2025: Welcome to the Agentic Enterprise
byDele Amefo
 
Scraping Amazon Prime Watchlist Data for Viewing Patterns.pdf
byyashpatric
 
preliminaries, concepts of programming languages
bymjmansoori54
 
What Is the Best BI Software Other Than Tableau.docx
byVarsha Nayak
 

Continuous Integration Testing in Django

  • 1.
    Continuous Integration Testing DjangoBoston Meetup 24 April 2014 Kevin Harvey @kevinharvey kevin@storyandstructure.com
  • 2.
  • 3.
    Who is thisguy? Fast Slow Unit Functional • Chief Technologist at Story+Structure • Djangonaut since 2007 (0.96)
  • 4.
    Here’s the best$24 I ever spent.
  • 5.
  • 6.
    Agenda • What isContinuous Integration? • Why use Continuous Integration? • CI in Practice: Travis • Coverage Thresholds with coverage.py • CI in Practice: Jenkins • Best Practices & Further Exploration
  • 7.
  • 8.
    Continuous Integration islike having a tireless robot that cleans up after you.
  • 9.
    What is CI? 1.Checkout out the latest copy of your code 2. Install the dependencies 3. Run the tests 4. Report the outcome Some server somewhere checks out your code, installs all your dependencies, runs your tests, and let’s you know if it worked or not.
  • 10.
    Testing in Django #jmad/tunes/tests/test_views.py from django.test import TestCase class TunesViewTestCase(TestCase): def test_index_view(self): response = self.client.get('/') self.assertEqual(response.status_code, 200) self.assertTemplateUsed(response, 'index.html') Here’s a quick primer on Django tests, for the uninitiated.
  • 11.
    Testing in Django #jmad/tunes/views/__init__.py from django.views.generic import TemplateView class IndexView(TemplateView): template_name = "index.html" # jmad/jmad/urls.py from django.conf.urls import patterns, url from tunes.views import IndexView urlpatterns = patterns('', url(r'^$', IndexView.as_view(), name='index'), ) Here’s the code to make that test pass (assuming there’s an index.html in a template directory somewhere).
  • 12.
    Testing in Django $python manage.py test . --------------------------------------------------------------- ------- Ran 1 test in 0.029s OK Destroying test database for alias 'default'... $ And here’s how you’d run the test suite for the project.
  • 13.
  • 14.
    Why CI? Drink morebeer. How can I drink more beer if the client calls me on Saturday night because the site is down?Bugs should show up fast, and you should fix them before your code is deployed.
  • 15.
    Why CI? Your testsuite is only useful if you run it. You will forget to run your tests. Your collaborators will forget to run your tests. If you don’t run the tests, you won’t know your code is busted when it’s time to deploy.
  • 16.
    Why CI? I runtests with SQLite, d@&$#t. It’s fast. It’s there. If I want to build my project on my mom’s Mac Mini I don’t have to install homebrew. Plus, running a test suite creates a new database everytime. Let the m1.small sitting in Northern Virginia wait around for TestCase to create the PostgreSQL database. It doesn’t even like beer.
  • 17.
    Why CI? Your projectis not getting deployed to a Macbook. Having said that, you need to run your tests in an environment like your production environment. Your project may have wacky dependencies that you installed a long time ago on your Macbook.
  • 18.
    Why CI? Know immediatelyif you can’t install a package
  • 19.
    Why CI? # requirements.txt ... PIL=1.1.7# need to redeploy? The time to learn about a neat new package replacing an old clunky one is NOT when you’re trying to do an emergency redeployment.
  • 20.
  • 21.
    JMAD The Jazz MusicianshipArchive and Database http://jmad.us code: https://github.com/kcharvey/jmad The Jazz Musicianship Archive and Database
  • 22.
    http://jmad.us I’m a bassplayer, I play some jazz.
  • 23.
    http://www.scu.edu/profiles/?p=5184 More importantly, Iknow Bill Stevens. He’s jazz faculty at Santa Clara University. He wrote a book called “Jazz Musicianship”. It’s a guide for jazz improvisation based on patterns that exists in many different jazz tunes.
  • 24.
    While we readheadings like “Adding Callables to ModelAdmin Classes”...
  • 25.
    ... his headingsare like “Engaging the Bebop Principle”.
  • 26.
    Screenshot JMAD is anarchive of jazz music that’s been tagged with these different musical concepts. Basically you search by concept, instrument, difficulty, etc., and you get back solos with those parameters
  • 27.
  • 28.
  • 29.
    Travis: Setup 1. Signin with your Github account 2. Select the repos you want Travis to work on 3. Add a .travis.yml file to the root of the repo 4. Commit
  • 31.
    Travis: Basic .travis.yml language:python python:   - "3.3"   - "2.7" # command to install dependencies install:   - "pip install -r requirements/ci.txt" # command to run tests script: "python manage.py test"
  • 32.
    Travis: Egg .travis.yml language:python python:   - "3.3"   - "2.7" # command to install dependencies install:   - "pip install -r requirements/ci.txt"   - "pip install ." # command to run tests script: "cd testproject;python manage.py test myapp"
  • 35.
    Travis: Pros SaaS No serverto set up, no apt-getting anything ever. It’s just there.
  • 36.
    Travis: Pros Free asin “free beer” (for public repos)
  • 37.
    Travis: Pros Config ismaintained very obviously in Git Explicit, no implicit.
  • 38.
    Travis: Pros Cool littlebadgy thingy. Impress your hacker friends with your TDD prowess.
  • 39.
  • 40.
    Travis: Pros Just doit, even if you don’t have any tests. It will still check your requirements and build your app.
  • 41.
    Travis: Cons Hope you’reusing GitHub. Maybe there’s a way to use non-GitHub repos, but I’ll be damned if it’s documented anywhere.
  • 42.
    Travis: Cons You’re stuckwith their architecture. For instance, when I was putting this app together they didn’t have Python 3.4 yet.
  • 43.
    coverage.py coverage.py is autility created by Boston’s own Ned Batchelder.
  • 44.
    coverage.py How much ofmy code is not covered by tests? It answers this question.
  • 45.
    coverage.py $ coverage run--source='.' manage.py test --settings=jmad.settings.base Creating test database for alias 'default'... ...E ... ---------------------------------------------------------- Ran 4 tests in 3.353s FAILED (errors=1) Destroying test database for alias 'default'... Run your tests with coverage...
  • 46.
    coverage.py $ coverage report--omit=*test*,*settings* Name Stmts Miss Cover ------------------------------------------------- jmad/__init__ 0 0 100% jmad/urls 6 0 100% jmad/wsgi 4 4 0% manage 6 0 100% people/__init__ 0 0 100% people/admin 1 0 100% people/models 1 0 100% people/views/__init__ 4 0 100% tunes/__init__ 0 0 100% tunes/admin 1 0 100% tunes/models 1 0 100% tunes/templatetags/__init__ 0 0 100% tunes/templatetags/add_css 5 0 100% tunes/urls 3 0 100% tunes/views/__init__ 5 0 100% ------------------------------------------------- TOTAL 37 4 89% ... then generate a report to see what’s not being tested.
  • 47.
    coverage.py $ coverage report--omit=*test*,*settings* So let’s take a closer look at the report command
  • 48.
    coverage.py $ coverage report--omit=*test*,*settings* --omit tells coverage to not report on a few things. Since we have multiple settings files, and we don’t test our tests, we omit them both.
  • 49.
    coverage.py $ coverage report--omit=*test*,*settings* --fail-under=85 --fail-under take an integer, and compares that to the total percentage of coverage, and makes this command return a 2 (anything but 0 is failure).
  • 50.
    Travis and coverage.py language:python python:   - "3.3"   - "2.7" # command to install dependencies install:   - "pip install -r requirements/ci.txt" # command to run tests script:   - "coverage run source=’.’ manage.py test"   - "coverage report --omit=*settings*,*test* --fail-under=85" # 85% coverage minimum Swap out your script with these two lines: one to run the tests with coverage, and the other to run a report that can fail. Now if we’re at 85% coverage and someone pushes new code without test coverage, we’ll drop below 85% and get a failed build.
  • 51.
    coverage.py “Code without testsis broken by design.” -- Jacob Kaplan-Moss This is a good thing.
  • 52.
  • 53.
    Jenkins • http://jenkins-ci.org/ • Django’sJenkins: http://ci.djangoproject.com/
  • 54.
    Installing Jenkins $ wgethttp://mirrors.jenkins-ci.org/war/latest/jenkins.war $ java -jar jenkins.war http://localhost:8080 Just get the .war file, run it, and hit port 8080 on your machine. You could deploy it behind Tomcat or the like.
  • 55.
    Or grab aVM Installing Jenkins I used a TurnKey Linux prebuilt VM.
  • 56.
    Configuring Jenkins You’ll needsome plugins: - Jenkins Violations Plugin - Jenkins Git Plugin - Jenkins Cobertura Plugin Install a few plugins.
  • 57.
    Configuring Jenkins Got Seleniumtests? So, if you’re like me, you’ve got Jenkins on a headless version of Linux. We’ll have to do some magic to get our Selenium tests to run.
  • 58.
    Configuring Jenkins # onthe Jenkins box $ sudo apt-get install iceweasel # install firefox $ sudo apt-get install xvfb # frame buffer emulator Install firefox (the package is called iceweasel for some reason).
  • 59.
    Configuring Jenkins # /etc/init.d/xvfb #!/bin/bash if[ -z "$1" ]; then echo "`basename $0` {start|stop}" exit fi case "$1" in start) /usr/bin/Xvfb :99 -ac -screen 0 1024x768x8 & ;; stop) killall Xvfb ;; esac Configure xvfb to run when the server starts
  • 60.
    Configuring Jenkins $ sudochmod 755 /etc/init.d/xvfb $ sudo shutdown -r now make that file executable, and restart the server
  • 61.
    Configuring Jenkins $ pipinstall django-jenkins INSTALLED_APPS = ( ... 'django_jenkins', ) ... JENKINS_TASKS = ( 'django_jenkins.tasks.run_pylint', 'django_jenkins.tasks.with_coverage', 'django_jenkins.tasks.run_pep8', # there are more of these ) $ python manage.py jenkins # Jenkins will run this command django-jenkins is a plugin that runs out tests and outputs the files Jenkins needs to show our build stats. pip install and add some stuff to your settings.py
  • 62.
    Configuring Jenkins 1. Configurea new test (name, description) 2. Give it your repo URL 3. Tell it how often to build 4. Tell it the commands to run 5. Configure where to save the reports 6. Click “Build Now” Check out the tutorials in the “Resources” section of this slide deck for more on configuring your repo. It’ll take about 15 minutes the first time.
  • 67.
    Configuring Jenkins #!/bin/bash virtualenv -ppython3.4 env env/bin/pip install -r requirements/ci.txt export SECRET_KEY='dnqsj22jdv9wjsldfub9' export DISPLAY=:99 env/bin/python manage.py jenkins --settings=jmad.settings.ci here’s what that command really should be
  • 70.
    So what didwe get? Jenkins I used a TurnKey Linux prebuilt VM.
  • 71.
    Here’s a listof all the projects Jenkins knows to build
  • 72.
    The project pagefor JMAD. Note the historic list of builds at the bottom left.
  • 73.
    An individual build.That’s a list of commit messages under ‘changes’. And the link to the console output.
  • 74.
  • 75.
  • 76.
  • 77.
    Free as inbeer and speech Jenkins: Pros Open. Extensible. Good for the spirit.
  • 78.
    Plugins install likeWordpress Jenkins: Pros And by that I mean, it’s almost *too* easy. Just search for them from your installation and click “install”.
  • 79.
    Distributed builds Jenkins: Pros Ihaven’t done any work with this at all, but Jenkins supports a ‘master/slave’ mode, allowing a single Jenkins instance to control many others. This would allow you to test a project on a bunch of different platforms simultaneously. You can see how that would benefit the Django project itself, or other large Python packages.
  • 80.
    It’s your architecture. Jenkins:Pros Need to run Python compiled with some magical incantation? Need a special server utility installed? Jenkins runs on an OS you control, so do what you gotta do.
  • 81.
    It’s nobody else’sarchitecture. Jenkins: Cons That, of course, leads to our first con.
  • 82.
    To paraphrase UncleBen, “With great power can come a whole lot of bullshit.”
  • 83.
    15 apt-get update 16sudo apt-get install build-essential 17 apt-get install build-essential 18 apt-get install libsqlite3-dev 19 apt-get install sqlite3 20 apt-get install bzip2 libbz2-dev 21 ls 22 ls .. 23 mkdir src 24 cd src/ 25 wget http://www.python.org/ftp/python/3.4.0/Python-3.4.0.tar.xz 26 tar xJf ./Python-3.4.0.tar.xz 27 cd Python-3.4.0/ 28 ./configure --prefix=/opt/python3.4 29 make && make install 30 python3.4 31 ln -s /opt/python3.4/bin/python3.4 ~/bin/python3.4 32 ls ~ 33 mkdir bin 34 ln -s /opt/python3.4/bin/python3.4 ~/bin/python3.4 35 ls Jenkins: Cons Here’s the first twenty lines of me fumbling through installing Python 3.4, pip, and virtualenv
  • 84.
    36 ls bin 37rm -rf bin 38 mkdir ~/bin 39 ln -s /opt/python3.4/bin/python3.4 ~/bin/python3.4 40 python2.4 41 python3.4 42 virtualenv 43 ls /opt/python3.4/bin/ 44 cd 45 ls 46 ls bin/ 47 bin/python3.4 48 python3.4 49 ls /usr/bin/ 50 ln -s /opt/python3.4/bin/python3.4 /usr/bin/python3.4 51 python3.4 52 rm -rf bin/ 53 wget https://raw.github.com/pypa/pip/master/contrib/get-pip.py 54 python3.4 get-pip.py 55 apt-get install zlib 56 apt-get install zlib1g Jenkins: Cons ... and here’s the next twenty lines...
  • 85.
    57 python3.4 get-pip.py 58apt-get install zlib1g 59 apt-get install zlib-dev 60 apt-get install zlibc 61 python3.4 get-pip.py 62 apt-get install zlib1g-dev 63 python3.4 get-pip.py 64 apt-get install zlib-bin 65 python3.4 get-pip. 66 python3.4 get-pip.py 67 cd src/ 68 ls 69 cd Python-3.4.0/ 70 history 71 ./configure --prefix=/opt/python3.4 72 make && make install 73 apt-get install libssl-dev openssl 74 make && make install 75 which pip 76 cd ~ 77 ln -s /opt/python3.4/bin/pip3.4 /usr/bin/pip3.4 78 pip3.4 install virtualenv Jenkins: Cons ... and the next. So you’ll need some sysadmin chops.
  • 86.
    And I stillneed to set up a mail server. Jenkins: Cons
  • 87.
    Git is aplugin Jenkins: Cons Again, it’s not hard to install plugins, but other tools are Git-centric, so it’s worth mentioning.
  • 88.
  • 89.
    Best Practices Use multiplesettings.py and requirements.txt files
  • 90.
    Best Practices # jmad/settings/ci.py INSTALLED_APPS= ( ... ‘django_jenkins’ ) ... JENKINS_TASKS = ( ‘django_jenkins.tasks.run_pylint’, ‘django_jenkins.tasks.with_coverage’, ‘django_jenkins.tasks.run_pep8’ ) Keep this stuff out of your production app (and your dev environment, for that matter).
  • 91.
    Best Practices # requirements/ci.txt ... coverage==3.7.1# duped in dev.txt django_jenkins==0.15.0 pep8==1.5.6 (and your dev environment, for that matter).
  • 92.
  • 93.
    Best Practices #!/bin/bash rm -rfenv virtualenv -p python2.7 env env/bin/pip install -r requirements/ci.txt export SECRET_KEY='dnqsj22jdv9wjsldfub9' env/bin/python manage.py jenkins --settings=jmad.settings.ci Toss the old env before you recreate it.
  • 94.
  • 95.
    “Just-in-time Jenkins” a.k.a. “The AWSMiser” a.k.a “Big Testing” Further Exploration You could imagine a scenario in which, using one of the many DevOps tools available, you spin up and AWS instance, install and configure Jenkins, set up your tests, report and then tear down the box. This would be particularly useful if you wanted to test on a multidtude of platforms but didn’t want to pay to keep them all up all the time.
  • 96.
    Alternatives to Travis •https://circleci.com/ • https://drone.io/ Further Exploration Travis is not the only SaaS CI game in town. Drone.io works with BitBucket.
  • 97.
    tox Further Exploration It’s atool to test your project in multiple version of Python in one go, and can act as a front end to a CI server. Has anyone here used tox?
  • 98.
    django-jenkins Tasks There area number of tasks available in django-jenkins that I haven’t showed you yet.
  • 99.
    django_jenkins.tasks.run_jshint django_jenkins.tasks.run_csslint django-jenkins Tasks Runs jshintor csshint tools of your static directory, and produces reports that work in Jenkins. You’ll need to install jshint/csslint on the box that Jenkins is running on.
  • 100.
    django_jenkins.tasks.run_pyflakes django-jenkins Tasks If you’reusing Pyflakes, django-jenkins has you covered. Add Pyflakes to you requirements/ci.txt file.
  • 101.
    django_jenkins.tasks.run_flake8 django-jenkins Tasks Same dealwith flake8. You’re beginning to see how jenkins is trying to fit in with whatever testing tools you’re already using.
  • 102.
    django_jenkins.tasks.run_sloccount django-jenkins Tasks SLOCCount isa utility for counting lines of code. The developer missed a big opportunity to call his project SLOCConut, IMHO. Install SLOCCount on the server to get this one going.
  • 103.
    django_jenkins.tasks.run_sloccount django-jenkins Tasks SLOCCount isa utility for counting lines of code. The developer missed a big opportunity to call his project SLOCConut, IMHO. Install SLOCCount on the server to get this one going.
  • 104.
    django_jenkins.tasks.run_graphmodels django-jenkins Tasks You canalso let Jenkins graph your models for you.
  • 105.
    You need django-extensionsand pygraphviz in your CI requirements for this one to work.
  • 106.
    django_jenkins.tasks.with_local_celery django-jenkins Tasks Django Jenkinsalso provides a test runner to run your tests with Celery, if you’re in to that sort of thing.
  • 107.
  • 108.
    Questions? @kevinharvey github.com/kcharvey Show of hands:if your boss/client/conscience dictated that you had to implement CI tomorrow, would you use one of the hosted/SaaS tools or go with Jenkins?
  • 109.
    Resources Setting up Jenkinsfor Selenium tests • http://www.labelmedia.co.uk/blog/setting-up- selenium-server-on-a-headless-jenkins-ci-build- machine.html • http://www.installationpage.com/selenium/how- to-run-selenium-headless-firefox-in-ubuntu/ • Just Google it