Effective Testing in Agile


Published on

Published in: Technology, Education
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Build infrastructure and designing for testability.Doing the best work and delivering the best possible productFocus on continual improvement
  • Reports, Daily statusUnderstand what customer really needHelp to develop project own jargon. Using “Power of Three”We need courage to make mistake, because that’s only way to learn the lesson. We need courage to ask for helpUse simple solution for the problemAlways try new technologies on practiceAdd changes during iterationWhen build fails team should self organize to fix this asapAgile team give team members equal weightWork as one team and love what you are doing
  •  Support team Critique product Ensure business needs met Ensure technological needs met
  • Without Quadrant One, the other quadrants will be much harder
  • “ility”SecurityMaintanabilityInteroperability(end-to-end functionality)Compatibility(browsers, OS)Instalability
  • Effective Testing in Agile

    1. 1. Effective Testing in Agile<br />Kyiv QA Meet Up #1<br />
    2. 2. What this talk about?<br />Agile<br />Agile Tester<br />Testing Quadrants<br />
    3. 3.
    4. 4.
    5. 5. Scrum Cycle<br />
    6. 6. Kanban<br />
    7. 7. Agile Team<br />
    8. 8. 10 Principles for Agile Tester<br />Provide Continuous Feedback<br />Deliver value to the customer<br />Enable face-to-face communication<br />Have courage<br />Keep it simple<br />Practice continuous improvement<br />Respond to change<br />Self-organize<br />Focus on people<br />Enjoying his work<br />
    9. 9. You have rights to<br />bring up issues related to testing, quality and process at any time<br />ask questions of your team members and receive timely answers<br />ask help from everyone on the team(s)<br />estimate testing tasks and have these included in the story estimates<br />the tools you need to perform testing tasks<br />expect your entire team, to be responsible for quality and testing<br />
    10. 10.
    11. 11. Technology-Facing Tests That Support The Team (Q1)<br />What is it?<br />Unit Tests<br />Component Tests<br />Integration Tests<br />Who should do this?<br />Programmers<br />When to start doing?<br /><ul><li>Continually
    12. 12. With running in the CI System</li></li></ul><li>Q1 Tools<br />Source code management<br />SVN, GIT<br />Integrated development environment<br />Eclipse, IntelliJ Idea, Net Beans<br />Build/CI tools<br />Ant, Maven, Jenkins, TeamCity<br />Unit Test Tools<br />jUnit, testNG, jMock<br />
    13. 13. Business-Facing Tests That Support The Team (Q2)<br />What is it?<br />Story Tests<br />Functional Tests <br />Mock Ups<br />Who should do this?<br />Testers, programmers, analysts<br />When to start doing this?<br />From start to the end of iteration<br />
    14. 14. Q2 Tools<br />Story tests<br />Checklists<br />Mind maps<br />Mockups<br />Flow diagrams<br />Automation<br />BDD(jBehave, Concordion, Rspec, Cucumber, Fitness)<br />Tools(Selenium, Watir, QTP, Silk, Robot Framework)<br />
    15. 15. Business-Facing Tests That Critique The Product (Q3)<br />What is it?<br />Demo<br />Scenario Testing<br />Exploratory Testing<br />Usability<br />API, Services<br />Who should do this?<br />Customer, Tester, Programmers<br />When to start doing this?<br />As early as possible<br />
    16. 16. Q3 Tools<br />Q2 Tools<br />Monitoring tools<br />Data Generation Tools<br />http://www.generatedata.com/<br />Exploratory Testing Tools<br />Rapid Reported<br />Session Tester<br />
    17. 17. Technology-Facing Test That Critique The Product (Q4)<br />What is it?<br />Performance<br />Load, Stress Testing<br />“ility”<br />Recovery<br />Data Migration<br />Who should do this?<br />Team<br />When to start doing this?<br />“Depends on”<br />
    18. 18. Q4 Tools<br />LoadTesting Tools<br />Load Runner<br />Silk Performer<br />jMeter<br />The Grinder<br />jUnitPerf<br />DB Profilers<br />Online monitoring<br />BroserMob<br />
    19. 19. Use Agile Testing Quadrants to define test activities you need<br />Practice with Test Automation to reduce repetitive work<br />Practice with Exploratory Testing at least one time per iteration<br />Document only what is useful<br />