Agile Testing Concepts

Sunil.N

©2015 Manipal Global Education

 INTRODUCTION
Agile Testing

2
©2015 Manipal Global Education
 CONCEPT
Agile Testing

3
©2015 Manipal Global Education
Client and management myths

 If you work with a non-Agile aware executive management or client, their

expectations will be:
 You will accept change continuously
 You will suddenly become more productive
 You are doing development without any discipline

4
©2015 Manipal Global Education
Why Agile?

 Software development is to be adopted for new ways of working and

technology changes.

Multi-Platform Collaborative Cloud Intelligent /

Delivery development Delivery Connected Systems

Impacts on Business and Software Development:

 Heavy demand for rapid product lifecycles  New skills and competencies needed
 Increasing interactions with customer  Increased security and privacy requirements
 Exploring adjacent or new markets  Greater need to align with strategic priorities

5
©2015 Manipal Global Education
The Agile manifesto – 2001

We are uncovering better ways of developing software by doing it and helping

others do it. Through this work we have come to value:

Individuals and processes and tools

interactions

Working software comprehensive documentation

Customer collaboration contract negotiation

Responding to change following a plan

It means that while there is value in the items on the right, we value the
items on the left more.

6
©2015 Manipal Global Education
Waterfall model

7
©2015 Manipal Global Education
Empirical processes

 The Empirical process is an inspect and adapt process where the product
is built incrementally.

Process

Inputα Outputβ

Inspect and Adapt

8
©2015 Manipal Global Education
 CONCEPT
Scrum Basics

9
©2015 Manipal Global Education
What is Scrum?

 Scrum refers to a holistic or “rugby” approach— where teams go the

distance as a unit, passing the ball back and forth—as opposed to the
traditional sequential or “relay race” approach for managing new product
development.
 It is not individual effort but the best coordination of the team that will
determine success.

10
©2015 Manipal Global Education
User Stories: Components

• A User Story describes functionality that will be useful to a stakeholder of the

system. 1 2 3

User Stories A brief

Tests that convey
description of Conversations
consists of three the story used about the story
and document
things details
for planning

4 5

Estimating
Assumptions
elements

11
©2015 Manipal Global Education
An example of user stories

Success would be …
User Story  Acceptance Test #1
 Acceptance Test #2

Success would be …
As a system admin at
 WAS is configured
Wal*Mart, I want to configure
 No critical errors occurred
WAS so I can manage my
in the process
applications
 No data was lost

12
©2015 Manipal Global Education
What is an Epic?

 As a premium site member, I want to cancel a reservation on the last

minute with no cancellation fee so that I am not charged for a travel
arrangement I no longer need.
EPIC
As an user, I want to cancel a reservation
so that I am not charged for a travel
arrangement I no longer need.

User Story
As a non-premium As a site visitor,
member, I want to I want to receive a
cancel 24 hours in confirmation of any
advance so that I am cancelled reservation
not charged for a so that I can have
travel arrangement I proof of
no longer need. 13 cancellations.
©2015 Manipal Global Education
Product Backlog

14
©2015 Manipal Global Education
Case study : Some possible user stories(1 of 6)

15
©2015 Manipal Global Education
Case study : Some possible user stories(2 of 6)

16
©2015 Manipal Global Education
Case study : Some possible user stories(3 of 6)

17
17
©2015 Manipal Global Education
Case study : Some possible user stories(4 of 6)

18
©2015 Manipal Global Education
Case study : Some possible user stories(4 of 6)

19
©2015 Manipal Global Education
Case study : Some possible user stories(5 of 6)

20
©2015 Manipal Global Education
Case study : Some possible user stories(6 of 6)

21
©2015 Manipal Global Education
 Scrum roles and responsibilities

Scrum Meeting

Review
Scrum Master
2- WEEK
SPRINT

Product Owner The Team Potentially Shippable

No Changes (In product
Commitment Duration or
Deliverable)

Retrospective

22
©2015 Manipal Global Education
Scrum roles and responsibilities—product owner

23
©2015 Manipal Global Education
Scrum roles and responsibilities—the team

 Can be shared with other teams (but it is better when not)

7 people +  Can change between Sprints (but better when they don’t)
or – 2  Can be distributed (but better when collocated)

 Possesses all the skills necessary to produce an increment

