In this chapter, you looked at some popular third-party tools to help us improve our TDD practice. Some of the tools such as py.test
and trial
are test runners with some unique features. Others such as sure
and pyhamcrest
are libraries that help us write cleaner tests. You looked at how we can integrate our unit tests into the wider development process: from putting them into the build environment and integrating with continuous integration tools, to enabling the test
command when packaging our code. We then took a look at how we can maintain a package against multiple versions of Python and integrating tests into Sphinx so that our documentation doesn't break.

Test-Driven Python Development
By :

Test-Driven Python Development
By:
Overview of this book
This book starts with a look at the test-driven development process, and how it is different from the traditional way of writing code. All the concepts are presented in the context of a real application that is developed in a step-by-step manner over the course of the book. While exploring the common types of smelly code, we will go back into our example project and clean up the smells that we find.
Additionally, we will use mocking to implement the parts of our example project that depend on other systems. Towards the end of the book, we'll take a look at the most common patterns and anti-patterns associated with test-driven development, including integration of test results into the development process.
Table of Contents (20 chapters)
Test-Driven Python Development
Credits
About the Author
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Getting Started with Test-Driven Development
Red-Green-Refactor – The TDD Cycle
Code Smells and Refactoring
Using Mock Objects to Test Interactions
Working with Legacy Code
Maintaining Your Test Suite
Executable Documentation with doctest
Extending unittest with nose2
Unit Testing Patterns
Tools to Improve Test-Driven Development
Answers to Exercises
Working with Older Python Versions
Index
Customer Reviews