Lesson 1: The Whys and Hows of Automated Testing
This section is co-authored by Denis Petelin and Prof. Callahan.
Why do we test?
We test to see if the software does what we want it to do.
And whenever it doesn't, what are the effects?
Classic way to do testing: test cases, bugs, regression,
growing "regression debt".
Please study regression testing .
Revolutionary idea: zero-bug mindset: bugs are not tasks in
backlog, you have to fix them as you go -- by the end of the
day zero bugs exist.
This is part of the "incremental improvement" idea: if we do continuous integration and continuous delivery with small batches, each delivery into production should produce at most a "small batch" of bugs! And we can fix that small batch immediately.
Revolutionary idea: zero-length feedback, developers can
test and fix bugs immediately.
Part of this is establishing a culture of trust: If we need to feed approval for each change through multiple levels of bureaucracy, we can't fix bugs right away. And we can relate this back to the discussion in chapter one on "Taylorism" versus "Toyota Production System": in the former, the "workers" just carry out the plans of the "managers." In the latter, everyone is responsible for the entire production process.
- Test pyramid:
- Unit tests for individual classes and methods (models, controllers, views)
- Integration tests to check feature top-down.
- Acceptance test to check feature as user sees it.
- TestCase: set of checks to be performed.
- Fixture: prepared data to be loaded into the db.
- Fake: a real object created for the test.
- Stub: a crude imitation of real object returning hard-coded values.
- Mock: an elegant imitation of the object (if real object is not yet ready or expensive).
- Test suite: set of tests serving specific purpose. Always: smoke test, main success [AKA happy path], extended tests.
- Django benefits:
- No need to unit-test Models (except custom query sets & business logic methods).
- No need to integration-test Autogenerated View (except live tests).
- Anatomy of test case:
- Arrange -- Act -- Assert.
- Assert kinds.
- Preparing data -- AutoFixture
- TaskModelTransactionTestCase(TransactionTestCase): regular fixture.
- For lazy guys -- AutoFixture :)
- Typical mistakes:
- Useless tests -- testing default Models methods, for example.
- Testing implementation -- method save_changes() returns OK -- everything is OK! (Test should check if changes indeed persisted).
- Large tests? Fat controllers!
- Small methods -- less than a screen.
- Small tests -- 8-10 lines.
- Refactoring palette in the PyCharm.
- Good beginners pattern:
- Create Model. Add tests if there are custom methods.
- Create Controller (View as Django calls it). Test if does what it should do. Test if it handles errors.
- Write View (Template as Django calls it). Write LiveTestCase using requirements.
- Why preparing requirements still matters (“Please show balance" in Danfoss).
- Big idea: can we somehow make requirements document testable?
- Turning use cases into tests -- gherkin
- Feature file & steps
- Passing info around -- context
- Selenium -- driving real browser around
- Behave test runner (behave-Jango)
- JIRA: acceptance tests are now part of the
- Relying strictly on this type of testing is bad idea! (See execution time for one test vs whole suite!)
Lesson 2: Testing Frameworks
Lesson 3: Jenkins
Jenkins is a CI/CD tool, but it is used to force the running of automated tests as part of the build process, so we have included it in this section.
Jenkins on Wikipedia.
- A Crash Course in Continuous Testing
- The Future of Continuous Testing: Fail Faster
Design for a Python-based spell checker
(We want one of these for our web pages! We will try to build it.)
- Setting up Jenkins as a webhook in GitHub
- Slack notification plugin integration with Jenkins
- Testing and Continuous Integration Part 1
- Testing and Continuous Integration Part 2
- Testing only recently changed git files in jenkins