Test Automation for Waterfall
Developer Claim: By waiting until the product code is near or at completion to execute your primary test automation capabilities, your likely missing out on some of the benefits offered by test automation. In other words, generally speaking, there are missed opportunities when pairing test automation and waterfall-like software development, where the automation team starts once the developer has a Release Candidate. He believes that moving the automation team earlier in the process would offer more value.
My Response: That sounds reasonable, but what well respected source claims of this inherent conflict between test automation and waterfall? Sure we can argue to move the test automation team to the left, but where do we point to for an objective assessment.
Developer Response: Siiiiigggghhh
Anyone here know of any reputable sources that address this question that we can mull over?
