SlideShare a Scribd company logo
Agile QA Process
Anand Bagmar
Anand.Bagmar@thoughtworks.com
abagmar@gmail.com
http://www.essenceoftesting.blogspot.com


Version 1.1




Agile QA Process                           1 / 12
1. Objective
QA is NOT the gatekeeper of the quality of the product. This is a TEAM responsibility. However,
we, as QAs, testers, have an additional responsibility – that of being watchful and proactive to
ensure the quality of the product remains a TEAM responsibility.

To make this effective, more so in a distributed development and QA team working on an Agile
Software project, the QA team should adhere to the guidelines and protocols recommended in
this document to help achieve the following:
 Enable the QA team better test the product.
 Provide correct set of visibility in terms of the quality of the product.
 Will be simple, intuitive, easy to follow and achieve.
 Test early and provide quick feedback on the quality of the product.


2. Process
The QA process for the team fits into 3 broad categories:
1. Agile Testing - from Iteration 0 to Release
2. Testing within each Iteration
3. Pre-Production / Release testing

Each of these processes is detailed below.

2.1    Agile Testing lifecycle – from Iteration 0 to Release
To be effective in testing on an Agile project, the QA needs to keep track of the past, the
present and the future! Also, the role of a QA is very dynamic as the project moves from
Iteration 0 till the release date.

The pictorial representation shown below depicts the typical activities the QA is involved in, in
the lifecycle of the project.




Agile QA Process                                                                            2 / 12
Iteration 0       Iteration 1       Iteration 2      Iteration 3       ...   ...   Iteration n

     Story test                         Showcase          Showcase                      Showcase
    analysis for         IPM           Iteration 1,      Iteration 2,                 Iteration n-1,
    Iteration 1                            IPM               IPM                           IPM

                      Iteration 1       Complete          Complete                     Complete
         Test
                     Story testing     Iteration 1       Iteration 2                 Iteration n-1
    Automation
                      (manual +       Story testing     Story testing                Story testing
     - strategy,
                     automation)
    framework
     setup, etc.                         Complete          Complete                    Complete
                      Story test        Iteration 1       Iteration 2                Iteration n-1
                     analysis for      Automation        Automation                  Automation
                     Iteration 2
                                       Iteration 2       Iteration 3                 Iteration n-1
                                      Story testing     Story testing                Story testing
                                       (manual +         (manual +                     (manual +
                                      automation)       automation)                  automation)

                                          Test             Test                          Test
                                       Automation       Automation                    Automation
                                         maint.,          maint.,                       maint.,
                                        execution        execution                     execution

                                        Story test        Story test                    Story test
                                       analysis for      analysis for                  analysis for
                                       Iteration 3       Iteration 4                  Iteration n+1




A QA does three types of activities in each Iteration:
1. Ideally, all testing (manual + automation) would be completed in the same iteration.
   However, in quite a few cases, I have seen that testing lags behind by some duration.
   Hence, in each iteration, there “may-be” some amount of work to be completed from the
   earlier iteration work.
   This is applicable mainly from Iteration 2 onwards. (See the boxes with the “green text” in
   the picture.)
2. Story testing for the current iteration. This testing includes manual and automation work.
   (See the boxes with the “black text” in the picture.)
3. Work with the Business Analysts to get visibility into the next iteration stories, and also help
   iron out those stories. (See the boxes with the “orange text” in the picture.)




Agile QA Process                                                                                3 / 12
2.2      Testing within each Iteration
The QA has various responsibilities in the iteration as depicted in the picture below.

NOTE: Though these activities typically occur in the sequence shown in the image, many a times,
based on the context, the sequence may be different, and also some of the activities may
happen in parallel.




                                              Story planning session -
                                                   write / refine
                                                Acceptance Criteria

                               Showcase                                          IPM




      Automation (execution,
                                                                                                  QA kickoff
          maintenance)




                                                   ITERATION


      Story testing – manual
                                                                                                 Story kickoff
       + Exploratory Testing




                         BA / QA Volleyball                              Test Scenario Writing


                                              Implement Automated
                                                Acceptance Tests



Let us try to understand the semantics of these tasks.

2.2.1 Story planning session – write / refine Acceptance Criteria
The planning for the iteration starts at least an iteration before the current one.



Agile QA Process                                                                                                 4 / 12
Example, if we are currently in Iteration 2, the planning for this iteration has happened at the
latest in Iteration 1.
In this step, the QA (at least one person from the QA team) should work with the Business
Analyst to understand the story, and help write the acceptance criteria.
This helps in various ways:
 There is better visibility of the business requirements.
 Better and more complete acceptance criteria can be written in the story as early as
    possible which will then feed into the development team.
 Since the QA team now knows what stories are coming up, they can plan their testing
    strategy more appropriately.

2.2.2 Iteration Planning Meeting (IPM)
The IPM is a forum for the QAs to understand the business priorities and which stories are
going to be played in the Iteration from the business stakeholders. The QA team should make
full use of this opportunity and ensure the following:
 Make it effective for onsite and offshore QA team
 Raise risks / issues as soon as possible
 Ensure QA capacity / estimates are accounted for
 Identify / highlight dependencies

2.2.3 QA kickoff for the Iteration
After the IPM, the QA team should have a QA kickoff for the iteration. In most cases, the
Business Analyst should be invited to ensure correct understanding by the team.
Items to cover in this step include the following:
● Overall understanding of the stories
● Any potential issues to watch out for
● Identifying and setting up test data for all the stories coming up
● Identifying automation maintenance tasks based on upcoming stories
● Creating a Status Matrix to identify priorities. (See below for more details on this.)
● Each QA will then signup for testing specific stories.
    In case of distributed team, a good guideline to follow is that the QA team should sign up
    for stories that are developed in the same location. This will ensure quick turnaround time
    for testing each story.

NOTE: In many cases the points to be included in the QA kickoff would actually be covered in
the IPM itself, hence making this step redundant.




Agile QA Process                                                                           5 / 12
2.2.4 Individual Story testing
2.2.4.1   Story kickoff
Once the story signup is done, there is a Story kickoff with the Business Analyst, the
developer(s) and the QA person. This is a very important discussion that gets all involved parties
on the same page in understanding the requirements and the deliverables of the story.

This discussion should be as detailed as possible with the QA(s) trying to identify and share the
test scenarios with the BA and the developers. Also, input from the BA and the developers
should be taken on any scenarios that may have been missed, or based on the understanding of
the code changes involved, if any other scenarios need to be included when testing the story.

