Which statement(s) are TRUE about Implicit requirements?
A. They are often, but not always, derived from explicit requirements
B. They apply only to unit and functional tests, not integration tests
C. Testing them is lower priority than testing explicit requirements, since they don’t come from the customer
D. All of the above are true
查看答案
Which of these is POOR advice for TDD?
A. Mock and stub early and often in unit tests
B. Aim for high unit test coverage
C. Sometimes it’s OK to use stubs and mocks in integration tests
D. Unit tests give you higher confidence of system correctness than integration tests
Which non-obvious statement about testing is FALSE?
A. Even 100% test coverage is not a guarantee of being bug-free
B. If you can stimulate a bug-causing condition in a debugger, you can capture it in a test
C. Testing eliminates the need to use a debugger
D. When you change your code, you need to change your tests as well
Which statement is FALSE about Waterfall, Spiral, and Rational Unified Process lifecycles?
All rely on careful planning, and measure progress against the plan
B. All rely on thorough documentation
C. All rely on a manager be in charge of the project
D. All use iteration and prototypes
Which statement is TRUE?
A big difference between Agile and Plan-and-Document is that Agile does not use requirements
B. A big difference between Agile and Plan-and-Document is measuring progress against a plan
C. You can build SaaS apps using Agile, but not with Plan-and-Document
D. A big difference between Agile and Plan-and-Document is building prototypes and interacting with customers during the process