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

Carrying out performance testing

Even though it's not related to verifying the correctness of software, a performance test suite is part of the testing strategy for many applications. Usually, they are expected to assess the performance of the software in terms of how fast it can do its job and how many concurrent users it can handle.

Due to their nature, performance tests are usually very expensive as they have to repeat an operation multiple times to get a benchmark that is able to provide a fairly stable report and absorb outliers that could have taken too long to run just because the system was busy doing something else.

For this reason, the performance test suite is usually only executed after all other suites are passed (also, it doesn't make much sense to assess how fast it can test the software when we haven't checked that it actually does the right thing).

For our chat example, we could write a benchmark suite that verifies how many messages per second we are able...