Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Testing for everyone agile yorkshire

359 views

Published on

Trying to explain the testers mindset and how it can help everyone develop better software

Published in: Technology, Education
  • Be the first to comment

  • Be the first to like this

Testing for everyone agile yorkshire

  1. 1. Testing for EveryoneTrying to answer the age old question What is the ‘Testing Mindset’?
  2. 2. Who Am I? Ady Stokes Nearly 2 decades in Software Testing, Quality Assurance and Risk management and still learning Currently manage QA and Risk at HML in Skipton for their Business Intelligence DivisionContacts:Twitter: @CricketRulzEmail work: adrian.stokes@hml.co.ukEmail home: adystokes@sky.com
  3. 3. Where I Work HML (part of the Skipton Group) Has over 42 billion in assets under management Offices in Skipton, Derry, GlasgowHighly regulated financial organisation Agile adoption since 2008
  4. 4. Everyone Tests!
  5. 5. Everyone Tests!It’s a fact of life everyone tests all the time!Think of your first coffee this morning. Youhad a sip to see if it wouldn’t burn your mouth!That’s testing!When you had your generic satellite system installed youpaused, rewound and fast forwarded live TV! That’s testing!!!Everyone tests! It’s nothing to be frightened of However, getting from undisciplined to structured,now that takes skills and knowledge!
  6. 6. Triangle Test Triangle Test Example By Glenford J Myers 1979 Scope – Software defines what type of triangle based on 3 possible outcomes, Equilateral (all sides same length) Isosceles (two sides of equal length) Scalene (all sides are unequal in length) List as many tests as you can in 10 minutes
  7. 7. Triangle Test Side One: Side Two: Output Grid Side Three: DRAW
  8. 8. Possible TestsIt is impossible to execute every possible test, but here are some things that I’dexpect you to have covered:• Valid entry for all three types of triangle• Permutations for isosceles with two equal sides? (3,3,4; 3,4,3; 4,3,3)• Incorrect or mathematically impossible triangles (1,2,3; 1,1,9999 ; 2, 5, 10)• Negative and zero inputs for at least one side (0, -1,)• Blanks (blank, 1, 1) for each field?• Spaces (space, 1, 1) for each field?• Boundaries and decimals (9999, 9999, 9999, 0.99 etc.)• Field size, what is the maximum entries or is it unlimited?• Special Characters ($%^&), Alpha’s, Alphanumeric?For each of the above do you know what the result should be? Can you think of any others?
  9. 9. It Is Not Fair Because…The triangle test is not really fair because…• You have no requirements so everything you did wasbased on an assumption about the program• I didn’t offer any help with what valid and invalid data was• I didn’t tell you how to start the program, what version itwas, if it was live or not.• There was no information on dependency or performanceBut hopefully it does make you think about testing andhow there are a great many things that can affect andinfluence your software?
  10. 10. So, What is the‘Testing Mindset’
  11. 11. So, What is the ‘Testing Mindset’It’s not…Developers Make, Testers Break(Sorry, but it was like that when we got there!)OrTesters Tell Tales To Teacher!(We want to tell YOU directly because we are all in it together) Its more like… What would happen given every possible practical scenario?
  12. 12. The Testing Mindset‘We can’t solve problems byusing the same kind of thinkingwe used when we created them’ Albert Einstein 12
  13. 13. Types of Tests!When it comes to software testing there are many methodstechniques and considerations which are useful to be aware of.• Boundary Value Analysis – at the edge of value entry• Equivalence Partitioning – grouping value entry• Unit testing – focus on individual components• Functional testing – focus on outputs• Load / Stress / Performance / Deployment and Rollback• Happy path / Sad path – does as it should, handles theunexpected• Usability – flow / understandable / navigation• Security – access / safe / secure
  14. 14. Top tips for testing Be curious Don’t make assumptions 14
  15. 15. The Testing of Requirements New World Old World • Singular• Singular • Complete• Complete • Consistent• Consistent • Correct• Correct • Current• Current • Unambiguous• Unambiguous • Prioritised• Prioritised • Traceable• Traceable • Testable
  16. 16. Questions?Motto: Don’t agitate, collaborate!
  17. 17. Who Am I Ady Stokes Contacts: Twitter: @CricketRulzEmail work: adrian.stokes@hml.co.uk Email home: adystokes@sky.com

×