Test level
A group of test activities organized and managed together, e.g. component, integration, system, and acceptance testing.
Syllabus chapters: 2
Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.
Related terms
Test level in a practice question
Question 1
When does test analysis and design for a given test level begin?
- When the previous test level has met its exit criteria
- During the corresponding development phase of the SDLC
- Once the work product for that test level has been approved
- At the start of test execution for that test level
Show answer
- When the previous test level has met its exit criteriaExit criteria feeding the next level's entry criteria describes how levels relate in sequential models.
- Correct answer: During the corresponding development phase of the SDLCAnalysis and design begin during the corresponding development phase, supporting early testing.
- Once the work product for that test level has been approvedTesters are involved as soon as drafts are available; approval is not the trigger.
- At the start of test execution for that test levelBeginning at execution would defer analysis and design past the point early testing requires.
Among the good testing practices that hold independently of the chosen SDLC model, test analysis and design for a given test level begin during the corresponding development phase of the SDLC, so that testing can adhere to the principle of early testing.
Syllabus section 2.1.2
Question 2
A team currently runs its performance tests only once the whole system has been assembled in a representative test environment. Which change would achieve shift left?
- Begin non-functional testing at the component test level wherever that is possible
- Run the full regression suite immediately after each release to production
- Complete the static analysis of the source code only once dynamic testing has begun
- Assign a dedicated independent test team to the later test levels
Show answer
- Correct answer: Begin non-functional testing at the component test level wherever that is possibleMoving non-functional testing down to component level is a named shift-left practice.
- Run the full regression suite immediately after each release to productionTesting after release moves activity later, which is the opposite direction.
- Complete the static analysis of the source code only once dynamic testing has begunStatic analysis should be completed prior to dynamic testing, not after it starts.
- Assign a dedicated independent test team to the later test levelsStaffing the later levels moves no test activity earlier in the SDLC.
Performing non-functional testing starting at the component test level, where possible, is named among the good practices that achieve shift left, precisely because these non-functional test types tend otherwise to be performed late in the SDLC when a complete system and a representative test environment are available — which is the situation described.
Syllabus section 2.1.5
Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.