Pre-lab 2 questions
Name:
Cnet ID:
Lab start time:

Note: There may be more than one answer. Make sure you circle
all that apply
1. There are several ways to collaborate on a project, but only one of the lines below describes collaboration with Duet Programming.
Delete all of the lines below except the one that describes Duet Programming.
      a) Share a single computer, trading off who is at the keyboard
      b) Work on different computers on different parts of the same problem, discussing your work at different points.
      c) Take your assignment and divide it in half. One student completes one half, the other student completes the other half. You design, implement, and test independently. Once you're both done, you put the code together and submit.

2. When are good times to discuss your progress with your partner? Delete all the lines below except the ones that are true for Duet Programming.
      a) When you complete a phase of work.
      b) When you are unsure how to progress.
      c) Only when you have finished the entire problem.
      d) When you have an idea of how your partner should solve their part of the problem.
      e) When you think of a good joke to tell.

3. Which words below describe roles in Duet Programming? (Delete the incorrect answers)
      a) Implementer
      b) Navigator
      c) Driver
      d) Strategist
      e) Manager
      f) Jester
      g) Back-Seat Driver
     
4. How often should you switch roles in Duet Programming? (Delete the incorrect answers)
      a) Every 2 minutes
      b) Each time you complete one phase of a single function in your assignment
      c) When you complete (implementation, testing infrastructure, testing and debugging) one function in your assignment
      d) Each week
      e) Never
******* Test-driven Development *******

5. Which statement(s) are true about TDD?
(delete all answers that are not true)
      a) All tests are written before any implementation
      b) A given test is written before its associated code is implemented
      c) A given test is run before its associated code is implemented
      d) One purpose of TDD is to help programmers better understand the requirements (specifications) for the problem before implementing the solution.
      e) Once a piece of code passes all of its tests, it will not be modified.