Continuous testing

Continuous testing checks every change as early as possible and keeps the results as evidence for whoever has to authorize the release.

The test pyramid

Many fast unit tests at the base, fewer integration tests in the middle and a small number of end-to-end tests at the top. The pyramid keeps feedback fast and failures easy to locate.

Shift left

Testing earlier is cheaper: a defect found in the pull request costs minutes, the same defect found in production costs an incident.

Acceptance in each environment

  • QA certification before the change moves on.
  • Acceptance in pre-production before asking for production.
  • A verification in production once it is installed.

How DevGob applies it

DevGob records QA, pre-production and production test results on the Deployment, and requires an accepted result before each gate; a failed test can open a linked bug.

Read it in the documentation

Related topics

DevOps automation Automate first what is repetitive, error-prone and frequent: builds, tests, deployments and the links between the work and the code. Continuous delivery Continuous delivery keeps every change ready to release: built, tested and deployable at the push of a button, in small and frequent batches. DevSecOps: security in the pipeline DevSecOps builds security into every stage of delivery: scanning code and dependencies, limiting access and keeping an audit trail of every change.

DevOps with governance, on one record

DevGob plans the work and governs every change on its way to production: backlog, sprints, committee authorizations, install evidence and an audit trail.

Request a workspace Documentation