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

Loading…

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

Like this presentation? Why not share!

Agile Testing

on

  • 2,328 views

dbg Agile Testing Presentation, demonstrating the use of Test Charters, Exploratory Testing, Session Based Testing and Testing Tours. With thanks to James Bach, Lisa Crispin, Janet Gregory and James ...

dbg Agile Testing Presentation, demonstrating the use of Test Charters, Exploratory Testing, Session Based Testing and Testing Tours. With thanks to James Bach, Lisa Crispin, Janet Gregory and James Whittaker

Statistics

Views

Total Views
2,328
Views on SlideShare
2,320
Embed Views
8

Actions

Likes
2
Downloads
50
Comments
0

2 Embeds 8

http://www.linkedin.com 7
https://www.linkedin.com 1

Accessibility

Categories

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.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Fixing a bug in a Live Environment can cost 10 to 100 times the amount in lost business, development effort and technical cost in Live, than if it is found in the Development or Testing Phases. Generally, if a defect is found later in the release schedule it is going to be more expensive to fix down the line. This is an critical factor in pretty much all IT projects, but is perhaps more keenly felt in more traditional waterfall projects where a fix deadline, payment milestones or SLA’s are not met.
  • Mars Climate Orbiter failed partly due to a software error where the thrusters that controlled the rate of descent where expecting data in Metric (newtons), but was supplied in Pound Force (the standard US measurement) NASA LOST £125 million

Agile Testing Agile Testing Presentation Transcript

  • Introduction to Agile Testingwww.dbg.co.uk
    Prepared by Daniel Billing
    PUBLIC
  • Agenda
    Why Test?
    Some Questions
    The Cost of Testing
    Agile Testing Techniques
    Workshop
    Testing Tours
  • A few questions?
    QA and Testing is all about asking questions, so here are a few for you to think about...
    Why Test?
    What do you believe Testing is?
    What do you believe Testing should be?
    What are your problems with Testing?
    What could be done to improve the process of Testing?
  • The Cost of Testing
  • The Cost of Testing
  • The Cost of Not Testing (or doing enough)
  • Agile Testing Techniques
  • Features of Agile Testing
    Technique agnostic
    Flexible and rapid – reduce the feedback loop
    Should be continuous, ideally using a robust automated framework
    No longer a ‘testing phase’, where code is thrown over the Testing fence
    Testers are no longer ‘Quality Police’
    Providing information and suggestions on quality
    Integration with the development process
    Reusable, lightweight documentation styles and tools
  • Agile Testing Techniques
    TDD (Test Driven Development)
    Automated Functional Testing
    Exploratory Testing
    Session Based Testing
    Test Charters
    Testing Tours
  • Exploratory Testing
    Manual
    Simultaneous learning, test design and execution
    Cognitive engagement with the process
    Use of deductive reasoning
    Less preparation up front, important bugs are found quickly
    Can be difficult to measure/quantify
    "a style of software testing that emphasizes the personal freedom and responsibility of the individual tester to continually optimize the quality of his/her work by treating test-related learning, test design, test execution, and test result interpretation as mutually supportive activities that run in parallel throughout the project.“ CemKaner
  • Test Charters
    A way of recording Exploratory Testing effort
    Defining a mission statement for testing – a statement of test objectives
    Capturing test metrics
  • Session Based Testing
    Developed by James Bach www.satsifice.com
    Combines Exploratory Testing with some accountability
    A fixed, uninterrupted period of time spent testing – no more than two hours
    Clear focus
    Includes Test Session information:
    Charter.
    Area tested.
    Detailed notes on how testing was conducted.
    A list of anybugs found.
    A list of issues (open questions, product or project concerns)
    Any files the tester used or created to support their testing
    Percentage of the session spent on the charter vs investigating new opportunities.
    Percentage of the session spent on:
    Testing - creating and executing tests.
    Bug investigation / reporting.
    Session setup or other non-testing activities.
    Session Start time and duration.
    Debrief within the test team, and results parsing
  • Testing Tours
    Developed by Dr James Whittaker
    Formerly of Microsoft, now at Google
    www.googletesting.blogspot.com
    Uses a ‘Tourist’ analogy
    Allows freedom to discover
    Requires structure to ensure coverage
    Uses ‘districts’ to allow testers to organise tests effectively
    Business District – where things get done
    Historical District – legacy code, out of date functions
    Tourist District – areas that novice users (tourists) will be attracted to, but experienced users (citizens) won’t visit
    Entertainment District – Nice to haves, and supportive features (once all the key features are tested)
    Hotel District – where software is ‘at rest’, maybe background tasks, batch processes
    Seedy District – Potential areas of vulnerability, ‘unsavoury’ functions and code
  • Testing Tours
    The Guidebook Tour – doing everything that is in the handbook, down to the letter
    The Money Tour – areas of the system that draw users, or have a high financial impact on the business; executing sales team demos against the software
    The Landmark Tour – testing the key features
    The Intellectual Tour – How do we make the software work as hard as possible? How do we stretch it to its limits?
    The FedEx Tour – testing the software by focussing on data management
    The After Hours Tour - Maintenance tasks, data back up and archiving, batch processing
    The Garbage Collector Tour – Taking the shortest route possible to reach your goal, collecting ‘garbage’ as you go
  • Workshop
  • Testing Tours Workshop
    Choose a Testing Tour
    Choose a high profile web application to test
    Plan your test charter – what are you going to test?
    Run your tests – find bugs!
    Record your test charter
    Report back to the group
  • Testing Tours Workshop
    The Test Tour you have chosen
    Test Charter – What are you going to Test? Your testing mission statement!
    Area tested. – What functionality is under test?
    Detailed notes on how testing was conducted.
    A list of anybugs found.
    A list of issues (open questions, product or project concerns)
    Any files the tester used or created to support their testing
    Percentage of the session spent on the charter vs. investigating new testing opportunities
    Percentage of the session spent on:
    Testing - creating and executing tests.
    Bug investigation / reporting.
    Session setup or other non-testing activities.
    Session Start time and duration.
    Feedback to the Group at the end! IMPORTANT