Agile testing

895 views

Published on

Agile Testing vs. Traditional Testing

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
895
On SlideShare
0
From Embeds
0
Number of Embeds
12
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • One popular topic in the discussion thread is the definition of success and failure. How do we know when a project is one or the other? Some of the more obvious ways of measuring success follow:Has the project satisfied the business requirements of the primary stakeholders?Were the deliverables produced on time and within the budget (as amended by formal change control)?Do the business owners believe the project was successful?Has the project delivered the business value promised?
  • Traditional Testing Model:Separate test group from developmentTests are derived from detailed requirements instead of being part of requirementsTesting is conducted after development is completeDefects are written to communicate with developersDevelopers and Testers are working against each otherAutomation is a nice-to-have instead of a must-have
  • Agile software development refers to a group of software development methodologies based on iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. The term was coined in the year 2001 when the Agile Manifesto was formulated.
  • Extreme Programming (XP)CrystalAdaptive Software Development (ASD)ScrumFeature Driven Development (FDD)Dynamic Systems Development Method(DSDM)
  • Scrum is an iterative, incremental framework for project management and agile software development.“Scrum Master”, who maintains the processes (typically in lieu of a project manager) “Product Owner”, who represents the stakeholders, represents the business “Team”, a cross-functional group of about 7 people who do the actual analysis, design, implementation, testing, etc.
  • There was an important job to be done andEverybody wassure Somebody would do it.Anybody could have done it, but Nobody did it.Somebody got angry about that because it wasEverybody’s job. Everybody thought Somebody could do it butNobody realized Everybodywouldn’t do it.In the end Everybody blamed SomebodyWhen Nobody did what Anybody could havedone.
  • Agile testing

    1. 1. 1<br />Agile Testing<br />Mary Jiang<br />May 5, 2010<br />
    2. 2. About Perficient<br />Perficient www.perficient.com<br /><ul><li>leading information technology consulting firm serving clients throughout North America
    3. 3. Founded in 1997
    4. 4. ~$250 million in annualized revenues
    5. 5. Locations in 19 major North American markets
    6. 6. Global Delivery Centers in Europe and China
    7. 7. 1400+ technology consultants
    8. 8. Served 600+ clients</li></ul>Perficient China<br /><ul><li>Fully owned and operated since 2004
    9. 9. Operating at SEI CMMI Level 5
    10. 10. Worldwide Leader! – One of the first to achieve CMMI using an Agile Methodology</li></li></ul><li>About Me<br />Mary Jiang (Jiang Rong)<br /><ul><li>Test lead of Perficient China
    11. 11. 8+ years software development and testing experience
    12. 12. CMMI, SDLC/waterfall and agile methodologies
    13. 13. 2+ Agile experience
    14. 14. Certified Scrum Master
    15. 15. Once worked in UTStarcom, Siemens and Alibaba</li></li></ul><li>Agenda<br /><ul><li>Warm-up
    16. 16. Quality & Testing
    17. 17. Agile Testing
    18. 18. Q&A</li></li></ul><li>What is a successful software project?<br /><ul><li>Satisfied the business requirements?
    19. 19. On time and within the budget?
    20. 20. Business owners believe the project was successful?
    21. 21. Delivered the business value?</li></li></ul><li>Reality vs Ideality<br />Source: Vernon Stinebaker<br />
    22. 22. Project Triangle<br />
    23. 23. Story of Squirrel Burgers<br />
    24. 24. Agenda<br /><ul><li>Warm-up
    25. 25. Quality & Testing
    26. 26. Agile Testing
    27. 27. Q&A</li></li></ul><li>No bugs?<br />Meet requirements?<br />Quality Customer satisfaction<br /> Customer satisfaction Market success<br /> Market success Profit<br />What is Quality?<br />WIN & WIN<br />
    28. 28.
    29. 29. From Testing to Quality Assurance<br />Quality Assurance<br />
    30. 30. 13<br />V-Model in traditional testing<br />
    31. 31. The pain in traditional testing<br />
    32. 32. Tester’s pain in the traditional testing<br />
    33. 33. Agenda<br /><ul><li>Warm-up
    34. 34. Quality & Testing
    35. 35. Agile Testing
    36. 36. Q&A</li></li></ul><li>Are you “Agile”?<br />
    37. 37.
    38. 38. Scrum Model<br />
    39. 39. 20<br />Agile Testing in one sprint of Scrum<br />
    40. 40. 21<br />Agile Testing in Perficient<br />
    41. 41. Testing Model in Perficient China<br />22<br />
    42. 42. Agile Testing Pyramid<br />
    43. 43. One example about Automation Testing<br /><ul><li>A demo for Fitness and Selenium</li></li></ul><li>
    44. 44.
    45. 45. A story about whose job is it?<br />This is a story about four people namedEverybody,Somebody, Anybody and Nobody. <br />
    46. 46. Reference<br />http://www.agiletester.ca/ (Lisa Crispin, Janet Gregory)<br />http://www.agilealliance.org<br />
    47. 47. Start your Agile road now!<br />

    ×