Low-level Test Case
A low-level test case provides detailed execution steps, input data, expected results, and prerequisites needed to perform a specific test consistently.
“A test case with concrete values for preconditions, input data, expected results, postconditions, and a detailed description of actions (where applicable).”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Low-level Test Case?
Low-level test cases leave little room for interpretation, making them suitable for repeatable manual testing and test automation.
Detailed procedure: Every execution step is documented.
Repeatability: Different testers can execute the same test consistently.
Automation support: Detailed cases are easier to convert into automated scripts.
Real World Example
A regulated product team is preparing a release where Low-level test case appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Low-level test case as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Low-level test case and similar ideas.
The page becomes useful in practice because Low-level test case is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Low-level test case in the context of ISTQB terminology?
Question 2
A tester needs to explain Low-level test case to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Low-level Test Case. Test your understanding with topic-specific questions in our Mock Exams.