Everything for QA Engineers
QA engineers write bug reports and test plans read by everyone on the team, so precision matters more than in almost any other role. This hub pulls together the testing vocabulary, grammar for clear defect writing, and every interview and blog resource tagged QA or testing.
Vocabulary sets
Grammar & writing
Interview prep
Blog articles (1)
- API Mocking English: MSW v2 and Testing Vocabulary
Learn the English vocabulary of API mocking with MSW v2 — request handlers, interceptors, stubs, fixtures, and network boundary — for clearer testing discussions.
Other role hubs
Explore more
Browse every exercise category, or search the full site.
Frequently Asked Questions
What's the difference between 'Test Case' and a 'Test Scenario' in QA?
A Test Scenario describes a high-level user goal or feature interaction, outlining the expected behavior from the user's perspective. A Test Case is a detailed set of steps, preconditions, and expected results designed to verify a specific aspect of that scenario – it breaks down the larger scenario into executable actions.
I'm seeing 'Exploratory Testing'. How does this differ from scripted testing?
Exploratory Testing is an unscripted approach where QA engineers simultaneously learn, design tests, and execute them based on their experience and intuition. It's valuable for uncovering unexpected issues not anticipated by formal test plans and is often used after initial scripted testing.
What exactly are 'Test Doubles' (mocks, stubs, dummies) and when do I use them?
Test doubles are simulated objects used during unit testing to isolate the code under test. Mocks replace dependencies with controlled behavior for verifying interactions; Stubs provide pre-defined responses; Dummies are simpler replacements that mimic the basic interface but don't have complex logic.
Can you explain 'Regression Testing' in the context of continuous integration?
Regression testing is the process of re-running previously executed tests after code changes to ensure that new features haven't introduced unintended defects into existing functionality. In CI, automated regression suites are triggered with every commit to quickly identify and address regressions.
What's 'Shift Left Testing' and how does it relate to a QA Engineer?
Shift Left testing advocates for incorporating quality activities earlier in the development lifecycle, ideally during design or requirements gathering. A QA engineer plays a key role by validating assumptions, identifying risks, and providing feedback throughout these phases, preventing issues from escalating later.
What's the purpose of 'Test Coverage Analysis', and what metrics do I look for?
Test coverage analysis measures the extent to which your test suite executes the source code. Key metrics include statement coverage, branch coverage, and path coverage – aiming for high coverage ensures a greater proportion of the codebase has been validated.
I keep hearing about 'Test Automation'. What types of tests can be automated?
Test automation primarily focuses on automating repetitive tasks like regression testing, API testing, and UI functional testing. It's less suitable for exploratory testing or complex scenarios requiring human judgment but significantly increases efficiency over time.
What is 'Black Box Testing', versus 'White Box Testing'?
'Black box testing' evaluates a system's functionality without knowledge of its internal structure or code. 'White box testing', conversely, requires testers to understand the internal logic and design of the software to create tests that cover specific code paths.
How do I write effective 'Bug Reports'? What information is most important?
A good bug report includes a clear summary, precise steps to reproduce the issue, the expected result, and the actual observed result. Including screenshots or videos significantly aids developers in understanding and fixing the defect quickly.
What is 'Performance Testing' and what are common types?
Performance testing evaluates a system's speed, stability, and scalability under various conditions. Common types include Load testing (simulating user traffic), Stress testing (pushing the system beyond its limits), and Endurance testing (testing prolonged usage).