Test Design & Development Flashcards
7 cards from real Mettl practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 7 Test Design & Development flashcards as text
What distinguishes a test scenario from a test case?
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.
In exploratory testing, what is a 'test charter'?
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.
Which of the following is a key advantage of using pairwise (all-pairs) testing?
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.
When would you use Risk-Based Test Design over exhaustive testing?
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.
What is the main difference between a test plan and a test strategy?
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.
Which Mettl assessment feature directly supports adaptive difficulty in test design?
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.
A negative test case is best described as:
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.