Software quality management
Manage software quality across the delivery flow: acceptance tests per environment, QA certification, defects linked to their change and rework metrics.
2 min read
Quality is measured where changes move
Software quality is not only the number of bugs. It is whether each change meets its acceptance criteria, passes its tests in every environment and stays in production without being rolled back.
Practices that raise quality
- Acceptance criteria written with the requirement, not after it.
- Code review before testing, not after release.
- Tests in a QA environment, then in pre-production, then in production.
- Defects found before release recorded apart from production bugs.
- Rework measured, so recurring problems become visible.
Quality controls in DevGob
- QA certification, pre-production and production test results on each change.
- An acceptance test required before the change leaves each test stage.
- Results recorded as success, success with observations or failed, with evidence.
- Pre-release defects and bugs linked to the deployment that produced them.
- A production rollback automatically opens a severity-1 bug.
- Test pass rate, deployment success rate and rework count in the reports.
How DevGob helps
DevGob ties every test result and defect to the change it belongs to, so quality is visible per release and over time.
Read it in the documentationFrequently asked questions
Does DevGob run automated tests?
No. Automated tests run in your pipeline; DevGob shows the CI runs and records the acceptance results and the evidence of each environment.
How are defects classified?
Pre-release defects are found before production; bugs hang from the deployment that caused them, and a production rollback creates one automatically.
Which quality metrics are available?
Test pass rate, deployment success rate (changes completed without a production rollback), rework count and on-time delivery.
Keep reading
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.