1. AGILE TESTING

2. INTRODUCTION
 General Concept
 Methodology
 Challenges for Agile Testing
 Test Levels
 First View, Second View and Third View of Agile Testing
 Agile Testers
 Benefits of being an Agile Tester
 Conclusion

3. GENERAL CONCEPT
 The Word “Agile” means "Moving Quickly" and this explains the
whole concept of Agile Testing.
 Agile testing involves testing from the customer perspective as early
as possible or as soon as code becomes available.
 In agile testing most of the organisation use “Quality Center” to raise
the defects.
 If we do only “Manual Testing” the whole software using “Agile
Testing” approach, then it may result in a buggy software as it is not
possible to test the entire build manually before each release .
 So, This is commonly done by using “Automated Acceptance
Testing”.

4. METHODOLOGY
 Development is incremental rather than sequential.
 People and interactions are emphasized, rather than
processes and tools. Customers, developers, and testers
constantly interact with each other.
 Working software is the priority rather than detailed
documentation.

5.  Customer collaboration is used, rather than contract negotiation. All
agile projects include customers as a part of the team. When
developers have questions about a requirement, they immediately
get clarification from customers.
 Responding to change is emphasized, rather than extensive
planning i.e. changing the plan to accommodate any changes in
assumptions for the plan, rather than stubbornly trying to follow the
original plan .

6. CHALLENGES FOR AGILE TESTING
 What information is the testing based on?
 What to test and what are the expected results?
 How to make testing, development and business
collaborate?
 How to involve customer and business people in testing?
 How to produce and communicate relevant information
promptly?

7. TEST LEVELS

8. FIRST VIEW OF AGILE TESTING
 Extreme Testing :
> Demands an on-site customer for continual feedback and to
define and carry out functional acceptance testing.
> Test scripts shall be written before the code is written and it should
be tested as automated .
> Integration testing and Unit testing should perform several times a
day.
> “Automated Unit Testing” should be done.

9. SECOND VIEW OF AGILE TESTING
 Exploratory Testing :
> To the extent that the next test we do is influenced by the result of the
last test we did, we are doing exploratory testing.
> In exploratory testing, tests are designed and executed at the
same time, and they often are not recorded.
> Exploratory testing involves simultaneously learning, test design,
test execution and test result interpretation .
> The key is the engagement of the tester, and his or her
responsibility for managing the time not the test technique , items
being tested or test review.

10. THIRD VIEW OF AGILE TESTING
 Development and testing must collaborate and agree on
the test procedures and quality goals for each increment.
> Not only functionality but also non-functional features
> Test requirements
> Expected results
 Test procedures must be easily selected to suit the
changing situations and requirements i.e. Test procedure
should not be fixed.

11. Agile Testers
 Use reusable checklists to suggest tests
 Focus on the essence of the test rather than the
incidental details
 Use lightweight documentation styles/tools

Leverage documents for multiple purpose

12. BENEFITS OF BEING AN AGILE TESTER
 Work together as one team towards a common goal
 Less risk of squeezed test period
 Test all the time, not just at the end

13. CONCLUSION
 Agile Testing, being a new methodology is very useful,
less time consuming, effective as per customer’s point of
view.
 We can perform automated testing in most of the time in
order to get a bug free software.
 Most valuable portion of this methodology is developers,
testers and customers work together as a team for better
performance of the software.

14. THANK YOU