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.