L10 - Version Control 2

Question 1

Why should we run tests locally before committing to VC ?

Answer 1

• Local tests run much faster than on the VC system
• Ensures that we know tests will pass on VC system

Question 2

Why should we always ensure tests pass before moving on?

Answer 2

Ensures you don’t forget what tests were run, and what changes you made

Question 3

Why should we avoid commits on a red build?

Answer 3

Building on a red build will make debugging harder and snowball, compound and overflow bugs as we increase development iterations

Question 4

Should we build on a red build?

Answer 4

No. If build fails, no more changes should be made until build has been made to a Green Build

Question 5

Why should developers never go home on a red build?

Answer 5

• Fixing a red build before leaving ensures you don’t forget changes you made that could’ve contributed to the bugs
• Changes made are fresh in your mind
• Stalls all progress → Must fix so the rest of the team can move forward and avoid stagnation of development

Question 6

What working practice can be employed to avoid going home on a red build? Why is this a good practice?

Answer 6

Check in first thing in the morning as opposed to the end of the day → If a red build occurs, you have the whole team fresh in the morning to tackle it

Question 7

Why should we be prepared to revert?

Answer 7

In case we need to technologically pivot or software becomes overly complex.

Question 8

Why should we avoid commenting out tests?

Answer 8

Ensuring tests are always active provides consistent safeguarding

Question 9

What is Regression Testing?

Answer 9

Re-running previous tests to ensure that they still pass

Question 10

Why is it important to take responsibility for breakages? What does this ensure?

Answer 10

• If you commit and your tests pass but others break… It’s your responsibility to fix it, regardless of who wrote the code
• Ensures that all developers are capable of working effectively across the entire code base