2.2.4.2     Test data preparation
Following the story kickoff, the QA should start preparing / identifying the test data that would
be needed to effectively test the story – manually and via automation. A different set of data
should be used for manual, automated and developer testing to prevent data-conflict related
test failures.

This activity should be done keeping the other QA team members and development team
members in the loop to ensure no overlap in the test data. Also, if any scripts / setup can be
shared, that would help save time and effort and also duplication can be avoided.

2.2.4.3    Test scenario writing
The test data preparation and test scenario writing activities go hand-in-hand, and not
necessarily sequentially. The (manual and to-be-automated) scenarios to be tested for this
story should be identified and updated in the Test Case Management tool being used.

Once the test scenarios are written, these should be shared / reviewed (at least informally) with
the Business Analysts and the developers developing this story, to ensure the scenarios are
complete, and also the developers can probably identify missing pieces in the code at a much
earlier stage.

2.2.4.4   Automate test scenarios
The QA team needs to identify test scenarios that make sense to be automated, and which can
be automated. Then the script automation should be started.

Since the story is still not complete, there probably will be limitations how much can be done at
this stage. However, in most cases, a lot of ground work and framework layers can be created
without needing the completed story.

After the BA / QA Volleyball, the missing pieces in the automation scripts can be completed by
pointing the tests to a local / developer environment.

QA’s should be mindful that the Test Automation code should be of “production” quality. They
should use proper OOPs (Object Oriented Programming) concepts while implementing the


Agile QA Process                                                                             6 / 12
automated tests and ensure that any new code that is written is NOT duplicated, and
structured properly.

2.2.4.5     Business Analyst (BA) / QA Volleyball
Once the developers complete the story development work, there should be a BA / QA
Volleyball. What this means is that the BA and QA will test the story’s acceptance criteria on the
developer’s local environment. All the acceptance criteria failures should be fixed by the
developer before the story can be said to be “development completed”.

2.2.4.6     Test the Story
After the BA / QA volleyball is completed, a new build should be made available to the QA team
to test the story based on the scripts identified and documented.

NOTE: The QA team should never be working against testing the developer code. Instead they
should always insist on testing the compiled and deployed binaries in the proper test
environment to simulate the end-user scenarios.

Once a build is available in the appropriate environment, the QA should execute the manual
test scripts.

There should be at least one round of Exploratory Testing for the story, and the features /
functionalities around the changes that have been developed as part of the story to ensure
there are no regressions or other issues in the product. Based on the time available in the
iteration, this can happen either on a developer sand-box, or deployed builds.

Exploratory Testing is very important and typically a lot of issues are found from this type of
testing.

2.2.5 Automation
All the automated tests should be run at least a couple of times per iteration, preferably via
some CI (Continuous Integration) mechanism. Else the automation is not of much value. The
frequency of these test runs should be fine-tuned keeping in consideration the load on the
system, availability of key resources needed by the system, etc. The test run reports should
then be shared with the team.

Also, the automated tests should be grouped logically to facilitate running selected tests easily.

Note: The list of groups would probably be an evolving list.

2.2.6 Showcase
The functionality developed in the iteration is presented to the Business Stakeholders at the
end of the iteration (, or, in some cases earlier too). It is important for a representative from the
QA team to be part of this event in order to understand how the functionality was received by
the various attendees, and also if any other new information (in terms of requirements, test
scenarios) comes up in the session.


Agile QA Process                                                                               7 / 12
3. UAT / Pre-Production / Release Testing
This testing will be done using the guidelines published by the client organization.


4. Defects reporting and verification
Along with the standard / regular defect reporting and verification process, a few additional
activities help a lot in reducing the turnaround for defects.

When reporting the defects, attach screen shots / videos (where applicable) to help the
developers reproduce the problem easily. This will ensure in quicker turnaround on the defect.

