When to Automate - Part 2
By Ray Claridge
Previously - I've blogged about automation and the need to go through an elaboration phase to ensure automation is worthwhile.
Previously - I've blogged about automation and the need to go through an elaboration phase to ensure automation is worthwhile.
My perspective on agile, scrum, testing and the web to inform, provoke and entertain you.
I think implementing automation is an evoluntary process. An organisation adopting Agile will be aware of Test Driven Development (Unit/Component testing) and how this aids the design process. With this in place, a continous integration build process follows, ensuring the Tests written to aid design and drive development are not broken and the design is adhered to. Continous Integration builds have several phases one of which is the functional tests stage, these tests are designed to catch bugs/defects not caught by Tests at the Unit/Component level. Having to convince management of the need for automation is a worrying sign of not fully embracing Agile and the principles that make it such a revolutionary method of delivering projects in today's market. Such analytical tools adequately present the case for Agile principles and guidelines.
I don't think it's about embracing Agile, it's about ensuring there's value for money.
I've seen it first hand, where time/money has been wasted on developing automated tests that have no financial payback. A business previously burnt, will want some assurances that their investment will pay dividends. It's true, quality will increase if automated during the SDLC. However, in this current economic climate, that might not be enough!