liveBook · Manning

Non-production testing

As explained in Automating API Delivery

Non-production testing is the evaluation of software in environments other than production using user-oriented acceptance, performance, security, and related tests.

Non-production testing evaluates a release candidate in increasingly production-like environments from the user’s perspective, increasing confidence before production deployment. section 8.3

A pipeline can use non-production testing to:

  • Run acceptance tests, performance tests, security tests, and other organization-defined checks. section 8.3
  • Deploy release candidates through environments that progressively resemble production. section 8.3
  • Allow only candidates that pass the checks to proceed to production or an equivalent destination. section 8.3
Figure 8.3 The Acme team’s deployment pipeline
figure

The deployment-pipeline diagram helps locate non-production testing between release-candidate publication and production deployment. section 8.3

How Automating API Delivery covers it

How deep it goes
Defines user-oriented test categories and environment progression but defers detailed deployment-pipeline implementation.
Examples
Uses release candidates, API definition files, artifact repositories, and increasingly production-like pipeline environments.
What you can do after
Operate/configure a pipeline gate that tests release candidates before allowing production deployment.
How it connects
Connects acceptance testing, performance testing, security testing, artifact repositories, deployment pipelines, and production deployment.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Automating API Delivery. The section links point to the parts of the book it draws on.