Example: The tool “Jing” (http://www.techsmith.com/jing/) has a free tool version that can be
used to take screenshots and video snippets from your computer.


5. Other
5.1.1 Code freeze for the iteration (example: 2 days before iteration end)
This will give the QA team a chance to do a quick pass of manual + exploratory testing of the
stories in the same iteration. Without this there is always going to be a spillover of stories in the
next iteration.

5.1.2 QA estimates
A story estimate really means the total time it takes to develop and test the story. If this
estimate changes to being a “development” estimate, then we need another approach.

A 1 point Developer story does not equate to a 1 point QA story. Hence, each story should have
QA estimates which would allow better capacity and scope planning for the iteration and
release.

This also facilitates data collection over a period of time w.r.t. the actual time needed by the QA
team to do effective testing versus the currently allocated QA capacity, so that the
management team can then take proper action to mitigate the issues.

5.1.3 Visibility
An appropriate dashboard should be created that provides all relevant details about the quality
of the product under test.
Example list of items to include in the dashboard:
● Number of stories in the iteration in “Ready for QA” state
● Number of stories in the iteration in “In QA” state
● Number of stories in the iteration which are not yet in “Ready for QA” state




Agile QA Process                                                                               8 / 12
● Number of Defects open (including the iteration reported in), with current assignees,
  priority and severity
● Number of Defects pending verification
● Automation backlog (Stories for which Automation is not yet completed)

5.1.4 Communication
Effective communication and collaboration within all the team members (co-located,
distributed) is critical to the success of an Agile software project.
A few tips mentioned below can help in this regard:
 Daily catch up calls / emails / IMs
 Sharing knowledge of story across QA team
 Keeping the QA status in the story updated
 In case of distributed teams, if a story changes location for any reason, the QA team needs
    to be made aware of the change, and they need to ensure testing is not going to be affected
    for it.
 Any change in story (addition, deletion, modification of narrative / acceptance criteria)
    should be communicated to at least one QA team member by the PM / BA / developer. This
    QA team member will then coordinate with the QA working on the story (if not the same
    person) and ensure all testing related to the story is adjusted appropriately.

5.1.5 Task list
There should be a common page / task list that the QA team across locations can keep adding /
editing tasks they encounter along the way in the Iterations. Any QA team member having
bandwidth then signup for it along the way and complete it.

The list can be of the following format:
Number Task / Item                       Estimated      Signup       Status       More notes
                                     effort (in days)




Agile QA Process                                                                          9 / 12
5.1.6 QA section in each story
Each story should have a QA specific section to help track the testing status on each story.
QA Assignee
QA Estimate - Text box
Defects reported - Text box
QA Status - each status should be separately tracked - either as a checkbox or radio button
(except Automation), or as a drop down list.


Status                           Description

Kickoff Done                     for when the kickoff for the story was done

BAV Done                         for when BA volleyball was done

Test Scenario Done               for when the test scenarios (manual and automation) were
                                 identified and documented in Quality Centre

Automation                       what is the status of test Automation for this story
> In Progress
> Blocked
> Done
> N/A

QA Complete                      when the story was done and tested




Agile QA Process                                                                        10 / 12
5.1.8 QA Status Matrix
This matrix can help the QA team come up with priorities of their tasks with respect to when
the stories for the current iteration are going to be available.

The matrix looks like this:

Current Iteration # 2
 Story  Sept Sept Sept Sept Sept Sept Sept Oct Oct Oct
 Date        22     23 24 27 28   29   30   1   4   5
 #10
 #11



The 1st column lists the Story numbers. The 1st row lists the days of the iteration. Based on
communication with the Business Analysts and developers working on each story, the QA team
can use different status to track when the story will be available for them for testing. They can
then use this information to prioritize their other tasks.

The following different status messages can be used on this chart:
 Status                             Acronym (Estimate)                Acronym (Actual /
                                                                      Completed)
 Kickoff done                       K                                 K
 Development complete ETA           D                                 D
 Scenario done                      S                                 S
 Automation                         A                                 A
 Complete                           C                                 C




Agile QA Process                                                                           11 / 12
6. Disclaimer
“QA” Vs “Tester”: There are various different terminologies and everyone probably has a
different view about that. To me this is just a label.

In the past 11+ years I have carried the label of “Test Engineer”, “Software Engineer”, “Software
Engineer in Test”, “Software Development Engineer in Test”, Product Quality Engineer, Quality
Analyst, etc. Regardless of the label, I have pretty much been doing slightly different
manifestations of the same thing – and that is doing what is required to ensure the quality of
the product that is being shipped out is of top quality.

I use “QA” Vs “Tester” depending on who I am talking with, so that the set of people can relate
better to what I am saying.




Agile QA Process                                                                           12 / 12

More Related Content

What's hot

Agile QA process
Agile QA processAgile QA process
Agile QA process
Ashish Agrawal
 
Agile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil KaradeAgile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil Karade
IndicThreads
 
Agile testing
Agile testingAgile testing
Agile testing
Yogita patil
 
Automated Testing with Agile
Automated Testing with AgileAutomated Testing with Agile
Automated Testing with Agile
Ken McCorkell
 
Introduction to Agile Testing
Introduction to Agile TestingIntroduction to Agile Testing
Introduction to Agile Testing
Raymond Adrian (Rad) Butalid
 
Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)
Leonard Fingerman
 
Testing & Quality Assurance
Testing & Quality AssuranceTesting & Quality Assurance
Testing & Quality Assurance
Anand Subramaniam
 
Agile Testing and Test Automation
Agile Testing and Test AutomationAgile Testing and Test Automation
Agile Testing and Test Automation
Naveen Kumar Singh
 
How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy
Impetus Technologies
 
Agile Testing Strategy
Agile Testing StrategyAgile Testing Strategy
Agile Testing Strategy
tharindakasun
 
Test Automation Strategy
Test Automation StrategyTest Automation Strategy
Test Automation Strategy
Martin Ruddy
 
Test Automation
Test AutomationTest Automation
Test Automation
nikos batsios
 
Agile testing - Testing From Day 1
Agile testing - Testing From Day 1Agile testing - Testing From Day 1
Agile testing - Testing From Day 1
Kaizenko
 
Test automation
Test automationTest automation
Test automation
Xavier Yin
 
Automation Testing
Automation TestingAutomation Testing
Automation Testing
Sun Technlogies
 
Presentation on Agile Testing
Presentation on Agile TestingPresentation on Agile Testing
Presentation on Agile Testing
1Solutions Pvt. Ltd.
 
Agile Testing - presentation for Agile User Group
Agile Testing - presentation for Agile User GroupAgile Testing - presentation for Agile User Group
Agile Testing - presentation for Agile User Group
suwalki24.pl
 
Introduction to Automation Testing
Introduction to Automation TestingIntroduction to Automation Testing
Introduction to Automation Testing
Archana Krushnan
 
Automation testing
Automation testingAutomation testing
Automation testing
Biswajit Pratihari
 
Testing concepts ppt
Testing concepts pptTesting concepts ppt
Testing concepts ppt
Rathna Priya
 

What's hot (20)

Agile QA process
Agile QA processAgile QA process
Agile QA process
 
Agile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil KaradeAgile testing principles and practices - Anil Karade
Agile testing principles and practices - Anil Karade
 
Agile testing
Agile testingAgile testing
Agile testing
 
Automated Testing with Agile
Automated Testing with AgileAutomated Testing with Agile
Automated Testing with Agile
 
Introduction to Agile Testing
Introduction to Agile TestingIntroduction to Agile Testing
Introduction to Agile Testing
 
Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)Test Automation Best Practices (with SOA test approach)
Test Automation Best Practices (with SOA test approach)
 
Testing & Quality Assurance
Testing & Quality AssuranceTesting & Quality Assurance
Testing & Quality Assurance
 
Agile Testing and Test Automation
Agile Testing and Test AutomationAgile Testing and Test Automation
Agile Testing and Test Automation
 
How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy How to Design a Successful Test Automation Strategy
How to Design a Successful Test Automation Strategy
 
Agile Testing Strategy
Agile Testing StrategyAgile Testing Strategy
Agile Testing Strategy
 
Test Automation Strategy
Test Automation StrategyTest Automation Strategy
Test Automation Strategy
 
Test Automation
Test AutomationTest Automation
Test Automation
 
Agile testing - Testing From Day 1
Agile testing - Testing From Day 1Agile testing - Testing From Day 1
Agile testing - Testing From Day 1
 
Test automation
Test automationTest automation
Test automation
 
Automation Testing
Automation TestingAutomation Testing
Automation Testing
 
Presentation on Agile Testing
Presentation on Agile TestingPresentation on Agile Testing
Presentation on Agile Testing
 
Agile Testing - presentation for Agile User Group
Agile Testing - presentation for Agile User GroupAgile Testing - presentation for Agile User Group
Agile Testing - presentation for Agile User Group
 
