 Introduction-Automation failures areas  Automation script failure categorization  Failure due to bad maintenance  Estimation factors
There are various reason which result into automation failure.  Poor Analysis which result into automating those test cases which are bad candidate for automation as a consequence poor ROI.  Automation script failure is also major issues which occur many times in various organization/projects.  Bad maintenance or automation process  Unplanned or poor planning/Estimation We will be discussing above factors in remaining slides
Test automation analysis needs to be done wise, below are some of the areas around which analysis needs to be done- 1) Identifying test automation candidates 2) Identifying which module/application to automate first so that it can bring better ROI. 3) Identification automation tool which fits technically and in budget also 4) Best fitted automation framework, there are several frameworks but we need to select framework wisely as per project need .
Automation Test candidate needs to be selected wisely m following are common selection criteria- 1) Technical feasible 2) Execution is required in every cycle 3) Manual configuration is not much Also application/module needs to be prioritize so that it can bring maximum ROI
Recommending/Selecting automation tool for any test automation project depends on various reasons- 1) Always consider project size and criticality in terms of financial hit of defect before selecting between open source and commercial tool 2) Identify whether selected tool is technically feasible or not as many tools sometimes does not support new technology 3) Integration of automation tool is possible with other testing/ALM/Defect tool if the same is required. Once we have tool selected we need to plan and create framework which can expedite testing as well as provide quality and ease in maintenance
Automationscriptfailure-Script failurecategorization Functionality change or object change Test data & configuration Object identification issue Environment & other reasons Below categorization describes failure areas mentioned in each quadrants
Maintenance in test automation is very critical , ideally we have to create a framework which helps in easy maintenance whether its waterfall or agile project. Areas which can help in easy maintenance are- 1) Reusability in automation framework 2) Streamlined automation process, good co-ordination between different teams(Manual testing/Dev) 3) Effective method of creating test data
Success of any test automation project depends on good planning and estimation Things which needs to be considered are- 1) Estimating efforts on the basis of test case complexity 2) Estimating efforts on the basis of framework 3) Maintenance/execution time and test data preparation efforts needs to considered in estimation for different testing cycles as they play major role.
Prashant Prashant.compsc@gmail.com

Test Automation failure analysis

  • 2.
     Introduction-Automation failuresareas  Automation script failure categorization  Failure due to bad maintenance  Estimation factors
  • 3.
    There are variousreason which result into automation failure.  Poor Analysis which result into automating those test cases which are bad candidate for automation as a consequence poor ROI.  Automation script failure is also major issues which occur many times in various organization/projects.  Bad maintenance or automation process  Unplanned or poor planning/Estimation We will be discussing above factors in remaining slides
  • 4.
    Test automation analysisneeds to be done wise, below are some of the areas around which analysis needs to be done- 1) Identifying test automation candidates 2) Identifying which module/application to automate first so that it can bring better ROI. 3) Identification automation tool which fits technically and in budget also 4) Best fitted automation framework, there are several frameworks but we need to select framework wisely as per project need .
  • 5.
    Automation Test candidateneeds to be selected wisely m following are common selection criteria- 1) Technical feasible 2) Execution is required in every cycle 3) Manual configuration is not much Also application/module needs to be prioritize so that it can bring maximum ROI
  • 6.
    Recommending/Selecting automation toolfor any test automation project depends on various reasons- 1) Always consider project size and criticality in terms of financial hit of defect before selecting between open source and commercial tool 2) Identify whether selected tool is technically feasible or not as many tools sometimes does not support new technology 3) Integration of automation tool is possible with other testing/ALM/Defect tool if the same is required. Once we have tool selected we need to plan and create framework which can expedite testing as well as provide quality and ease in maintenance
  • 7.
    Automationscriptfailure-Script failurecategorization Functionality changeor object change Test data & configuration Object identification issue Environment & other reasons Below categorization describes failure areas mentioned in each quadrants
  • 8.
    Maintenance in testautomation is very critical , ideally we have to create a framework which helps in easy maintenance whether its waterfall or agile project. Areas which can help in easy maintenance are- 1) Reusability in automation framework 2) Streamlined automation process, good co-ordination between different teams(Manual testing/Dev) 3) Effective method of creating test data
  • 9.
    Success of anytest automation project depends on good planning and estimation Things which needs to be considered are- 1) Estimating efforts on the basis of test case complexity 2) Estimating efforts on the basis of framework 3) Maintenance/execution time and test data preparation efforts needs to considered in estimation for different testing cycles as they play major role.
  • 10.