0% found this document useful (0 votes)
15 views11 pages

Agile Testing

The document outlines key principles of Agile Testing, emphasizing customer-driven development, flexibility, and early delivery through iterative processes. It discusses methodologies such as Behavior-Driven Development (BDD) and Test-Driven Development (TDD), highlighting their focus on user stories and systematic testing. Additionally, it covers frameworks like Extreme Programming (XP) and Scrum, which prioritize teamwork and frequent communication in short development cycles.

Uploaded by

begamgulshan30
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views11 pages

Agile Testing

The document outlines key principles of Agile Testing, emphasizing customer-driven development, flexibility, and early delivery through iterative processes. It discusses methodologies such as Behavior-Driven Development (BDD) and Test-Driven Development (TDD), highlighting their focus on user stories and systematic testing. Additionally, it covers frameworks like Extreme Programming (XP) and Scrum, which prioritize teamwork and frequent communication in short development cycles.

Uploaded by

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

Agile

Testing
Agile Life Cycles

• Customer-driven – Focus on meeting customer expectations.

• Bottom-up development – Development occurs incrementally from smaller


components.

• Flexibility – Ability to adapt to changing requirements.

• Early delivery – Delivering fully functional components quickly and iteratively


User stories
Customers express
requirements through user
stories, which drive short
iterations of design, coding,
and testing.

• Behavior-Driven
Development
• Use Cases
BDD
Behavior-Driven BDD scenarios are mapped to

Development decision tables, which help in


systematically analyzing and

(BDD) testing different conditions and


actions
Example: A BDD scenario for an ATM
transaction includes conditions (e.g., Decision Tables
account in credit, valid card) and actions
(e.g., debit account, dispense cash).
BDD scenarios are mapped to
decision tables, which help in
systematically analyzing and
testing different conditions and
actions
Hierarchy of Use
• Cases
1.High-level: Similar to user
Use Cases stories.
Unified Modeling • 2. Essential: Adds sequence of
Language (UML)- Use input/output events.
cases are central to UML • 3. Expanded Essential: Focuses
and are easily on pre- and post-conditions.
understood by both • 4.Real: Replaces variables with
customers and actual values for testing.
developers.
Extreme Programming

Customer-Driven
XP EMPHASIZES CUSTOMER
INVOLVEMENT THROUGH USER STORIES
AND FREQUENT RELEASES

Paired Programming
TWO DEVELOPERS WORK TOGETHER,
CONTINUOUSLY REVIEWING EACH OTHER’S
CODE.

Testing
SYSTEM TESTING IS DRIVEN BY USER
STORIES, AND THERE IS NO PRELIMINARY
DESIGN PHASE, AS XP IS A BOTTOM-UP
PROCESS.
Scrum Back to Agenda

Teamwork
SCRUM EMPHASIZES TEAMWORK
AND FREQUENT COMMUNICATION
THROUGH DAILY STAND-UP
MEETINGS.

Sprints
DEVELOPMENT IS DIVIDED INTO SHORT
ITERATIONS (SPRINTS) LASTING 2-4
WEEKS, WITH DAILY BUILDS AND
TESTING.

Testing Level
UNIT TESTING OCCURS DAILY, WHILE
INTEGRATION/SYSTEM TESTING
HAPPENS AT THE END OF EACH
SPRINT.
Test-First Approach
Tests are written before code, and code is written to
pass these tests.

Fault Isolation
TDD simplifies fault isolation as tests are run on
non-existent code first, ensuring that the code

Test-Driven
meets the test requirements.

Developmen
t (TDD)
Agile Model-Driven
Development (AMDD)

Modeling: AMDD
incorporates modeling into
agile development, allowing
for a design step before
implementation.
Compromise : It bridges
the gap between traditional
design-heavy approaches
and agile’s iterative,
bottom-up development
Strategy and
Model-Driven Tactics
Agile MDAD combines the
strategic (design) and
Development tactical
(implementation)
aspects of
development.
Testing Levels
It includes unit,
integration, and
system testing,
ensuring
comprehensive
coverage.
Thank you

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy