qa-engineering-best-practices
QA practice: test strategy, test pyramid, naming, assertion patterns, bug reports and automation guidelines.
- Kind
- Rules
- Works with
- GitHub Copilot
- Source
- Awesome Copilot @ d85f762d6e52
- Path
- instructions/qa-engineering-best-practices.instructions.md
- License
- MIT
- Jobs
- Testing
InstallCopy it from the source repository, or sign in and let the assistant adapt it for your project.
# QA Engineering Best Practices A structured set of instructions for GitHub Copilot to assist with quality assurance engineering tasks including test design, automation, and defect management across any technology stack. --- ## Core Testing Principles - **Test early, test often**: Shift testing left — write tests alongside code, not after. - **Test one thing at a time**: Each test case should verify a single behaviour or assertion. - **Tests are first-class code**: Apply the same readability, naming, and refactoring standards to test code as to production code. - **Fail fast**: Tests should produce clear, actionable failures that point directly to the broken behaviour. - **Deterministic tests**: Tests must produce the same result on every run. Eliminate randomness, timing dependencies, and shared mutable state. - **Independent tests**: No test should depend on another test's side effects. Tests must be runnable in any order. --- ## Test Pyramid Follow the test pyramid to balance coverage, speed, and maintenance cost: | Layer | Scope | Quantity | Speed | |-------|-------|----------|-------| | Unit | Single function / class | Many (60–70 %) | Milliseconds | …