QA Engineering Standards

How the QA Engineer team tests and documents its work. Short on purpose: each page tells you what to do, with a real example.

11 Sections · Oct 2026 Last updated · Drafting Document status

Our stack in one line

Backend and data pipelines → pytest. Frontend → Playwright. Stress & load → Locust. AI prompts → consistency + accuracy. Everything documented in Kiwi TCMS.

Pages

• 1. Introduction: Scope, tools, and who owns what.
• 2. Writing Test Cases: The template, naming, and what to cover.
• 3. Backend Testing (pytest): How we test APIs and async functions.
• 4. Frontend Testing (Playwright): How we test the UI.
• 5. Data Pipeline Testing: Every task lands correctly, failures stop the pipeline, alerts are sent.
• 6. Stress & Load Testing (Locust): Load, stress, spike, soak, and recovery.
• 7. AI Prompt Testing: Consistency and accuracy, with an AI judge.
• 8. Kiwi, Results & Bugs: Documenting in Kiwi, result statuses, bugs, and release sign-off.
• 9. Appendix: Glossary and change log.
• 10. Smoke Tests in CI/CD: Run smoke tests automatically after every deploy, and stop the pipeline when they fail.
• 11. AI Standards Review in CI/CD: Proposal: Abangku skills review each change and failed smoke runs, recommend fixes, and block on Blockers.

Too lazy to read?

Pass the page URL to your AI tool:

Read https://swe.ardhiraka.com/qa/2-test-cases
and https://swe.ardhiraka.com/qa/3-backend-testing,
then write test cases and a pytest test for the requirement below.

Every page is also available as plain markdown at /qa/{slug}.md, indexed in /qa/llms.txt.