Quality Engineering: systematic approach to software quality | Guide for developers

Quality Engineering: A Systematic Approach to Integrating Quality into the Software Development Lifecycle

Quality Engineering (QE) is not a set of tools, but a strategic discipline that integrates quality into every stage of software development. Unlike traditional testing, which focuses on detecting defects after implementation, QE eliminates problems at the design stage, reducing technical debt and accelerating time to market. For middle/senior developers, this means transitioning from reactive to proactive processes, where quality becomes an integral part of the architecture, rather than a stage at the end of the cycle.

From Metaphysics to Metrics: How to Define Quality in the Digital Age

Software quality is a multifaceted concept. As Robert Pirsig noted in "Zen and the Art of Motorcycle Maintenance," it's hard to formalize, but engineering requires measurability. Modern standards highlight two key aspects:

• Functional quality: compliance with requirements (for example, correct payment processing in a fintech application).
• Structural quality: non-functional characteristics (reliability, security, performance).

A critical mistake many teams make is ignoring structural quality. For example, an application might perform all functions but crash under peak load due to unoptimized DB queries. QE solves this by implementing metrics at early stages: static code analysis, load testing in the CI/CD pipeline, production monitoring.

Functional vs Structural Quality: The Two Pillars of QE

Functional quality is measured through:

• Test case coverage (minimum 70% for critical modules)
• Number of bugs in production after release
• Compliance with specifications in acceptance tests

Structural quality is assessed by:

• Mean Time to Recovery (MTTR) after failures
• Defect density per 1000 lines of code
• Technical debt level (analysis via SonarQube)

Practical example: In a project for a banking client, the team implemented automated security scanning at the build stage. This reduced vulnerabilities in releases by 65%, but required architecture review—integrating OWASP ZAP into the pipeline revealed issues in legacy modules requiring refactoring.

How Data Changes the Approach to Quality

QE turns quality from a subjective assessment into a manageable process through data. Key metrics are divided into two categories:

• Business-oriented (long-term):

- NPS (Net Promoter Score)

- User churn rate due to bugs

- ROI from reducing cost of quality

• Operational (short-term):

- Test suite execution time

- Percentage of automated tests

- Number of manual checks per release

It's important to avoid the "metrics trap": for example, high test coverage doesn't guarantee absence of critical bugs if tests check insignificant scenarios. An effective QE approach requires correlating metrics: a decrease in defect density must be backed by increased user satisfaction.

Case Study: When a Design Error Spawned a Mythical Employee

Real case from practice: A company with 1000+ consultants had a critical error in its time-tracking system. In the user selection form, the "Name" field was a dropdown list with the first entry—Amy Adams—selected by default. Employees who forgot to select themselves automatically billed under her name. The administrator, trying to fix the issue, created a fake employee "A. Trubkozub," who weekly became "employee of the month" with 300+ hours.

Root cause: lack of QE at the design stage. Solution included:

• Automatic user identification via SSO
• Data validation on client and server
• Anomaly monitoring in billing data

This case demonstrates how a proactive quality approach prevents business risks. Quality engineers at the requirements analysis stage should have identified the cognitive load on users when selecting from the list.

Key Points

• QE replaces "quality as a stage" with "quality as a process": testing shifts left, integrating into development.
• Metrics must correlate with business goals: reducing defects is not an end in itself, but a means to boost NPS and cut cost of quality.
• Quality engineers are architects of reliability: their role includes designing testable architecture, not just writing tests.
• Automation is a tool, not the goal: 80% of QE efforts should prevent defects, 20% detect them.

Who Is a Quality Engineer in the DevSecOps Era

A modern quality engineer (SDEqT) is a hybrid of developer, tester, and DevOps engineer. Key competencies:

• Architectural influence: participation in design reviews to spot quality risks (e.g., monolith vs microservices).
• Tool expertise: pipeline setup with SAST/DAST integration, AI-generated test data.
• Metrics literacy: building dashboards linking technical metrics to business KPIs.

Example code for quality integration in CI/CD:

quality_gate:
  stage: test
  script:
    - sonar-scanner -Dsonar.qualitygate.wait=true
    - owasp-zap-cli full-scan -t https://app.example.com
  rules:
    - if: $CI_COMMIT_BRANCH == "main"
      when: always

This stage blocks merge to main on quality gate failure, following the "fail fast" principle. However, tune thresholds: critical vulnerabilities (CVSS > 9.0) halt the pipeline, low-severity generate alerts.

Conclusion: QE as a Driver of Business Advantages

Quality Engineering has evolved from niche practice to necessity for products competing globally. Teams adopting QE achieve:

• 40-60% reduction in production bug fix time
• Faster releases with maintained stability
• Lower cost of quality via early detection

Key challenge: mindset shift—quality isn't "QA's job." It's cross-functional collaboration, with quality engineers guiding best practices across the SDLC.

— Editorial Team