← All CAD Flashcard Decks

CAD Test-Driven Development and Agile Testing Flashcards

6 cards from real CAD practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.

Read the first 6 CAD Test-Driven Development and Agile Testing flashcards as text
  1. What is the recommended maximum duration for a unit test suite to run in a TDD workflow?

    Answer: Under 10 seconds to a few minutes at most

    Unit test suites should run in seconds to a few minutes so developers get immediate feedback and run them frequently without interrupting their flow.

  2. What does the 'FIRST' acronym describe in the context of good unit tests?

    Answer: Fast, Isolated, Repeatable, Self-validating, Timely

    FIRST stands for Fast, Isolated/Independent, Repeatable, Self-validating, and Timely — the five properties that characterize well-written unit tests.

  3. In Agile, what is a 'test pyramid' used to represent?

    Answer: The recommended distribution of test types: many unit tests, fewer integration tests, fewest UI/end-to-end tests

    The test pyramid model recommends having a large base of fast unit tests, a middle layer of integration tests, and only a small number of slow end-to-end tests at the top.

  4. What is 'continuous testing' in an Agile/DevOps pipeline?

    Answer: Automatically executing tests at every stage of the delivery pipeline to provide immediate feedback

    Continuous testing is the practice of automatically running tests at each pipeline stage — commit, build, integration, staging — so issues are caught as early as possible.

  5. Which Agile testing strategy places business-facing, exploratory, and usability tests in Quadrant 3?

    Answer: Brian Marick's Agile Testing Quadrants

    Brian Marick's Agile Testing Quadrants place business-facing tests that critique the product — such as exploratory testing, usability testing, and UAT — in Quadrant 3.

  6. What is the role of a 'Definition of Done' (DoD) in Agile testing?

    Answer: It is a shared checklist of quality criteria that every user story must meet before it is considered complete

    The Definition of Done is a team-wide agreement on the quality standards — including test coverage, code review, and documentation — that must be satisfied before a story is accepted as complete.