Industry analysts predict that during the second half of this decade, increases in software testing activity will be fuelled by software testing automation. Automated testing tools have matured and ROI to a state where ROI (return on investment) need no longer be a pipe dream.
This will allow more people to be engaged in software test automation with better testing tools. Yet there are still far too many programmes where automation is not delivering on this promise. The main drivers seem to be inflated expectations created by unrealistic ROI in business cases; poor planning and management; and poor skills in implementing the automated testing solution.
It is important to consider automation of the test environment as early as possible and design it into the system from the outset. It's also important to recognise that automation is not appropriate for every project or for all testing on any particular project.
We can help you achieve this balance so that the benefit from test automation at the right time and in the right way.
When designing for automation, some of the pitfalls to avoid are:
* don't be dogmatic and automate everything. You need to be selective and concentrate on common and repetitive tasks * make sure the ROI is realistic. The costs can be high in the short term and initially outweigh the benefits. It is key that credible payback on investment is calculated. * make sure that the staff have suitable levels of skill and experience. If you're using some types of automated tool this can reduce the required skill level across all the testing teams. * create modular test scripts and data driven testing to improve the parameterisation of the solution.
Copyright 2004 Rightrix Solutions. All rights reserved. All product names are trademarks of their respective companies. Views
expressed at QThreads.com reflect the views of the authors alone,
and do not necessarily reflect those of QThreads.com.
Home | Content | Resources | Contact | 
