IT:AD: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.

For Continuous Testing, the scope of testing extends from validating bottom-up requirements or user stories to assessing the system requirements associated with overarching business goals.

“The widespread culture of Agile development has accelerated development while software testing still lags behind, forcing organizations to cut corners in QA or slow down Dev processes entirely” 1).

The Continuous Testing strategy fosters a company-wide cultural change to achieve four capabilities: * Test early, * test faster, * test often * automate.

Continuous Testing is a prerequisite for IT:AD:Continuous Integration.


class "Version Control Service" as VCS
class "Build Automation" as BA
class "Continuous Integration" as CI << <&cog> >>
class "Continuous Delivery" as CDEL << <&cog> >>

note left of CDEL
Process maturity heavily
affects the level of
conformance to
Continuous Delivery (CD).
Automation of Static+Dynamic
Security, Performance,
Compliance, Functional,
Post-Deployment Tests
range from 0 to 100%.

class "(Functional) Test Automation" as TA
class "Continuous Testing" as CT << <&cog> >>
class "Continuous Accredited Delivery" as CAL << <&cog> >> #E0E0E0

note left of CAL
Depends on 100%
conformance to
Continuous Delivery

class "Continuous Deployment" as CDEP << <&cog> >>
class "Unit/Static/Dynamic Tests" as ST

CI .UP.> VCS : uses
BA <|-RIGHT- CI : improves
CI <|-DOWN- CDEL : improves
CI <|-RIGHT- CT : improves
CT <|-DOWN- CDEP : improves
CT .UP.> TA : uses

CDEL ..> CT : may use\nsome or\nall of

CDEL <|-DOWN- CAL : improves

ST <.. CI : may use
ST <.. CDEL: uses