Agile Testing
Agile Testing
Testing
Agile Life Cycles
• Behavior-Driven
Development
• Use Cases
BDD
Behavior-Driven BDD scenarios are mapped to
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