Introduction to Automation Testing
Introduction to Automation TestingIntroduction to Automation Testing
Introduction to Automation Testing
 
Automation testing
Automation testingAutomation testing
Automation testing
 
Testing concepts ppt
Testing concepts pptTesting concepts ppt
Testing concepts ppt
 

Similar to Agile QA Process

ICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall Projects
ICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall ProjectsICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall Projects
ICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall Projects
Eliane Collins
 
2V_presentation
2V_presentation2V_presentation
2V_presentation
nrvikhyath
 
2 v presentation_new
2 v presentation_new2 v presentation_new
2 v presentation_new
nrvikhyath
 
Test Automation and Keyword-driven testing af Brian Nielsen, CISS/AAU
Test Automation and Keyword-driven testing af Brian Nielsen, CISS/AAUTest Automation and Keyword-driven testing af Brian Nielsen, CISS/AAU
Test Automation and Keyword-driven testing af Brian Nielsen, CISS/AAU
InfinIT - Innovationsnetværket for it
 
Technical meeting automated testing with vs2010
Technical meeting automated testing with vs2010Technical meeting automated testing with vs2010
Technical meeting automated testing with vs2010
Clemens Reijnen
 
Test Driven Development via Agile Testing
Test Driven Development via Agile TestingTest Driven Development via Agile Testing
Test Driven Development via Agile Testing
Anand Bagmar
 
Implementing Test Automation in Agile Projects
Implementing Test Automation in Agile ProjectsImplementing Test Automation in Agile Projects
Implementing Test Automation in Agile Projects
Dominik Dary
 
Releasing fast code - The DevOps approach
Releasing fast code - The DevOps approachReleasing fast code - The DevOps approach
Releasing fast code - The DevOps approach
Michael Kopp
 
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex EnvironmentsDr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
AgileSparks
 
Qtp basic
Qtp basicQtp basic
Qtp basic
Sandeep
 
Implementing Test Automation in Agile Projects
Implementing Test Automation in Agile ProjectsImplementing Test Automation in Agile Projects
Implementing Test Automation in Agile Projects
Michael Palotas
 
Shirly Ronen - User story testing activities
Shirly Ronen - User story testing activitiesShirly Ronen - User story testing activities
Shirly Ronen - User story testing activities
AgileSparks
 
test
testtest
test
gikrauss
 
test
testtest
test
gikrauss
 
Qtp92 Presentation
Qtp92 PresentationQtp92 Presentation
Qtp92 Presentation
a34sharm
 
Agile testing - Reducing time to Market
Agile testing - Reducing time to MarketAgile testing - Reducing time to Market
Agile testing - Reducing time to Market
Manoj K G
 
JUnit with_mocking
JUnit with_mockingJUnit with_mocking
JUnit with_mocking
Zeeshan Khan
 
Agile Software Development in Practice - A Developer Perspective
Agile Software Development in Practice - A Developer PerspectiveAgile Software Development in Practice - A Developer Perspective
Agile Software Development in Practice - A Developer Perspective
Wee Witthawaskul
 
Chapter 10
Chapter 10Chapter 10
Chapter 10
Tony Huynh
 
How to Select the Right Automation Testing Tool
How to Select the Right Automation Testing ToolHow to Select the Right Automation Testing Tool
How to Select the Right Automation Testing Tool
Exist
 

Similar to Agile QA Process (20)

ICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall Projects
ICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall ProjectsICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall Projects
ICTSS 2010 - Iterative Software Testing Process for Scrum and Waterfall Projects
 
2V_presentation
2V_presentation2V_presentation
2V_presentation
 
2 v presentation_new
2 v presentation_new2 v presentation_new
2 v presentation_new
 
Test Automation and Keyword-driven testing af Brian Nielsen, CISS/AAU
Test Automation and Keyword-driven testing af Brian Nielsen, CISS/AAUTest Automation and Keyword-driven testing af Brian Nielsen, CISS/AAU
Test Automation and Keyword-driven testing af Brian Nielsen, CISS/AAU
 
Technical meeting automated testing with vs2010
Technical meeting automated testing with vs2010Technical meeting automated testing with vs2010
Technical meeting automated testing with vs2010
 
Test Driven Development via Agile Testing
Test Driven Development via Agile TestingTest Driven Development via Agile Testing
Test Driven Development via Agile Testing
 
Implementing Test Automation in Agile Projects
Implementing Test Automation in Agile ProjectsImplementing Test Automation in Agile Projects
Implementing Test Automation in Agile Projects
 
Releasing fast code - The DevOps approach
Releasing fast code - The DevOps approachReleasing fast code - The DevOps approach
Releasing fast code - The DevOps approach
 
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex EnvironmentsDr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
Dr. Ronen Bar-Nahor - Optimizing Agile Testing in Complex Environments
 
Qtp basic
Qtp basicQtp basic
Qtp basic
 
Implementing Test Automation in Agile Projects
Implementing Test Automation in Agile ProjectsImplementing Test Automation in Agile Projects
Implementing Test Automation in Agile Projects
 
Shirly Ronen - User story testing activities
Shirly Ronen - User story testing activitiesShirly Ronen - User story testing activities
Shirly Ronen - User story testing activities
 
test
testtest
test
 
test
testtest
test
 
Qtp92 Presentation
Qtp92 PresentationQtp92 Presentation
Qtp92 Presentation
 
Agile testing - Reducing time to Market
Agile testing - Reducing time to MarketAgile testing - Reducing time to Market
Agile testing - Reducing time to Market
 
JUnit with_mocking
JUnit with_mockingJUnit with_mocking
JUnit with_mocking
 
Agile Software Development in Practice - A Developer Perspective
Agile Software Development in Practice - A Developer PerspectiveAgile Software Development in Practice - A Developer Perspective
Agile Software Development in Practice - A Developer Perspective
 
Chapter 10
Chapter 10Chapter 10
Chapter 10
 
How to Select the Right Automation Testing Tool
How to Select the Right Automation Testing ToolHow to Select the Right Automation Testing Tool
How to Select the Right Automation Testing Tool
 

More from Anand Bagmar

Eradicate Flaky Tests
Eradicate Flaky TestsEradicate Flaky Tests
Eradicate Flaky Tests
Anand Bagmar
 
