LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestras Condiciones de uso y nuestra Política de privacidad para más información.
LinkedIn emplea cookies para mejorar la funcionalidad y el rendimiento de nuestro sitio web, así como para ofrecer publicidad relevante. Si continúas navegando por ese sitio web, aceptas el uso de cookies. Consulta nuestra Política de privacidad y nuestras Condiciones de uso para más información.
Why do I do Exploratory Testing Its Fun, creative, keeps me interested. Challenges me. Ask from some definitions of ET? Ask anyone here know ET? Ask developer? Tester, Test Manager?
Critical ThinkingScientific Thinkingposing useful questionsobserving what’s going ondescribing what you perceivethinking critically about what you knowrecognizing and managing biasdesigning hypotheses and experimentsthinking despite already knowinganalyzing someone else’s thinkingreasoning about cause and effecttreating “facts” as merely what we believe we know as of this moment
Developers Tunnel vision: Biased to test for what is there
Deciding where to Test –add value to your testing
Oracles - How do we know it’s a problem?
Did you ask useful questions?Did you know your mission?Did you Know who you’re testing for?Did you make a conscious decision on what to test ? Where you aware of any bias? Did you make any assumptions?
Exploratory testing workshop
Exploratory Testing Workshop<br />Parts of this class have been excerpted from: <br /><ul><li>Rapid Software Testing, by James Bach, email@example.com
Black Box Software Testing, by CemKaner, firstname.lastname@example.org</li></ul>Name: Anne-Marie Charrett<br />E-mail: email@example.com<br />WEB: www.testingtimes.ie<br />Phone: 085 289 6263<br />
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 />
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 />
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 />
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 />
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 />
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 />
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 />
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 />
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 />
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 />
Follow up <br />Mind Map of Heuristics<br />Hand Out <br />Email me: firstname.lastname@example.org<br />FREE Online Coaching – skype: charretts<br />