FREE CAD Test-Driven Development (TDD) Questions and Answers 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 FREE CAD Test-Driven Development (TDD) Questions and Answers flashcards as text
What is the 'Transformation Priority Premise' in TDD as proposed by Robert C. Martin?
Answer: A set of ordered code transformations that guide incremental implementation from simple to complex
The Transformation Priority Premise provides an ordered list of small code changes that guide developers from the simplest passing implementation toward more general solutions.
Which practice helps prevent TDD tests from becoming tightly coupled to implementation details?
Answer: Writing tests that verify return values and observable behavior rather than internal method calls
Testing observable behavior and outputs rather than internal implementation details keeps tests resilient to refactoring and focused on what actually matters.
What is 'outside-in' TDD?
Answer: Starting with high-level acceptance tests and driving implementation inward through unit tests
Outside-in TDD begins with high-level acceptance or integration tests that define desired behavior, then progressively adds unit tests for inner components as they are discovered.
In TDD, what risk does the 'obvious implementation' technique carry compared to 'fake it till you make it'?
Answer: It may skip important intermediate test cases and introduce subtle bugs
Jumping straight to the obvious implementation can bypass incremental validation steps, potentially introducing errors that smaller steps would have caught.
How does TDD support the YAGNI (You Aren't Gonna Need It) principle?
Answer: By ensuring only code required to pass existing tests is written, preventing speculative features
TDD enforces YAGNI by only allowing production code that is driven by a failing test, which prevents developers from building features that are not yet needed.
What is the purpose of a 'walking skeleton' in the context of TDD and agile development?
Answer: A minimal end-to-end implementation that proves the architecture works and can be tested
A walking skeleton is a thin end-to-end slice of functionality that validates the technical architecture while providing a foundation for TDD iterations.