Cross- of potentially shippable product
functional  Team takes on tasks based on skills, not just the official
“role”.

Self-managing  Team manages itself to achieve the Sprint commitment.

24
©2015 Manipal Global Education
Scrum Master Roles
Scrum Master

Guides
Guidesthe
theteam’s
team’suse
useof
of Teaches Scrum to the
Serves the team Protects the Team
Scrum
Scrum team and organization

The Scrum Master The Scrum Master The Scrum Master

takes action to help protects the team ensures that all
remove from anything that standard Scrum rules
impediments to the threatens its and practices are
team’s effectiveness. effectiveness, such followed.
as outside
The Scrum Master interference or
The Scrum Master
facilitates the team’s disruption.
organizes all Scrum-
group interactions
related practices.
to help the team The Scrum Master
achieve its full will need to
potential. confront
uncomfortable
issues, both inside
and outside the
team.
25
©2015 Manipal Global Education
Scrum project roles in a nutshell

26
©2015 Manipal Global Education
Sprint planning

What is on the Product Owner’s “shopping list”?

Team understands details of what Product Owner has prioritized on Product

Backlog.

How much “money” do we have in our bank account?

Team decides how much productive time is available during the Sprint.

How many items on the shopping list can we afford to “buy”

with that “money”?

Team decides how many Product Backlog items can be committed for
completion during the Sprint.

27
©2015 Manipal Global Education
Sprint Backlog

28
©2015 Manipal Global Education
Sprint Cycle: 2 Weeks

29
©2015 Manipal Global Education
Definition of Done

In Scrum, “Done” is defined as “Potentially Shippable”.

RELEASE RELEASE RELEASE RELEASE RELEASE RELEASE

S P R I NT S P R I NT S P R I NT S P R I NT S P R I NT S P R I NT
RELEASE

S P R I NT S P R I NT S P R I NT S P R I NT S P R I NT PRE-RELEASE
S P R I NT

30
©2015 Manipal Global Education
? CHECK YOUR
UNDERSTANDING

31
©2015 Manipal Global Education
1. Which one of these life cycle models does Agile
follow?
 Waterfall Model

 Iterative and Incremental Model

 V Model

32
©2015 Manipal Global Education
1. Which of the following prioritized items does the
product backlog contain?
 Epics

 User Stories

 Both A & B

33
©2015 Manipal Global Education
1. Which of the below roles is not defined by Scrum?

 Product Owner

 Project Manager

 Developer / Tester

 Scrum Master

34
©2015 Manipal Global Education
 CONCEPT
Scrum Execution

35
©2015 Manipal Global Education
Daily Scrum Meeting

Every weekday

Whole team attends

Everyone stands

Lasts 15 minutes or less

Product Owner can attend and report

Update of artifacts after standup-Sprint backlog, Task board, and so on

36
36
©2015 Manipal Global Education
Daily Scrum Meeting (continued)

Every Developer / Tester reports the following three things:

What task was I able to accomplish since yesterday?

What task will I try to accomplish for the day?

Any issues blocking my work?

No discussions or conversations until meeting ends

37
©2015 Manipal Global Education
Conduct Daily Scrum Meeting in the following scenario:

 There are three developers and two testers working on building a product
that will automate the Bank Transactions.
• One person is working on Creating new accounts.
• Sub-tasks:
• Create a Registration/login page.
• Add options for User to select Creating new account.
• Add all the mandatory / optional fields as text box or combo boxes.
• Validate the data entered and the formats and save the data in the database.
 Generate the account number and display. One person is working on
Creating Fixed Deposit.
• Sub-tasks
• Provide the user list of FD plans and the rates.
 Check if User is already an account holder. If yes, then display a
webpage which will get the User account details so that FD account to
be linked with S/B account.
• One person is working on Generating Reports.
• Sub-tasks:
38
©2015 Manipal Global Education
Conduct Daily Scrum Meeting in the following scenario:

 Design a screen/page to provide the Report generating options.