Automating the real-user scenarios across multi-apps, and multi-devices
Automating the real-user scenarios across multi-apps, and multi-devicesAutomating the real-user scenarios across multi-apps, and multi-devices
Automating the real-user scenarios across multi-apps, and multi-devices
Anand Bagmar
 
Visual Validation - The missing tip of the automation pyramid @GoT2022
Visual Validation - The missing tip of the automation pyramid @GoT2022Visual Validation - The missing tip of the automation pyramid @GoT2022
Visual Validation - The missing tip of the automation pyramid @GoT2022
Anand Bagmar
 
Design Patterns in Automation
Design Patterns in AutomationDesign Patterns in Automation
Design Patterns in Automation
Anand Bagmar
 
Change Tyres In A Moving Car - Make Functional Test Automation Effective Keynote
Change Tyres In A Moving Car - Make Functional Test Automation Effective KeynoteChange Tyres In A Moving Car - Make Functional Test Automation Effective Keynote
Change Tyres In A Moving Car - Make Functional Test Automation Effective Keynote
Anand Bagmar
 
Rewrite vs Refactor (AgileIndia 2021)
Rewrite vs Refactor (AgileIndia 2021)Rewrite vs Refactor (AgileIndia 2021)
Rewrite vs Refactor (AgileIndia 2021)
Anand Bagmar
 
Next Generation Functional & Visual Testing powered by AI
Next Generation Functional & Visual Testing powered by AINext Generation Functional & Visual Testing powered by AI
Next Generation Functional & Visual Testing powered by AI
Anand Bagmar
 
The Best Test Automation Framework is...
The Best Test Automation Framework is...The Best Test Automation Framework is...
The Best Test Automation Framework is...
Anand Bagmar
 
Eradicate Flaky Tests - AppiumConf 2021
Eradicate Flaky Tests - AppiumConf 2021Eradicate Flaky Tests - AppiumConf 2021
Eradicate Flaky Tests - AppiumConf 2021
Anand Bagmar
 
Getting started with Appium 2.0
Getting started with Appium 2.0Getting started with Appium 2.0
Getting started with Appium 2.0
Anand Bagmar
 
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
Anand Bagmar
 
Selenium Deep Dive
Selenium Deep DiveSelenium Deep Dive
Selenium Deep Dive
Anand Bagmar
 
Does your functional automation really add value?
Does your functional automation really add value?Does your functional automation really add value?
Does your functional automation really add value?
Anand Bagmar
 
Measuring Coverage From E2E Tests
Measuring Coverage From E2E TestsMeasuring Coverage From E2E Tests
Measuring Coverage From E2E Tests
Anand Bagmar
 
Getting started with Visual Testing using Applitools - @TPC, Feb2020
Getting started with Visual Testing using Applitools - @TPC, Feb2020Getting started with Visual Testing using Applitools - @TPC, Feb2020
Getting started with Visual Testing using Applitools - @TPC, Feb2020
Anand Bagmar
 
Visual validation - The missing tip of the automation pyramid @ QA Symposium
Visual validation - The missing tip of the automation pyramid @ QA SymposiumVisual validation - The missing tip of the automation pyramid @ QA Symposium
Visual validation - The missing tip of the automation pyramid @ QA Symposium
Anand Bagmar
 
Collaboration - A Taboo!
Collaboration - A Taboo!Collaboration - A Taboo!
Collaboration - A Taboo!
Anand Bagmar
 
Visual Validation - The Missing Tip of the Automation Pyramid
Visual Validation - The Missing Tip of the Automation PyramidVisual Validation - The Missing Tip of the Automation Pyramid
Visual Validation - The Missing Tip of the Automation Pyramid
Anand Bagmar
 
Measuring Consumer Quality - The Missing Feedback Loop
Measuring Consumer Quality - The Missing Feedback LoopMeasuring Consumer Quality - The Missing Feedback Loop
Measuring Consumer Quality - The Missing Feedback Loop
Anand Bagmar
 
What is Agile Testing? How does Automation help?
What is Agile Testing? How does Automation help?What is Agile Testing? How does Automation help?
What is Agile Testing? How does Automation help?
Anand Bagmar
 

More from Anand Bagmar (20)

Eradicate Flaky Tests
Eradicate Flaky TestsEradicate Flaky Tests
Eradicate Flaky Tests
 
Automating the real-user scenarios across multi-apps, and multi-devices
Automating the real-user scenarios across multi-apps, and multi-devicesAutomating the real-user scenarios across multi-apps, and multi-devices
Automating the real-user scenarios across multi-apps, and multi-devices
 
Visual Validation - The missing tip of the automation pyramid @GoT2022
Visual Validation - The missing tip of the automation pyramid @GoT2022Visual Validation - The missing tip of the automation pyramid @GoT2022
Visual Validation - The missing tip of the automation pyramid @GoT2022
 
Design Patterns in Automation
Design Patterns in AutomationDesign Patterns in Automation
Design Patterns in Automation
 
Change Tyres In A Moving Car - Make Functional Test Automation Effective Keynote
Change Tyres In A Moving Car - Make Functional Test Automation Effective KeynoteChange Tyres In A Moving Car - Make Functional Test Automation Effective Keynote
Change Tyres In A Moving Car - Make Functional Test Automation Effective Keynote
 
Rewrite vs Refactor (AgileIndia 2021)
Rewrite vs Refactor (AgileIndia 2021)Rewrite vs Refactor (AgileIndia 2021)
Rewrite vs Refactor (AgileIndia 2021)
 
Next Generation Functional & Visual Testing powered by AI
Next Generation Functional & Visual Testing powered by AINext Generation Functional & Visual Testing powered by AI
Next Generation Functional & Visual Testing powered by AI
 
The Best Test Automation Framework is...
The Best Test Automation Framework is...The Best Test Automation Framework is...
The Best Test Automation Framework is...
 
Eradicate Flaky Tests - AppiumConf 2021
Eradicate Flaky Tests - AppiumConf 2021Eradicate Flaky Tests - AppiumConf 2021
Eradicate Flaky Tests - AppiumConf 2021
 
Getting started with Appium 2.0
Getting started with Appium 2.0Getting started with Appium 2.0
Getting started with Appium 2.0
 
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
Visual Validation - The missing tip of the automation pyramid @AgileIndia2020
 
Selenium Deep Dive
Selenium Deep DiveSelenium Deep Dive
Selenium Deep Dive
 
Does your functional automation really add value?
Does your functional automation really add value?Does your functional automation really add value?
Does your functional automation really add value?
 
