Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Exploratory testing workshop

3.956 visualizaciones

Publicado el

A talk I gave on exploratory testing using a Lego Robot.

Publicado en: Tecnología, Educación
  • Inicia sesión para ver los comentarios

Exploratory testing workshop

  1. 1.
  2. 2. Exploratory Testing Workshop<br />Parts of this class have been excerpted from: <br /><ul><li>Rapid Software Testing, by James Bach, james@satisfice.com
  3. 3. Black Box Software Testing, by CemKaner, kaner@kaner.com</li></ul>Name: Anne-Marie Charrett<br />E-mail: amcharrett@testingtimes.ie<br />WEB: www.testingtimes.ie<br />Phone: 085 289 6263<br />
  4. 4. 3<br />
  5. 5. Exploratory testing is an approach to software testing ….<br />described as <br />simultaneous learning, <br />test design <br />and test execution.<br />
  6. 6. tester's responsibility for managing his or her time<br />cognitive engagement of the tester <br />
  7. 7. Exercise <br />
  8. 8. Observation<br />Be aware of what you are looking out for<br />Watch out for the assumptions you make<br />Your “idea” or “model” of your what you’re testing often determines<br />What you decide to test <br />What you decide is a bug<br />Remember. We are all biased! <br />
  9. 9. Tester Mindset<br />Curious <br />Skeptical<br />Self Management<br />Communication<br />Observant <br />
  10. 10. Tunnel Vision Trap<br />Bias limits the number of bugs you find<br />Diversify your strategy<br />
  11. 11. Context Trap<br />What is your mission?<br />Who are your stakeholders?<br />
  12. 12. Quantity Trap<br />Too Little<br />Too Much<br />Just Right<br />
  13. 13. Generic Risk List<br />Complex Anything disporportionality large, intricate or convoluted<br />New Anything that has no history in the product<br />Changed Anything that has been tampered or "improved"<br />Upsteam Dependency Anything whose failure will cause cascading failures in the rest of the system<br />Downstream Dependency Anything that is especially sensitive to failures in the rest of the system<br />Critical Anything whose failure could cause substantial damage<br />Precise Anything that must meet requirements exactly<br />Strategic Anything that has special importance to your business, such as a feature that sets you apart from the competition<br />Third-Party Anything used in the product, but developed outside of the project<br />Distributed Anything spread out in time or space, yet whose elements must work together<br />Buggy Anything known to have lots of problems<br />Recent Failure Anything with a recent history of failure<br />Focus<br />
  14. 14. How do we choose where to look?<br />How do we see what is NOT there? <br />Depends a lot on our choice of Model<br />Input Output<br />State Machine<br />Event Driven Behavior<br />Requirements <br />Functionality<br />Data Driven <br />Modeling Trap<br />Diversify<br />
  15. 15. Tilted Twister<br />This is a mind storm Tilted Twister<br />It solves Rubix Cubes <br />It consists of software and hardware<br />I will be video recording this <br />I want you to use exploratory testing to test it<br />
  16. 16. Mission: Tilted Twister Data<br />Project Manager: A client requested a rubix cube solver, the developers gone on holiday. I want you to test this, before the client turns up.<br />Find Top 5 Issues in the next 20 mins<br />Any questions? <br />
  17. 17. Turbo Twister Instructions<br />Orange Button = Select <br />Light Grey Buttons – Move through options<br />Dark Grey – Back or Exit <br />My Files->Software Files->Tilted Twister<br />
  18. 18. Problems Found<br />Cannot detect colour differences<br />Motor arm overshoots<br />Hard to know how to turn it on<br />Calibration Rubix cube is too big<br />Takes to long to work out solution & then runs out of memory<br />
  19. 19. Debrief <br />What was your mission?<br />What problems did you find?<br />How did you know they were problems?<br />How did you find them?<br />What questions did you ask?<br />Can you report credibly?<br />Did you need more time?<br />
  20. 20. Need Exploratory Testing and Automation<br />Developer needs to adapt & learn tester mindset for:<br />TDD<br />Unit Testing <br />ET thinking in developing automated tests.<br />Exploratory Testers need Testability<br />
  21. 21. Tips & Tricks To Test Effectively<br />Know your mission, stakeholders<br />Too much, Too little, Just Right<br />Focus – Defocus<br />Boundary Testing<br />Pair Testing <br />Scenario Testing<br />Negative Testing<br />Caricatures <br />20<br />
  22. 22. Follow up <br />Mind Map of Heuristics<br />Hand Out <br />Email me: amcharrett@testingtimes.ie<br />FREE Online Coaching – skype: charretts<br />

×