Scribd
Upload
379 views14 pages

Agile Testing PDF

This document provides an overview of agile testing. It discusses the agile manifesto, what agile testing is, how it differs from waterfall testing, agile testing principles, lifecycle, quadrants, advantages and disadvantages, methodologies like scrum and kanban, and testing methods like behavior driven development and test driven development. It concludes with a case study on a highly automated agile testing process.

Uploaded by

Syeda Narjis Batool
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
379 views14 pages

Agile Testing PDF

This document provides an overview of agile testing. It discusses the agile manifesto, what agile testing is, how it differs from waterfall testing, agile testing principles, lifecycle, quadrants, advantages and disadvantages, methodologies like scrum and kanban, and testing methods like behavior driven development and test driven development. It concludes with a case study on a highly automated agile testing process.

Uploaded by

Syeda Narjis Batool
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 14

Click to edit Master title style

Agile Testing
Group:
Syed Muhammad Jaffer Abbas
Syeda Narjis Batool
Priyanka Ramrakhyani
Sana Saleem
Click to edit
Contents to be
Master
Covered
title style

• Agile Manifesto
• What is Agile Testing?
• Agile Testing Vs Waterfall Testing
• Agile Testing Principles
• Agile Testing Lifecycle
• Agile Testing Quadrants
• Advantages and Disadvantages of Agile Testing
• Agile Methodologies
• Agile Testing Methods
• Conclusion
• Case Study
Click to
Agile Manifesto
edit Master title style

• The Agile Manifesto was published by a team of software developers in 2001, highlighting the
importance of the development team.

• 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 interactions over processes and tools.
 Working software over comprehensive documentation.
 Customer collaboration over contract negotiation.
 Responding to change over following a plan.
• That is, while there is value in the items on the right, we value the items on the left more.
Click to
What is Agile
edit Master
Testing?
title style

• Agile testing is a software testing process that follows the principles of agile software
development.

• Agile testing aligns with iterative Development Methodology in which requirements develop
gradually from customers and testing teams.

• The development is aligned with customer requirements.


Click to
Agile Testing
edit Master
Vs Waterfall
title style
Testing

S.No Agile Testing Waterfall Testing

1. Testing is not a separate phase and Testing is a separate phase. All levels and
occurs concurrently with development. types of testing can begin only after the
completion of development.
2. Acceptance Testing is done after every Acceptance Testing is done only at the end of
iteration and customer feedback is the project.
sought.
3. No time delays between coding and Usual time delays between coding and testing.
testing.
4. Continuous testing with overlapping test Testing is a timed activity and test levels
levels. cannot overlap.
5. Agile testing is well suited for large Waterfall testing can be adopted for all sorts of
projects. projects.
Click to
Agile Testing
edit Master
Principles
title style

 Testing moves the project forward.


 Testing is not a phase.
 Decrease time of feedback response.
 Keep the Code Clean.
 Test Driven.
Click to
Agile Testing
edit Master
Lifecycle
title style
Click to
Agile Testing
edit Master
Quadrants
title style
Click to editand
Advantages Master
Disadvantages
title style of Agile Testing

Advantages Disadvantages

• Customer satisfaction by rapid, continuous • Documentation could get lengthy.


delivery of useful software.
• Cost more as compare
• People and interactions are emphasized rather to waterfall or interactive model.
than process and tools.
• It is not useful for small projects.
• Working software is delivered frequently.
• The project can easily get taken off track if the
• Continuous attention to technical excellence customer representative is not clear what final
and good design. outcome that they want.
• Regular adaptation to changing • Only senior programmers are capable of taking
circumstances. the kind of decisions required during the
development process.
Click to
Agile Methodologies
edit Master title style

Scrum is an Agile eXtreme DSDM focuses on Kanban focuses on Feature Driven


development Programming is frequent delivery of managing work with Development
method that customer-centric the product, involving an emphasis on just- (FDD) involves
emphasizes on and focuses on users actively and in-time (JIT) delivery,
designing and
team-centric constantly changing empowering the while not overloading
teams to make quick the team members. building features.
approach. requirements.
decisions.
Click to
Agile Testing
edit Master
Methodstitle style
• Behavior Driven Development (BDD)
improves communication amongst
project stakeholders so that all
members correctly understand each
feature before the development
process starts. There is continuous
example-based communication
between developers, testers, and
business analysts.

• TDD can be defined as a programming


practice that instructs developers to
write new code only if an automated
test has failed. Test-Driven
development is a process of
developing and running automated test
before actual development of the
application.
HighlytoAutomated
Click edit Master
Agile
titleTesting
style Process: An Industrial Case
Study
Click to edit Master title style

“
“If you don’t like unit testing your
product, most likely your customers
won’t like to test it either.”
– Anonymous
Click to edit Master title style

Thank You

You might also like