Agile Testing Practices
Agile Manifesto…
Agile SW Development
Feel empowered with                    AgileIt’s exciting to break the silos and be an equal team memberAgile is perceived...
Agile Testing MindsetResult-oriented…craftsman-like…collaborative…eager tolearn…passionate about delivering business value...
Principles of Agile Tester Agile
Types of Tests
Basic Recipes1. Iterate through quadrant rapidly working in smallincrementsWrite a test for some small chunk of a feature,...
Acceptance TestingTests = details to a storyTests => add value and clarify scopeAnswer the question: If I tested for X,Y,Z...
What to test ?…“Don’t try to do more. Just do more of the right things.”Start at broad overview level while providing just...
Patterns and anti-patternsDecoupled. Each test stands on its own, not dependingupon or being impacted by results of other ...
Exploratory Testing
Exploratory Testing technique
Exploratory Testing Ideas
What Should Happen Right         After
“       Jenkins - The whole         team’s domain• “CI doesn’t get rid of bugs but makes it  dramatically easier to find a...
More of JenkinsAutomated Unit and Functional and evenPerformance should be deployed through JenkinsNotification is built-i...
Build Pipelinehttp://build.tstllc.net/jenkins/view/Travel/
References• http://www.slideshare.net/codecentric/exploratory-testing-  inagileoverviewmeettheexpertselisabethhendrickson•...
Upcoming SlideShare
Loading in …5
×

Agile test practices

790 views

Published on

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
790
On SlideShare
0
From Embeds
0
Number of Embeds
23
Actions
Shares
0
Downloads
7
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Not reporting to POAnyone can be a Tester on a teamTester is a role
  • The whole idea is to test continually and incrementally while code is being developedRetrospective, design storms, story time
  • The point is Testing is not left until the end
  • Agile test practices

    1. 1. Agile Testing Practices
    2. 2. Agile Manifesto…
    3. 3. Agile SW Development
    4. 4. Feel empowered with AgileIt’s exciting to break the silos and be an equal team memberAgile is perceived to be all about “speed” …butIt’s more about quality (if not it should be questioned)Everyone on the team owns QualityAgile testers do more than perform testing tasksAgile testers work to ensure their team delivers the quality theircustomers needTesters advocate for quality on behalf of customer whileassisting developers to deliver maximum value
    5. 5. Agile Testing MindsetResult-oriented…craftsman-like…collaborative…eager tolearn…passionate about delivering business valueLearn to work with what you have at any given point of time Example: UI may not be ready but a piece of API may beContinually looking for ways the team can do better job ofproducing high-quality software (not just testers) New tools/ways Self-improvingWillingness to take any new role / task Design discussions Suggestions for testability Suggestions for usability
    6. 6. Principles of Agile Tester Agile
    7. 7. Types of Tests
    8. 8. Basic Recipes1. Iterate through quadrant rapidly working in smallincrementsWrite a test for some small chunk of a feature, write thecode, once the test is passing, perhaps automate more testsfor it, do exploratory testing on it, then add the next smallchunk and go through the whole process again.2. There are no hard and fast rules about what goes in whatquadrant. Think through them as you do yourrelease, theme, and iteration planning, so your whole teamstarts out by thinking about testing first.3. Call out risk factors early and understand the types ofrelevant testsExamples: a major code refactoring might trigger a targetedregression testing.A major cross-cutting feature or re-achitecture might requireperformance/load test
    9. 9. Acceptance TestingTests = details to a storyTests => add value and clarify scopeAnswer the question: If I tested for X,Y,Z would that makethe story accepted by a customerThe story does not get delivered unless the acceptancetests pass => “Story is Done”
    10. 10. What to test ?…“Don’t try to do more. Just do more of the right things.”Start at broad overview level while providing just enoughdetails/dataThe focus is on functionality and usability rather thantechnical aspects (i.e. black box testing)Composition of essential acceptance tests = Vital happypaths + essential negative tests
    11. 11. Patterns and anti-patternsDecoupled. Each test stands on its own, not dependingupon or being impacted by results of other tests.A test must always truly exercise a system as close toproduction as possible.Think in terms of narrative, flow. Think in terms ofbounded contexts, and who the audience is for thatcontextDon’t write ATs @ unit- testing level (no field validationtests…) Unit tests are implementation-specific, ATs are NOTAvoid long multi-purpose tests
    12. 12. Exploratory Testing
    13. 13. Exploratory Testing technique
    14. 14. Exploratory Testing Ideas
    15. 15. What Should Happen Right After
    16. 16. “ Jenkins - The whole team’s domain• “CI doesn’t get rid of bugs but makes it dramatically easier to find and remove” -Martin Fowler• Integration is about communication• Keeps the pulse of the latest development
    17. 17. More of JenkinsAutomated Unit and Functional and evenPerformance should be deployed through JenkinsNotification is built-inVisible to entire teamReporting is built-inThe whole team needs to exploit CI for early defectdetection
    18. 18. Build Pipelinehttp://build.tstllc.net/jenkins/view/Travel/
    19. 19. References• http://www.slideshare.net/codecentric/exploratory-testing- inagileoverviewmeettheexpertselisabethhendrickson• Agile Testing book by Lisa Crespin

    ×