Book Image

Learning Python Testing

By :
Book Image

Learning Python Testing

By:

Overview of this book

<p>Automated testing is the best way to increase efficiency and decrease the defects of software testing. It takes away much of the effort on your part so that you can find bugs early and easily. The Python unit testing framework makes it easy to write efficient automated test cases in Python. Applications involving many paradigms and styles can be very complicated to test, but with the right tools, testing becomes the simplest part of the development process.</p> <p>This book starts with a short introduction to testing, and then introduces the doctest tool, both in terms of practicalities and how it fits into the testing environment. From there, the discussion proceeds to unittest.mock and mock objects, and to unittest. Next, Nose is introduced and discussed. Later on, focus turns from the tools themselves toward best practices and disciplines of testing. Finally, the integration of testing with existing build processes and toolchains is covered. By the end of this book, you will know how to use automated testing quickly and easily and in a way that helps catch bugs early and fix them.</p>
Table of Contents (16 chapters)
Learning Python Testing
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Index

Nose and doctest tests


Nose doesn't just support doctest, it actually enhances it. When you're using Nose, you can write test fixtures for your doctest files.

If you pass --doctest-fixtures=_fixture on the command line, Nose will go looking for a fixture file whenever it finds a doctest file. The name of the fixture file is based on the name of the doctest file, and is calculated by appending the doctest fixture suffix (in other words, the value of doctest-fixtures) to the main part of the doctest filename, and then adding .py to the end. For example, if Nose found a doctest file called PID.txt, and had been told to find doctest‑fixtures=_fixture, it would try to find the test fixture in a file called PID_fixture.py.

The test fixture file for a doctest is very simple: it's just a Python module that contains a setup() or setUp() function, and a teardown() or tearDown() function. The setup function is executed before the doctest file, and the teardown function is executed after the doctest file...