Measuring Coverage From E2E Tests
Measuring Coverage From E2E TestsMeasuring Coverage From E2E Tests
Measuring Coverage From E2E Tests
 
Getting started with Visual Testing using Applitools - @TPC, Feb2020
Getting started with Visual Testing using Applitools - @TPC, Feb2020Getting started with Visual Testing using Applitools - @TPC, Feb2020
Getting started with Visual Testing using Applitools - @TPC, Feb2020
 
Visual validation - The missing tip of the automation pyramid @ QA Symposium
Visual validation - The missing tip of the automation pyramid @ QA SymposiumVisual validation - The missing tip of the automation pyramid @ QA Symposium
Visual validation - The missing tip of the automation pyramid @ QA Symposium
 
Collaboration - A Taboo!
Collaboration - A Taboo!Collaboration - A Taboo!
Collaboration - A Taboo!
 
Visual Validation - The Missing Tip of the Automation Pyramid
Visual Validation - The Missing Tip of the Automation PyramidVisual Validation - The Missing Tip of the Automation Pyramid
Visual Validation - The Missing Tip of the Automation Pyramid
 
Measuring Consumer Quality - The Missing Feedback Loop
Measuring Consumer Quality - The Missing Feedback LoopMeasuring Consumer Quality - The Missing Feedback Loop
Measuring Consumer Quality - The Missing Feedback Loop
 
What is Agile Testing? How does Automation help?
What is Agile Testing? How does Automation help?What is Agile Testing? How does Automation help?
What is Agile Testing? How does Automation help?
 

Recently uploaded

Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Jeffrey Haguewood
 
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity serverDandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
Antonios Katsarakis
 
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024
Jason Packer
 
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframeDigital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Precisely
 
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
saastr
 
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing InstancesEnergy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Alpen-Adria-Universität
 
June Patch Tuesday
June Patch TuesdayJune Patch Tuesday
June Patch Tuesday
Ivanti
 
Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)
Jakub Marek
 
GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)
Javier Junquera
 
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS  at Code Europe 2024Introduction of Cybersecurity with OSS  at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
Hiroshi SHIBATA
 
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
AstuteBusiness
 
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfHow to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
Chart Kalyan
 
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development ProvidersYour One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
akankshawande
 
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying AheadDigital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Wask
 
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green MasterplanJavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
Miro Wengner
 
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Tatiana Kojar
 
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
Intelisync
 
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdfMonitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Tosin Akinosho
 
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and MilvusGenerating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
Zilliz
 
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptxNordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
MichaelKnudsen27
 

Recently uploaded (20)

Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
Salesforce Integration for Bonterra Impact Management (fka Social Solutions A...
 
Dandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity serverDandelion Hashtable: beyond billion requests per second on a commodity server
Dandelion Hashtable: beyond billion requests per second on a commodity server
 
Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024Columbus Data & Analytics Wednesdays - June 2024
Columbus Data & Analytics Wednesdays - June 2024
 
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their MainframeDigital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
Digital Banking in the Cloud: How Citizens Bank Unlocked Their Mainframe
 
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
Overcoming the PLG Trap: Lessons from Canva's Head of Sales & Head of EMEA Da...
 
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing InstancesEnergy Efficient Video Encoding for Cloud and Edge Computing Instances
Energy Efficient Video Encoding for Cloud and Edge Computing Instances
 
June Patch Tuesday
June Patch TuesdayJune Patch Tuesday
June Patch Tuesday
 
Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)Main news related to the CCS TSI 2023 (2023/1695)
Main news related to the CCS TSI 2023 (2023/1695)
 
GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)GNSS spoofing via SDR (Criptored Talks 2024)
GNSS spoofing via SDR (Criptored Talks 2024)
 
Introduction of Cybersecurity with OSS at Code Europe 2024
Introduction of Cybersecurity with OSS  at Code Europe 2024Introduction of Cybersecurity with OSS  at Code Europe 2024
Introduction of Cybersecurity with OSS at Code Europe 2024
 
Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |Astute Business Solutions | Oracle Cloud Partner |
Astute Business Solutions | Oracle Cloud Partner |
 
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdfHow to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
How to Interpret Trends in the Kalyan Rajdhani Mix Chart.pdf
 
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development ProvidersYour One-Stop Shop for Python Success: Top 10 US Python Development Providers
Your One-Stop Shop for Python Success: Top 10 US Python Development Providers
 
Digital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying AheadDigital Marketing Trends in 2024 | Guide for Staying Ahead
Digital Marketing Trends in 2024 | Guide for Staying Ahead
 
JavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green MasterplanJavaLand 2024: Application Development Green Masterplan
JavaLand 2024: Application Development Green Masterplan
 
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
Skybuffer AI: Advanced Conversational and Generative AI Solution on SAP Busin...
 
A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024A Comprehensive Guide to DeFi Development Services in 2024
A Comprehensive Guide to DeFi Development Services in 2024
 
Monitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdfMonitoring and Managing Anomaly Detection on OpenShift.pdf
Monitoring and Managing Anomaly Detection on OpenShift.pdf
 
Generating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and MilvusGenerating privacy-protected synthetic data using Secludy and Milvus
Generating privacy-protected synthetic data using Secludy and Milvus
 
Nordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptxNordic Marketo Engage User Group_June 13_ 2024.pptx
Nordic Marketo Engage User Group_June 13_ 2024.pptx
 

