• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Agile testing

Agile testing



Agile Testing vs. Traditional Testing

Agile Testing vs. Traditional Testing



Total Views
Views on SlideShare
Embed Views



1 Embed 6

http://www.linkedin.com 6



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
  • 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 Agile testing Presentation Transcript

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