Chapter 1 - Continuous Testing

Continuous testing is the process of executing automated tests as part of the software delivery pipeline to obtain immediate feedback on the business risks associated with a software release candidate.

That’s the definition of CT, but we have the definition of Bas DIjkstra

Continuous testing is the process that allows you to get valuable insights into the business risks associated with delivering application increments following a CI/CD approach. No matter if you're building and deploying once a month or once a minute, CT allows you to formulate an answer to the question, 'Are we happy with the level of value that this increment provides to our business, stakeholders, end users?' for every increment that's being pushed and deployed in a CI/CD approach.

Why should we care about testing in every step?

• You get feedback at any stage, therefore the automated tests need to be included in the build pipeline, and the build needs also to fail as soon as problems are detected.
• You can continuously learn about your product, and the quality expected.
• Consequently, it's also speeding up development by reducing blocked time, and it's also limiting a work in progress and the context which is needed. This way you can benefit from potential earlier releases, and therefore, you also have a faster time to market.
• Continuous testing also increases confidence we're going in the right direction. Therefore, we reduce waste by learning early.
• Not to forget, all these benefits increase team morale.

Too much text

Chapter 2 - The Whole Team Approach