Continuous-integration (CI) systems, such as Jenkins, are frequently used to launch tests after each of the code commits. This is one of the major benefits of using a CI system. Imagine that there is an invisible engineer who is always watching for any change in the network; upon detecting change, the engineer will faithfully test a bunch of functions to make sure that nothing breaks. Who wouldn't want that?
Let's look at an example of integrating pytest into the Jenkins tasks.
Get Mastering Python Networking - Second Edition now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.
Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.
Start your free trial Become a member now