Difference between revisions of "Manual QA Without Tears"
(Created page with "new tester - use exploratory testing charters, file bugs then introduce checklist for developers to follow try moving checklist to JIRA tickets you can assign to multiple peop...") |
|||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
new tester - use exploratory testing charters, file bugs | new tester - use exploratory testing charters, file bugs | ||
| − | then introduce checklist for developers to follow | + | |
| + | then introduce checklist for developers to follow - Gawande http://www.amazon.co.uk/The-Checklist-Manifesto-Things-Right/dp/1846683149 | ||
| + | |||
try moving checklist to JIRA tickets you can assign to multiple people (checklists can be better if used by many people, less checklist fatigue) | try moving checklist to JIRA tickets you can assign to multiple people (checklists can be better if used by many people, less checklist fatigue) | ||
| + | |||
introduce a best before date for checklist items, remove and see if problem comes back | introduce a best before date for checklist items, remove and see if problem comes back | ||
| + | |||
serendipity for tests: vary text used, persona simulated, avoid boredom and find more problems | serendipity for tests: vary text used, persona simulated, avoid boredom and find more problems | ||
| − | Jerry Wineberg: Perfect Software and other Illusions - uncovering what the software was supposed to do in the first place | + | |
| + | Jerry Wineberg: Perfect Software and other Illusions - uncovering what the software was supposed to do in the first place http://www.amazon.co.uk/Perfect-Software-Other-Illusions-Testing/dp/0932633692 | ||
| + | |||
| + | Cheat Sheet by Hendrickson - test obsessed - http://testobsessed.com/2007/02/test-heuristics-cheat-sheet/ | ||
| + | |||
| + | You Ain't done yet list http://www.thebraidytester.com/downloads/YouAreNotDoneYet.pdf | ||
| + | |||
| + | Little Black Book on test design Edgren - http://www.thetesteye.com/papers/TheLittleBlackBookOnTestDesign.pdf | ||
| + | |||
| + | Tester does part-time tech support to get context and knowledge | ||
| + | |||
| + | If a tester takes on writing technical tests, a danger is that he or she may stop or lose the skill to do manual tests - ensure they do both | ||
| + | |||
| + | One team spends one hour every morning on learning new things | ||
| + | |||
| + | Tester pairing with dev can be silent but still trigger good testing behaviour - almost like a voodoo doll or cardboard cutout. To replicate more scalably, try setting time aside or make it fun - "I know she will complain about this, better add a test!" | ||
| + | |||
| + | If you need to switch between developer and testing modes, go for coffee in between - it's a big switch! | ||
| + | |||
| + | If bored when testing, that's a signal that something is wrong! Try some techniques to change it up: test with others (even random people found on twitter) or keep a log of your thoughts during the testing session | ||
| + | |||
| + | Dice game taught by Bolton and Bach: http://www.bettertesting.co.uk/content/?p=438 - helps you get into an exploratory testing mode | ||
Latest revision as of 02:14, 12 September 2015
new tester - use exploratory testing charters, file bugs
then introduce checklist for developers to follow - Gawande http://www.amazon.co.uk/The-Checklist-Manifesto-Things-Right/dp/1846683149
try moving checklist to JIRA tickets you can assign to multiple people (checklists can be better if used by many people, less checklist fatigue)
introduce a best before date for checklist items, remove and see if problem comes back
serendipity for tests: vary text used, persona simulated, avoid boredom and find more problems
Jerry Wineberg: Perfect Software and other Illusions - uncovering what the software was supposed to do in the first place http://www.amazon.co.uk/Perfect-Software-Other-Illusions-Testing/dp/0932633692
Cheat Sheet by Hendrickson - test obsessed - http://testobsessed.com/2007/02/test-heuristics-cheat-sheet/
You Ain't done yet list http://www.thebraidytester.com/downloads/YouAreNotDoneYet.pdf
Little Black Book on test design Edgren - http://www.thetesteye.com/papers/TheLittleBlackBookOnTestDesign.pdf
Tester does part-time tech support to get context and knowledge
If a tester takes on writing technical tests, a danger is that he or she may stop or lose the skill to do manual tests - ensure they do both
One team spends one hour every morning on learning new things
Tester pairing with dev can be silent but still trigger good testing behaviour - almost like a voodoo doll or cardboard cutout. To replicate more scalably, try setting time aside or make it fun - "I know she will complain about this, better add a test!"
If you need to switch between developer and testing modes, go for coffee in between - it's a big switch!
If bored when testing, that's a signal that something is wrong! Try some techniques to change it up: test with others (even random people found on twitter) or keep a log of your thoughts during the testing session
Dice game taught by Bolton and Bach: http://www.bettertesting.co.uk/content/?p=438 - helps you get into an exploratory testing mode
