Automation Approaches

Introduction

  • Define Automation Test Strategy in Agile based Product Development. For version 1.0 Release.
  • Define Risks & Mitigation Plan
  • Product Development is done using Agile-SCRUM Methodology
  • Product is a web based application.
  • Definition of “Ready” for User Stories is met before Sprint Starts.
  • The First Release is tagged and labelled as Version 1.0
  • One Milestone constitute of  3 Sprints 
  • One Sprint is of 10 working days.
  • 0% Automation Coverage is achieved but needs to be increased, however keyword driven framework is adopted based on objects.
  • Automation Tool is Finalized and considered in Project Kick-off.
  • Development Team combination is of 6 Developers and 3 QA.
  • Continuous Integration (CI) is adopted.
  • Objective:
  1. To prepare an Automation Test Strategy that could achieve maximum automation
  2. To meet the deadline
  3. To ensure quality and meeting acceptance criteria
  • Proposed Solutions:
  1. Adopt Parallel Approach
  2. Adopt Lagging Approach
  • Solution I- Parallel Approach
  1. The objective of this Approach is to perform Development of User Stories and Automation of User Stories in the same Sprint parallely
  2. The Test team starts automation/script created based on designs, screens and mockups.
  3. The Test team executes the scripts created on the build and notifies by logging bugs either in the same week or next week (In the same sprint)
  4. This can be better explained in the next diagram

Risks and Mitigations

  • Solution II- Lagging Approach
  1. The objective of this Approach is to perform Development of User Stories in Sprint n and Automation of User Stories in the n+1 Sprint
  2. The Test team starts automation/script created based stability of user stories delivered in Sprint n
  3. The Test team performs Manual Testing in Sprint n
  4. The Test team executes n-1 Sprints scripts i.e scripts of previous sprint
  5. However in this approach 100% automation for Release 1.0 is not achieved
  6. This can be better explained in the next diagram

To know more email: marketing@calsoftinc.com

Contributed by: Sagar Abhyankar| Calsoft inc

Sagar Abhyankar

Sagar Abhyankar

Project Manager at Calsoft Inc.
A Scrum Alliance Certified Scrum Master, with 11 years of experience in testing and delivering Products in Property,Finance,Storage,Refrigeration and Music streaming domain. Over 9 years, I have worked on testing of Software using different Software Testing Tools like Squish, HP Load Runner, IBM Rational Performance Test, HP ALM, HP QC, JIRA, Test-Link. I have also successfully lead teams of talented individuals to test the products that were developed using Waterfall Model and Agile methods to create world-class products. In June 2012, I also visited Denmark to discuss testing strategies, understand client expectations that would help deliver better quality product releases.
Sagar Abhyankar

Latest posts by Sagar Abhyankar (see all)

Leave a Reply

Your email address will not be published. Required fields are marked *