← All ISTQB Flashcard Decks

Test Levels and Types Flashcards

7 cards from real ISTQB 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 Levels and Types flashcards as text
  1. Which test level focuses on verifying that individual components work correctly together?

    Answer: Integration testing

    Integration testing verifies that components or systems interact correctly with each other, focusing on interfaces and interactions.

  2. Who typically performs unit (component) testing according to ISTQB?

    Answer: Developers

    Unit testing is typically performed by the developers who wrote the code, using white-box techniques to test individual components in isolation.

  3. What is the primary objective of system testing?

    Answer: Verify the complete integrated system meets specified requirements

    System testing evaluates the complete integrated system to verify it meets the specified functional and non-functional requirements.

  4. Which test level is most closely associated with validating that a system meets business processes and user workflows?

    Answer: User acceptance testing (UAT)

    UAT validates that the system meets the needs of users and stakeholders by testing it against real business scenarios and workflows.

  5. In integration testing, what is a 'stub'?

    Answer: A simplified replacement for a called component

    A stub is a simplified implementation that replaces a called (lower-level) component, allowing the calling component to be tested in isolation.

  6. Which ISTQB statement about test levels is MOST accurate?

    Answer: Each test level has its own specific test objectives and test basis

    ISTQB defines each test level by distinct test objectives, a specific test basis, test objects, typical defects, and appropriate techniques.

  7. At which test level are user stories most commonly used as the test basis in Agile development?

    Answer: Acceptance testing

    In Agile, acceptance testing often uses user stories and acceptance criteria as the test basis to validate business value from the user's perspective.