Manual QA Without Tears

From CitconWiki
Revision as of 01:55, 12 September 2015 by Douglassquirrel (talk | contribs)
Jump to navigationJump to search

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 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

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