Files
magnus919_agent-skills/qa-methodology/references/regression-testing.md
T
Magnus HedemarkandGitHub c7c4d3b74f Port 11 methodology skills from hermes-profiles (#69)
Engineering: backend-engineering, frontend-engineering, data-engineering,
ml-engineering, platform-engineering, qa-methodology

Executive: go-to-market, legal-strategy, operational-design, org-design,
product-strategy

ml-engineering: added missing training-infrastructure.md reference
qa-methodology: added test-data-management, performance-testing,
security-testing references

All frontmatter converted to agent-skills convention.
Source: https://github.com/magnus919/hermes-profiles
2026-07-21 00:58:26 -04:00

1.4 KiB

Regression Testing

What Belongs in a Regression Suite

Include Exclude
Every fixed bug (as a test) Tests that haven't failed in 6+ months (archive)
Critical user paths Tests for deprecated features
Known failure patterns Tests that overlap with lower-level coverage
API contract checks Visual regression tests for work-in-progress UI
Data integrity assertions Performance tests (separate suite)

Suite Hygiene

Condition Action
Test hasn't failed in 6 months Consider archiving — it may not be testing anything meaningful
Test flakes > 1% over 10 runs Investigate and fix or remove immediately
Test takes > 5s (unit) / > 30s (integration) Optimize or promote to slower tier
Test depends on another test's state Fix isolation — tests must be independent
Test runs against production data Switch to synthetic fixtures

Change-Based Test Selection

Not every change needs the full regression suite. For targeted changes:

Change Type Required Tests
Bug fix Test that reproduces the bug + related unit tests
Feature addition New feature tests + smoke tests on adjacent areas
Refactoring Full unit suite + integration smoke tests
Configuration change Smoke tests on affected components
Dependency update Full regression suite
Infrastructure change Integration + E2E suite