From the course: Software Testing Foundations: Continuous Testing and DevOps

Intro to continuous testing - Jenkins Tutorial

From the course: Software Testing Foundations: Continuous Testing and DevOps

Start my 1-month free trial

Intro to continuous testing

“

- [Instructor] So you've established reliable automated testing for your project. That's great. Why should you make continuous testing your next goal? Well, because it helps both you and your team do their jobs better. Continuous testing means running your tests in a dedicated testing solution and not just on developers' workstations. Running your tests in a dedicated solution means that your testing environment is pre-configured in a predictable way to reduce configuration errors. It also means being able to control the scheduling of your tests. You can run your tests at certain times of day or once every hour. You could also set your tests to run whenever certain conditions take place, like on code check-in or after deploying new code to a certain environment. If you run tests on multiple different browsers, a practice often called cross-browser regression testing, you can arrange for those tests to be scheduled during off peak hours so that they won't disrupt the normal development workflow. You can also have reports of your test results generated and saved for later use. If they're saved online, it's much easier for other teammates to access them whenever they're needed. An archive of past test results is a great way to get a picture of application health over time. Offering continuous testing is also helpful for your developers. With a good continuous testing implementation your developers can run your automation whenever they need to. So if you want to take control of the scheduling of your tests, make test results more available to your whole team and make it easier for developers to test their own code, implementing continuous testing is the best choice for you.

Contents