Book Image

Crafting Test-Driven Software with Python

By : Alessandro Molina
Book Image

Crafting Test-Driven Software with Python

By: Alessandro Molina

Overview of this book

Test-driven development (TDD) is a set of best practices that helps developers to build more scalable software and is used to increase the robustness of software by using automatic tests. This book shows you how to apply TDD practices effectively in Python projects. You’ll begin by learning about built-in unit tests and Mocks before covering rich frameworks like PyTest and web-based libraries such as WebTest and Robot Framework, discovering how Python allows you to embrace all modern testing practices with ease. Moving on, you’ll find out how to design tests and balance them with new feature development and learn how to create a complete test suite with PyTest. The book helps you adopt a hands-on approach to implementing TDD and associated methodologies that will have you up and running and make you more productive in no time. With the help of step-by-step explanations of essential concepts and practical examples, you’ll explore automatic tests and TDD best practices and get to grips with the methodologies and tools available in Python for creating effective and robust applications. By the end of this Python book, you will be able to write reliable test suites in Python to ensure the long-term resilience of your application using the range of libraries offered by Python for testing and development.
Table of Contents (18 chapters)
1
Section 1: Software Testing and Test-Driven Development
6
Section 2: PyTest for Python Testing
13
Section 3: Testing for the Web
16
About Packt

Enabling continuous integration

Wouldn't it be convenient if someone else was in charge of running all our tests every time we made a change to our code base? This would mean that we couldn't forget to run some specific tests just because they were related to an area of the code that we were not directly touching.

That's exactly the goal of Continuous Integration (CI) environments. Every time we push our changes to the code repository, these environments will notice and rerun the tests, usually merging our changes with the changes from our colleagues to make sure they cope well together.

If you have a code repository on GitHub, using Travis as your CI is a fairly straightforward process. Suppose that I made an amol-/travistest GitHub project where I pushed the code base of our chat application; to enable Travis, the first thing that I have to do is to go to https://travis-ci.com/ and log in with my GitHub credentials:

Figure 4.1 – Travis CI Sign in page

Once we...