Mettl Test Design & Development 3 — Questions and Answers
Question 1: What distinguishes a test scenario from a test case?
- A test scenario is more detailed and includes step-by-step actions
- A test scenario describes what to test at a high level while a test case details exact steps and expected results (Correct answer)
- A test scenario is used only in agile projects
- A test case is created before a test scenario
Correct answer: A test scenario describes what to test at a high level while a test case details exact steps and expected results
Test scenarios are high-level descriptions of what functionality to test, while test cases specify the exact inputs, steps, and expected outcomes.
Question 2: In exploratory testing, what is a 'test charter'?
- A document listing all defects found during a session
- A brief mission statement defining the scope and goals of a testing session (Correct answer)
- A formal test plan approved by stakeholders
- A checklist of regression test cases
Correct answer: A brief mission statement defining the scope and goals of a testing session
A test charter guides exploratory testing sessions by defining what to explore, how to explore it, and what to observe.
Question 3: Which of the following is a key advantage of using pairwise (all-pairs) testing?
- It guarantees 100% code coverage
- It reduces the number of test cases while covering all combinations of two parameters (Correct answer)
- It tests every possible input combination
- It is only applicable to UI testing
Correct answer: It reduces the number of test cases while covering all combinations of two parameters
Pairwise testing ensures every pair of parameter values is tested at least once, significantly reducing test case count without sacrificing coverage.
Question 4: When would you use Risk-Based Test Design over exhaustive testing?
- When time and resources are unlimited
- When all features have equal importance and complexity
- When time is limited and you need to prioritize tests based on likelihood and impact of failure (Correct answer)
- When the product has no prior defect history
Correct answer: When time is limited and you need to prioritize tests based on likelihood and impact of failure
Risk-Based Testing prioritizes test effort toward areas with the highest probability of failure and greatest business impact when resources are constrained.
Question 5: What is the main difference between a test plan and a test strategy?
- A test plan is project-specific while a test strategy is a high-level organizational document (Correct answer)
- A test plan is written by developers while a test strategy is written by testers
- A test plan covers automation only while a test strategy covers manual testing
- There is no difference; the terms are interchangeable
Correct answer: A test plan is project-specific while a test strategy is a high-level organizational document
A test strategy defines the overall testing approach for the organization, while a test plan is project-specific and includes schedule, scope, and resources.
Question 6: Which Mettl assessment feature directly supports adaptive difficulty in test design?
- Static question banks with fixed order
- Item Response Theory (IRT)-based scoring that adjusts item difficulty based on candidate responses (Correct answer)
- Multiple-choice-only question formats
- Fixed time limits regardless of performance
Correct answer: Item Response Theory (IRT)-based scoring that adjusts item difficulty based on candidate responses
Mettl uses IRT-based adaptive testing to deliver questions at appropriate difficulty levels based on ongoing candidate performance.
Question 7: A negative test case is best described as:
- A test that expects the system to crash
- A test that verifies the system handles invalid, unexpected, or out-of-range inputs gracefully (Correct answer)
- A test that runs only after all positive tests fail
- A test with no expected result defined
Correct answer: A test that verifies the system handles invalid, unexpected, or out-of-range inputs gracefully
Negative testing validates that the system rejects bad inputs and handles errors appropriately without crashing or behaving unexpectedly.
What distinguishes a test scenario from a test case?