3.3. Central automated Test server

• Primarily this is to keep the running of tests from interfering with ongoing work people that people are doing
• If their computer is busy running tests, it interferes with their work
• Some tests are general in nature (not the unit tests)
• these tests can be delegated to central Test Server
• Regression scans are also a good candidate
• RISK: developers see this as “someone else’s responsibility”
• have already seen this
• desire for “I write code, someone else does the testing work”
• mentality arises from testing being viewed as drudgery
• a separate system would reinforce this mentality
• public shaming is the general practice to manage this
• developers that check in code that cause a problem are publicly held accountable, this encourages developers to check their own work, before checking in. (this should be mild and short, not ongoing shaming)