• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile test practices

Agile test practices






Total Views
Views on SlideShare
Embed Views



1 Embed 10

http://www.linkedin.com 10



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • 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 Agile test practices Presentation Transcript

  • 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 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
  • 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
  • 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, 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
  • 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”
  • 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
  • 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
  • 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 and remove” -Martin Fowler• Integration is about communication• Keeps the pulse of the latest development
  • 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
  • Build Pipelinehttp://build.tstllc.net/jenkins/view/Travel/
  • References• http://www.slideshare.net/codecentric/exploratory-testing- inagileoverviewmeettheexpertselisabethhendrickson• Agile Testing book by Lisa Crespin