Se ha denunciado esta presentación.

Develop your inner tester

819 visualizaciones

Publicado el

How to make the most of the tools you've got.

Publicado en: Tecnología, Educación
  • Sé el primero en comentar

  • Sé el primero en recomendar esto

Develop your inner tester

  1. 1. Develop your inner tester<br />Name: Anne-Marie Charrett<br />E-mail: amcharrett@testingtimes.com.au<br />WEB: www.testingtimes.com.au<br />Phone: 0410560923<br />
  2. 2. 2<br />Tester Mindset<br /><ul><li> Analytical
  3. 3. Eye For Detail
  4. 4. Skeptical </li></li></ul><li>Can you work out the Rule ?<br />Identify a rule that applies to series of triples of numbers.<br />For example the following series of numbers match the rule<br />2,4,6<br />4,6,8<br />6,8,10<br />To find out what the rule is, construct other sets of three numbers to test your assumptions <br />I will tell you if they satisfy the rule or not<br />If you think you know the rule put your hand up.<br />Wason’s Discovery Rule <br />
  5. 5. Pattern<br />The Rule is: Sequence of incremental numbers<br />21% of subjects did not find the solution in 45 mins<br />
  6. 6. Challenge in Testing<br />5<br />Confirmation Bias <br />“Tendency for people to seek evidence to verify their hypothesis rather than refute them”<br />Test to Pass instead of Test to Fail<br />Discredit your code......<br />
  7. 7. Counter Balance <br />6<br />ConfirmationBias<br />Logical Reasoning<br />StrategicHypothesisThinking<br />
  8. 8. Testing similar to Scientific Thinking<br />Testing = Determine Hypothesis + Test Hypothesis + Evaluate Hypothesis<br />Get better at determining Hypothesis or <br />In other words<br />Generate new testing ideas<br />7<br /> Strategic Hypothesis Thinking<br />
  9. 9. 8<br /> GENERATE NEW TESTING IDEAS<br />
  10. 10. Different Models raise new questions<br /> == Different Hypothesis <br /> == Different Tests<br /> == Different Bugs<br />What model does your customer have? <br />9<br /> GENERATE NEW TESTING IDEAS <br />
  11. 11. Quality is Value to Some Person<br />Capability Can it perform the required functions?<br />Reliability Will it work well and resist failure in all required situations?<br />Usability How easy is it for a real user to use the product?<br />Performance How speedy and responsive is it?<br />Installability How easily can it be installed onto its target platform?<br />Compatibility How well does it work with external components &<br />configurations?<br />Supportability How economical will it be to provide support to users of the<br />product?<br />Testability How effectively can the product be tested?<br />Maintainability How economical will it be to build, fix or enhance the product?<br />Portability How economical will it be to port or reuse the technology<br />elsewhere?<br />Localizability How economical will it be to publish the product in another language?<br />James Bach Heuristic Risk-Based Testing http://www.satisfice.com/articles/hrbt.pdf<br />
  12. 12. Pen Exercise <br />You’re mission is to test a pen. <br />
  13. 13. Pen Exercise <br />
  14. 14. Pen Tests <br />Does it write? <br />Does it write on paper? Other mediums?<br />Does it leak? <br />Is it the right colour? <br />Does it write on an angle<br />Does it write upside down? <br />Does it not write when I want it to? <br />Does the clicker work? <br />Does it run out of ink too soon<br />Does it take too long to get the ink flowing? <br />Does this nib get sticky? <br />
  15. 15. Lots of Models<br />Code Coverage<br />Requirements Model<br />Multiple Environments, Multiple Models <br />Infinite number of tests <br />Could keep testing forever!!!<br />And...the clock’s a tickin’ <br />14<br /> Problem - Exhaustive Testing <br />
  16. 16. Risk is context dependent<br />Capacity for Risk differs <br />*Perfect Software G.Weinberg<br />15<br /> Risk <br />Likelihood of Failure* <br />Consequence of Failure<br />
  17. 17. One 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 />James Bach Heuristic Risk-Based Testing http://www.satisfice.com/articles/hrbt.pdf<br />
  18. 18. Review <br />Use different approaches – mix them up<br />Risk Based to Focus<br />Quality to Abstract Out<br />Creep & Leap Heuristic<br />Test To Fail <br />Be Sceptical <br />Be critical <br />Feedback <br />Peer Reviews<br />Pair up in Testing <br />Decision Tree <br />17<br />
  19. 19. Follow up <br />Perfect Software – G M Weinberg<br />James Bach – Strategic & Critical Thinking<br />Mind Map of Testing Resources <br />Email me: amcharrett@testingtimes.com.au<br />FREE Online Coaching – skype: charretts<br />
  20. 20. We would like to thank our sponsors and supporters for helping us bring you this event<br />
  21. 21. Please complete the feedback form in your delegate pack for a chance to win some great prizes.<br />Please remember to return the form before you enter the lock note, or leave the event. <br />

×