Q1:

Software verification is: 1. A process internal to the development team 2. Checking whether you are building the right product 3. Checking whether you are building the product right 4. Making sure the software is what the user really wants

Answer choices:

A: 1 only

B: 2 only

C: 3 only

D: 4 only

E: 1 & 3 only

F: 2 & 4 only

G: 3 & 4 only

H: 1, 2 & 3 only

Also discuss: which, if any, of the statements 1, 2, 3 and 4 apply to software validation?

Q2:

Which of the following is not a form of static testing?

Answer choices:

A: Inspection of software

B: Formal analysis of the program

C: Software execution using statically determined inputs

D: Code walkthrough

Q3:

Once a software has been thoroughly verified, it is guaranteed to pass all acceptance tests.

Answer choices:

A: True

B: False

Q4:

To test a unit of code, the programmer typically creates a _________ to set up data and invoke the unit under test.

Answer choices:

A: driver

B: stub

C: mock

D: None of the above

Also discuss: What do you think are the differences between a stub and a mock?

Q5:

While writing unit tests for a unit A that has a dependency on unit B, do you believe that a test double for B should only be created if the actual code for B has not yet been implemented?

Answer choices:

A: No, it is typically a good to use test doubles in unit tests even if the actual code is ready.

B: Yes, test doubles are only needed if the actual code is not ready.