Testing, Quality & Reliability Topics
Quality assurance, testing methodologies, test automation, and reliability engineering. Includes QA frameworks, accessibility testing, quality metrics, and incident response from a reliability/engineering perspective. Covers testing strategies, risk-based testing, test case development, UAT, and quality transformations. Excludes operational incident management at scale (see 'Enterprise Operations & Incident Management').
Monitoring, Logging, and Observability
Understanding running systems through their signals. Covers metrics, logs, and traces, instrumentation, dashboards, alerting design, and log analysis and correlation for debugging production. Emphasizes designing observability so problems are detectable and diagnosable before users are affected.
Test Infrastructure, Environments, and Parallel Execution
The systems that run tests: environments, orchestration, scheduling, and scaling execution. Covers designing test environments, parallel execution and sharding for speed, test orchestration, and building internal tooling and infrastructure for testing. Includes test result aggregation infrastructure and execution monitoring.
Flaky Test Management and Test Reliability
Detecting, isolating, and eliminating non-deterministic tests. Covers root-causing flakiness, quarantine and remediation systems, distinguishing product bugs from test bugs, and maintaining suite health over time. Emphasizes keeping automated suites trustworthy so failures mean something.
Test Coverage Analysis and Optimization
Measuring and improving how thoroughly tests exercise the system: code coverage, requirement coverage, and gap analysis. Covers interpreting coverage metrics without gaming them, identifying under-tested areas, and optimizing a suite for signal versus redundancy. Includes when high coverage is and is not meaningful.
Assertions and Behavior Verification
Choosing what to assert and how to verify behavior meaningfully. Covers assertion strategy, verifying observable behavior over implementation detail, avoiding weak or over-specified assertions, and using assertion libraries effectively. Emphasizes assertions that fail for the right reasons and give a clear diagnosis.
SLIs, SLOs, SLAs, and Error Budgets
Defining and operating reliability targets. Covers choosing service level indicators, setting service level objectives and agreements, computing and spending error budgets, and using them to drive engineering decisions. Includes negotiating reliability targets with stakeholders.
Non-Functional Testing
Testing quality attributes beyond correctness: reliability, usability, compatibility, maintainability, and other non-functional requirements. Covers identifying non-functional requirements, designing checks for them, and awareness of where functional testing is insufficient. Serves as the umbrella for quality attributes not covered by a dedicated topic.
Test Case Design and Edge Case Analysis
Systematically deriving the cases, inputs, and conditions most likely to expose defects. Covers formal test-design techniques (equivalence partitioning, boundary value analysis, decision tables, state transitions, and pairwise/combinatorial design) and writing clear, maintainable test cases with documented expected results. Also covers the edge-case mindset: boundary conditions, invalid and unexpected inputs, corner cases, and the attention to detail that anticipates failures when validating complex behavior.
Test Levels and the Test Pyramid
How unit, integration, component, end-to-end and contract tests fit together and where each provides the most value. Covers the test pyramid and the competing shapes proposed against it (the testing trophy and the honeycomb), multi-layer test architecture, contract testing as the seam between services, choosing the right level to catch a given class of defect cheaply, and what to run per commit versus per release. Includes the cost and confidence trade-offs between fast low-level tests and slower, broader system tests. The scope is which level a test belongs at and why. Deciding how much to invest in testing and where to prioritize under time pressure is covered separately.