Agile QA Process

  • 1. Agile QA Process Anand Bagmar Anand.Bagmar@thoughtworks.com abagmar@gmail.com http://www.essenceoftesting.blogspot.com Version 1.1 Agile QA Process 1 / 12
  • 2. 1. Objective QA is NOT the gatekeeper of the quality of the product. This is a TEAM responsibility. However, we, as QAs, testers, have an additional responsibility – that of being watchful and proactive to ensure the quality of the product remains a TEAM responsibility. To make this effective, more so in a distributed development and QA team working on an Agile Software project, the QA team should adhere to the guidelines and protocols recommended in this document to help achieve the following:  Enable the QA team better test the product.  Provide correct set of visibility in terms of the quality of the product.  Will be simple, intuitive, easy to follow and achieve.  Test early and provide quick feedback on the quality of the product. 2. Process The QA process for the team fits into 3 broad categories: 1. Agile Testing - from Iteration 0 to Release 2. Testing within each Iteration 3. Pre-Production / Release testing Each of these processes is detailed below. 2.1 Agile Testing lifecycle – from Iteration 0 to Release To be effective in testing on an Agile project, the QA needs to keep track of the past, the present and the future! Also, the role of a QA is very dynamic as the project moves from Iteration 0 till the release date. The pictorial representation shown below depicts the typical activities the QA is involved in, in the lifecycle of the project. Agile QA Process 2 / 12
  • 3. Iteration 0 Iteration 1 Iteration 2 Iteration 3 ... ... Iteration n Story test Showcase Showcase Showcase analysis for IPM Iteration 1, Iteration 2, Iteration n-1, Iteration 1 IPM IPM IPM Iteration 1 Complete Complete Complete Test Story testing Iteration 1 Iteration 2 Iteration n-1 Automation (manual + Story testing Story testing Story testing - strategy, automation) framework setup, etc. Complete Complete Complete Story test Iteration 1 Iteration 2 Iteration n-1 analysis for Automation Automation Automation Iteration 2 Iteration 2 Iteration 3 Iteration n-1 Story testing Story testing Story testing (manual + (manual + (manual + automation) automation) automation) Test Test Test Automation Automation Automation maint., maint., maint., execution execution execution Story test Story test Story test analysis for analysis for analysis for Iteration 3 Iteration 4 Iteration n+1 A QA does three types of activities in each Iteration: 1. Ideally, all testing (manual + automation) would be completed in the same iteration. However, in quite a few cases, I have seen that testing lags behind by some duration. Hence, in each iteration, there “may-be” some amount of work to be completed from the earlier iteration work. This is applicable mainly from Iteration 2 onwards. (See the boxes with the “green text” in the picture.) 2. Story testing for the current iteration. This testing includes manual and automation work. (See the boxes with the “black text” in the picture.) 3. Work with the Business Analysts to get visibility into the next iteration stories, and also help iron out those stories. (See the boxes with the “orange text” in the picture.) Agile QA Process 3 / 12
  • 4. 2.2 Testing within each Iteration The QA has various responsibilities in the iteration as depicted in the picture below. NOTE: Though these activities typically occur in the sequence shown in the image, many a times, based on the context, the sequence may be different, and also some of the activities may happen in parallel. Story planning session - write / refine Acceptance Criteria Showcase IPM Automation (execution, QA kickoff maintenance) ITERATION Story testing – manual Story kickoff + Exploratory Testing BA / QA Volleyball Test Scenario Writing Implement Automated Acceptance Tests Let us try to understand the semantics of these tasks. 2.2.1 Story planning session – write / refine Acceptance Criteria The planning for the iteration starts at least an iteration before the current one. Agile QA Process 4 / 12
  • 5. Example, if we are currently in Iteration 2, the planning for this iteration has happened at the latest in Iteration 1. In this step, the QA (at least one person from the QA team) should work with the Business Analyst to understand the story, and help write the acceptance criteria. This helps in various ways:  There is better visibility of the business requirements.  Better and more complete acceptance criteria can be written in the story as early as possible which will then feed into the development team.  Since the QA team now knows what stories are coming up, they can plan their testing strategy more appropriately. 2.2.2 Iteration Planning Meeting (IPM) The IPM is a forum for the QAs to understand the business priorities and which stories are going to be played in the Iteration from the business stakeholders. The QA team should make full use of this opportunity and ensure the following:  Make it effective for onsite and offshore QA team  Raise risks / issues as soon as possible  Ensure QA capacity / estimates are accounted for  Identify / highlight dependencies 2.2.3 QA kickoff for the Iteration After the IPM, the QA team should have a QA kickoff for the iteration. In most cases, the Business Analyst should be invited to ensure correct understanding by the team. Items to cover in this step include the following: ● Overall understanding of the stories ● Any potential issues to watch out for ● Identifying and setting up test data for all the stories coming up ● Identifying automation maintenance tasks based on upcoming stories ● Creating a Status Matrix to identify priorities. (See below for more details on this.) ● Each QA will then signup for testing specific stories. In case of distributed team, a good guideline to follow is that the QA team should sign up for stories that are developed in the same location. This will ensure quick turnaround time for testing each story. NOTE: In many cases the points to be included in the QA kickoff would actually be covered in the IPM itself, hence making this step redundant. Agile QA Process 5 / 12
  • 6. 2.2.4 Individual Story testing 2.2.4.1 Story kickoff Once the story signup is done, there is a Story kickoff with the Business Analyst, the developer(s) and the QA person. This is a very important discussion that gets all involved parties on the same page in understanding the requirements and the deliverables of the story. This discussion should be as detailed as possible with the QA(s) trying to identify and share the test scenarios with the BA and the developers. Also, input from the BA and the developers should be taken on any scenarios that may have been missed, or based on the understanding of the code changes involved, if any other scenarios need to be included when testing the story. 2.2.4.2 Test data preparation Following the story kickoff, the QA should start preparing / identifying the test data that would be needed to effectively test the story – manually and via automation. A different set of data should be used for manual, automated and developer testing to prevent data-conflict related test failures. This activity should be done keeping the other QA team members and development team members in the loop to ensure no overlap in the test data. Also, if any scripts / setup can be shared, that would help save time and effort and also duplication can be avoided. 2.2.4.3 Test scenario writing The test data preparation and test scenario writing activities go hand-in-hand, and not necessarily sequentially. The (manual and to-be-automated) scenarios to be tested for this story should be identified and updated in the Test Case Management tool being used. Once the test scenarios are written, these should be shared / reviewed (at least informally) with the Business Analysts and the developers developing this story, to ensure the scenarios are complete, and also the developers can probably identify missing pieces in the code at a much earlier stage. 2.2.4.4 Automate test scenarios The QA team needs to identify test scenarios that make sense to be automated, and which can be automated. Then the script automation should be started. Since the story is still not complete, there probably will be limitations how much can be done at this stage. However, in most cases, a lot of ground work and framework layers can be created without needing the completed story. After the BA / QA Volleyball, the missing pieces in the automation scripts can be completed by pointing the tests to a local / developer environment. QA’s should be mindful that the Test Automation code should be of “production” quality. They should use proper OOPs (Object Oriented Programming) concepts while implementing the Agile QA Process 6 / 12
  • 7. automated tests and ensure that any new code that is written is NOT duplicated, and structured properly. 2.2.4.5 Business Analyst (BA) / QA Volleyball Once the developers complete the story development work, there should be a BA / QA Volleyball. What this means is that the BA and QA will test the story’s acceptance criteria on the developer’s local environment. All the acceptance criteria failures should be fixed by the developer before the story can be said to be “development completed”. 2.2.4.6 Test the Story After the BA / QA volleyball is completed, a new build should be made available to the QA team to test the story based on the scripts identified and documented. NOTE: The QA team should never be working against testing the developer code. Instead they should always insist on testing the compiled and deployed binaries in the proper test environment to simulate the end-user scenarios. Once a build is available in the appropriate environment, the QA should execute the manual test scripts. There should be at least one round of Exploratory Testing for the story, and the features / functionalities around the changes that have been developed as part of the story to ensure there are no regressions or other issues in the product. Based on the time available in the iteration, this can happen either on a developer sand-box, or deployed builds. Exploratory Testing is very important and typically a lot of issues are found from this type of testing. 2.2.5 Automation All the automated tests should be run at least a couple of times per iteration, preferably via some CI (Continuous Integration) mechanism. Else the automation is not of much value. The frequency of these test runs should be fine-tuned keeping in consideration the load on the system, availability of key resources needed by the system, etc. The test run reports should then be shared with the team. Also, the automated tests should be grouped logically to facilitate running selected tests easily. Note: The list of groups would probably be an evolving list. 2.2.6 Showcase The functionality developed in the iteration is presented to the Business Stakeholders at the end of the iteration (, or, in some cases earlier too). It is important for a representative from the QA team to be part of this event in order to understand how the functionality was received by the various attendees, and also if any other new information (in terms of requirements, test scenarios) comes up in the session. Agile QA Process 7 / 12
  • 8. 3. UAT / Pre-Production / Release Testing This testing will be done using the guidelines published by the client organization. 4. Defects reporting and verification Along with the standard / regular defect reporting and verification process, a few additional activities help a lot in reducing the turnaround for defects. When reporting the defects, attach screen shots / videos (where applicable) to help the developers reproduce the problem easily. This will ensure in quicker turnaround on the defect. Example: The tool “Jing” (http://www.techsmith.com/jing/) has a free tool version that can be used to take screenshots and video snippets from your computer. 5. Other 5.1.1 Code freeze for the iteration (example: 2 days before iteration end) This will give the QA team a chance to do a quick pass of manual + exploratory testing of the stories in the same iteration. Without this there is always going to be a spillover of stories in the next iteration. 5.1.2 QA estimates A story estimate really means the total time it takes to develop and test the story. If this estimate changes to being a “development” estimate, then we need another approach. A 1 point Developer story does not equate to a 1 point QA story. Hence, each story should have QA estimates which would allow better capacity and scope planning for the iteration and release. This also facilitates data collection over a period of time w.r.t. the actual time needed by the QA team to do effective testing versus the currently allocated QA capacity, so that the management team can then take proper action to mitigate the issues. 5.1.3 Visibility An appropriate dashboard should be created that provides all relevant details about the quality of the product under test. Example list of items to include in the dashboard: ● Number of stories in the iteration in “Ready for QA” state ● Number of stories in the iteration in “In QA” state ● Number of stories in the iteration which are not yet in “Ready for QA” state Agile QA Process 8 / 12
  • 9. ● Number of Defects open (including the iteration reported in), with current assignees, priority and severity ● Number of Defects pending verification ● Automation backlog (Stories for which Automation is not yet completed) 5.1.4 Communication Effective communication and collaboration within all the team members (co-located, distributed) is critical to the success of an Agile software project. A few tips mentioned below can help in this regard:  Daily catch up calls / emails / IMs  Sharing knowledge of story across QA team  Keeping the QA status in the story updated  In case of distributed teams, if a story changes location for any reason, the QA team needs to be made aware of the change, and they need to ensure testing is not going to be affected for it.  Any change in story (addition, deletion, modification of narrative / acceptance criteria) should be communicated to at least one QA team member by the PM / BA / developer. This QA team member will then coordinate with the QA working on the story (if not the same person) and ensure all testing related to the story is adjusted appropriately. 5.1.5 Task list There should be a common page / task list that the QA team across locations can keep adding / editing tasks they encounter along the way in the Iterations. Any QA team member having bandwidth then signup for it along the way and complete it. The list can be of the following format: Number Task / Item Estimated Signup Status More notes effort (in days) Agile QA Process 9 / 12
  • 10. 5.1.6 QA section in each story Each story should have a QA specific section to help track the testing status on each story. QA Assignee QA Estimate - Text box Defects reported - Text box QA Status - each status should be separately tracked - either as a checkbox or radio button (except Automation), or as a drop down list. Status Description Kickoff Done for when the kickoff for the story was done BAV Done for when BA volleyball was done Test Scenario Done for when the test scenarios (manual and automation) were identified and documented in Quality Centre Automation what is the status of test Automation for this story > In Progress > Blocked > Done > N/A QA Complete when the story was done and tested Agile QA Process 10 / 12
  • 11. 5.1.8 QA Status Matrix This matrix can help the QA team come up with priorities of their tasks with respect to when the stories for the current iteration are going to be available. The matrix looks like this: Current Iteration # 2 Story Sept Sept Sept Sept Sept Sept Sept Oct Oct Oct Date 22 23 24 27 28 29 30 1 4 5 #10 #11 The 1st column lists the Story numbers. The 1st row lists the days of the iteration. Based on communication with the Business Analysts and developers working on each story, the QA team can use different status to track when the story will be available for them for testing. They can then use this information to prioritize their other tasks. The following different status messages can be used on this chart: Status Acronym (Estimate) Acronym (Actual / Completed) Kickoff done K K Development complete ETA D D Scenario done S S Automation A A Complete C C Agile QA Process 11 / 12
  • 12. 6. Disclaimer “QA” Vs “Tester”: There are various different terminologies and everyone probably has a different view about that. To me this is just a label. In the past 11+ years I have carried the label of “Test Engineer”, “Software Engineer”, “Software Engineer in Test”, “Software Development Engineer in Test”, Product Quality Engineer, Quality Analyst, etc. Regardless of the label, I have pretty much been doing slightly different manifestations of the same thing – and that is doing what is required to ensure the quality of the product that is being shipped out is of top quality. I use “QA” Vs “Tester” depending on who I am talking with, so that the set of people can relate better to what I am saying. Agile QA Process 12 / 12