Review and executive summary: Five reasons test automation projects fail by Ford Arnett
Full ariticle : Five reasons test automation projects fail from FierceElectronics.com by Ford Arnett
If you are about to embark on a software test automation investment, this is a SHOULD READ, and if you aren't - this is a MUST READ to get you going down the automation path!
Summary: "Test automation... has an alarmingly high failure rate. Often, this is due to unrealistic expectations, lack of understanding around automation, or not putting enough focus on value."
Key Points:
"1. Forgetting automation software is still software" - manage it like other software development. Have standards, schedules, set deliverables, version it, test it, and re-use - re-use - re-use (don't reinvent if you can help it).
"2. Automating ‘just because’" - prioritize functions to be automated and start with high-value tests with the largest time savings.
"3. No organizational support" - set the right expectations with all stakeholders.
"4. Expecting automation to fix everything - Automation can be a wonderful tool to allow a team to release faster, find defects earlier, and streamline the process. ... If your team has a well-established process and runs like a well-oiled machine, automation will likely be a powerful tool to your arsenal. Instead, if the project is struggling to keep up with quality concerns and you are releasing twice as fast than you have capacity, automation might not solve everything." True dat.
"5. Overlooking maintenance One of the most important things that are constantly overlooked is test maintenance. Maintenance can often be 30% or more (in longer projects it can exceed the original cost) of the entire budget!" Find tools and process automation to lower these maintenance costs. But plan for it upfront and then work to minimize this cost.
If you are about to embark on a software test automation investment, this is a SHOULD READ, and if you aren't - this is a MUST READ to get you going down the automation path!
Summary: "Test automation... has an alarmingly high failure rate. Often, this is due to unrealistic expectations, lack of understanding around automation, or not putting enough focus on value."
Key Points:
"1. Forgetting automation software is still software" - manage it like other software development. Have standards, schedules, set deliverables, version it, test it, and re-use - re-use - re-use (don't reinvent if you can help it).
"2. Automating ‘just because’" - prioritize functions to be automated and start with high-value tests with the largest time savings.
"3. No organizational support" - set the right expectations with all stakeholders.
"4. Expecting automation to fix everything - Automation can be a wonderful tool to allow a team to release faster, find defects earlier, and streamline the process. ... If your team has a well-established process and runs like a well-oiled machine, automation will likely be a powerful tool to your arsenal. Instead, if the project is struggling to keep up with quality concerns and you are releasing twice as fast than you have capacity, automation might not solve everything." True dat.
"5. Overlooking maintenance One of the most important things that are constantly overlooked is test maintenance. Maintenance can often be 30% or more (in longer projects it can exceed the original cost) of the entire budget!" Find tools and process automation to lower these maintenance costs. But plan for it upfront and then work to minimize this cost.
Comments
Post a Comment