- Learning Python Testing
- Table of Contents
- Learning Python Testing
- Credits
- About the Author
- About the Reviewers
- www.PacktPub.com
- Preface
- 1. Python and Testing
- 2. Working with doctest
- Where doctest performs best
- The doctest language
- Expecting exceptions
- Expecting blank lines
- Controlling doctest behavior with directives
- Ignoring part of the result
- Ignoring white space
- Skipping an example
- The other directives
- The execution scope of doctest tests
- Check your understanding
- Exercise – English to doctest
- Embedding doctests into docstrings
- Putting it into practice – an AVL tree
- Summary
- 3. Unit Testing with doctest
- 4. Decoupling Units with unittest.mock
- 5. Structured Testing with unittest
- The basics
- Assertions
- The assertTrue method
- The assertFalse method
- The assertEqual method
- The assertNotEqual method
- The assertAlmostEqual method
- The assertNotAlmostEqual method
- The assertIs and assertIsNot methods
- The assertIsNone and assertIsNotNone methods
- The assertIn and assertNotIn methods
- The assertIsInstance and assertNotIsInstance methods
- The assertRaises method
- The fail method
- Make sure you get it
- Test fixtures
- Summary
- 6. Running Your Tests with Nose
- 7. Test-driven Development Walk-through
- 8. Integration and System Testing
- 9. Other Tools and Techniques
- Index
The doctest uses the first blank line after >>> to identify the end of the expected output, so what do you do when the expected output actually contains a blank line?
The doctest handles this situation by matching a line that contains only the text <BLANKLINE> in the expected output with a real blank line in the actual output.
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.