• Create the tables and views.
• Design the report layout for different queries (ex: fetch all the details of
Customer XYZ like account summary, FD details, Home loan details and so
on.
 2 Testers testing first 2 scenarios.

39
©2015 Manipal Global Education
Sprint Backlog Updation

40
©2015 Manipal Global Education
 Kanban Task Board (1 of 4)

A Kanban board is a work and workflow visualization tool that enables you to
optimize the flow of your work. Physical Kanban boards, like the one
pictured below, typically use sticky notes on a whiteboard to
communicate status, progress, and issues.
TO DO IN PROGRESS DONE

41
©2015 Manipal Global Education
Kanban Task Board (2 of 4)

TO DO IN PROGRESS DONE

42
©2015 Manipal Global Education
Kanban Task Board (3 of 4)

TO DO IN PROGRESS DONE

43
©2015 Manipal Global Education
Kanban Task Board (4 of 4)

TO DO IN PROGRESS DONE

44
©2015 Manipal Global Education
? CHECK YOUR
UNDERSTANDING

45
©2015 Manipal Global Education
1. Product Owner has to mandatorily participate in Daily
Scrum Meeting.
 Yes

 No

 Not required

 Need basis

46
©2015 Manipal Global Education
1. Sprint backlog is updated by:

 Scrum Master

 Scrum Team

 Scrum Product Owner

 Any of the above

47
©2015 Manipal Global Education
 CONCEPT
Sprint Review and
Retrospective

48
©2015 Manipal Global Education
Sprint Review

 The purpose of the Sprint Review is:

• Demo what the team has built
• Generate feedback which the Product Owner can incorporate in the Product Backlog

 Attended by Team, Product Owner, ScrumMaster, functional managers, and any other
stakeholders

 A demo of what’s been built and not a presentation about what’s been built:
• No Power Points allowed!

 Usually lasts 1-2 hours

 Followed by Sprint Retrospective

49
©2015 Manipal Global Education
Sprint Retrospective

 1-2 hour meeting following each Sprint Demo

 Attended by Product Owner, Team, and ScrumMaster
What is it?  Usually a neutral person will be invited in to facilitate
 Presents what is working and what could work better

Why does the

Retrospective  Accelerates visibility
 Accelerates action to improve
matter?

50
©2015 Manipal Global Education
Sprint Retrospective: Four Square Method

51
©2015 Manipal Global Education
? CHECK YOUR
UNDERSTANDING

52
©2015 Manipal Global Education
1. Which practice does not fall under technical best
practices?
 Automated build and
Continuous Integration

 Automated Regression Testing

 Code Review and Rework

 None of the above

53
©2015 Manipal Global Education
1. 2. Retrospective meetings help us to:

 Identify areas of improvement

 Recognize team members

 Inspect and Adapt

 A & B Only

54
©2015 Manipal Global Education
 CONCEPT
Agile - Testing

55
©2015 Manipal Global Education
Agile Test Quadrants
Automated
and Manual Business Facing Manual

 Functional Testing  Exploratory Testing

 Examples  Scenarios
 Story tests Q2 Q3  Usability Testing
 Prototypes  User Acceptance Testing

Critique Product
 Simulations  Alpha/Beta

 Performance and load testing

 Unit Tests
 Security Testing Q1 Q4  Component Tests
 ‘ility’ testing

Automated Tools
Technology Facing
56
©2015 Manipal Global Education
Agile Test Quadrants (continued)

Quadrant 1:
 Depicts unit and component tests written by developers
 Largely automated and represent a low cost of ensuring that the system works as intended

Quadrant 2:
 Depicts user facing story and functional tests
 Tests the higher level features of the system and can be both automated and manual

Quadrant 3:

 Depicts system-level tests to determine the aggregate behavior of the system meets its
usability and functionality requirements
 Largely manual since they involve users and testers using the system in actual or simulated
deployment

Quadrant 4:
 Ensures the system meets non-functional requirements
 Supported by tools such as load, performance, or specialized tools

57
©2015 Manipal Global Education
Agile Test Quadrants (continued)

 Testers are a seamless part of the team to improve and build quality into
the system and work
 closely with the product owner. Following are the key aspects of an agile
tester.

58
58
©2015 Manipal Global Education
A typical day in the life of a developer

59
©2015 Manipal Global Education
A typical day in the life of a tester

60
©2015 Manipal Global Education
? CHECK YOUR
UNDERSTANDING

61
©2015 Manipal Global Education
1. Quadrant 2 in the Agile Test Quadrants depicts

 Non-functional tests

 User facing story and functional

tests

 Unit and Component Tests

 User facing story and functional

tests

62
©2015 Manipal Global Education