Member-only story

Continuous Testing Clarified

Continuous Testing is the most important process in DevOps; Yet most so-called ‘Agile’ or ‘DevOps’ projects did not have it or got it wrong.

Zhimin Zhan

Non-Medium-Members: you can view this article free on Vocal Media.

This article is one of the “IT Terminology Clarified” series.

According to Wikipedia, 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.” The keywords are “automated tests”, “delivery pipeline”, “immediate feedback” and “software release candidate”. (The reason I quote Wikipedia, a non-academic reference, for definitions: because Continuous Testing is new, and there is a lot of confusion over it. So I reach for a common understanding at Wikipedia)

Table of Contents:· Continuous Testing explained in simple words
·
Continuous Testing is the Holy Grail of Software Development
·
Software Development Trend ⇒ Continuous Testing
·
Continuous Testing vs DevOps
·
Continuous Testing vs Continuous Integration
·
If CI is implemented properly, no need for CD or CT
·
Continuous Delivery is really about testing
·
Reality Check of CT/DevOps

Create an account to read the full story.

The author made this story available to Medium members only.
If you’re new to Medium, create a new account to read this story on us.

Or, continue in mobile web

Already have an account? Sign in

Responses (1)

What are your thoughts?

Yes, I have seen this DevOps image several times. But I've never understood how to release software that has not yet been deloyed. The point in Cont Delivery is that changes are deployed and then later released to users by a separate decision.