โ† All CAD Flashcard Decks

CAD Continuous Integration and 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 Continuous Integration and Testing flashcards as text
  1. What is the primary purpose of a CI build pipeline in an Agile development environment?

    Answer: To automatically compile, test, and validate every code change merged into the shared repository

    A CI pipeline automatically builds and tests each integration to catch defects early and maintain a releasable codebase.

  2. Which testing strategy is most aligned with the Agile testing pyramid?

    Answer: A large number of unit tests, fewer integration tests, and minimal end-to-end tests

    The testing pyramid recommends many fast unit tests at the base, fewer integration tests in the middle, and a small number of slow end-to-end tests at the top.

  3. In a CI workflow, what does 'breaking the build' typically indicate?

    Answer: A committed change caused compilation errors or test failures in the shared branch

    Breaking the build means a recent commit introduced code that fails to compile or passes existing tests, blocking the team.

  4. What is the recommended response time for fixing a broken CI build in Agile practice?

    Answer: It should be the team's top priority and fixed immediately

    Agile teams treat a broken build as the highest priority because it blocks the entire team from integrating and validating further changes.

  5. Which practice helps ensure that automated tests in a CI pipeline remain trustworthy?

    Answer: Eliminating flaky tests and ensuring each test produces deterministic results

    Flaky tests erode confidence in the CI pipeline, so teams must fix or remove non-deterministic tests to keep the suite reliable.

  6. What is the main benefit of running static code analysis as part of a CI pipeline?

    Answer: It detects code quality issues, security vulnerabilities, and style violations automatically before code review

    Static analysis catches potential bugs, security flaws, and coding standard violations early without executing the code.