Wednesday 2 January 2013

A Test Strategy

Test strategies are in one sense personal - all testers should have one, or be able to relate to one. Testers should be able to identify one, or identify components that make a test strategy important to them.

I am currently re-evaluating a test strategy and writing this down with appropriate influences, partly to document a work-in-progress and partly to aid reflection and feedback.

The strategy communication (which is different from the strategy) is simplified as a mind map below - with all the usual restrictions with mind maps, simplifications and presentations.

Test Strategy Representation



Question
Do you have a personalized or adapted test strategy?

Feedback
Feedback, comments and questions are very welcome.

Some References:
[] Satisfice: RST: CRUSSPIC STMPL
[] Kaner: General Test Design references
[] Tester's Headache: Mapping Information Value of Testing
[] Tester's Headache: Framing: Some Decision and Analysis Frames in Testing
[] Tester's Headache: The Documented Process Trap
[] Tester's Headache: The Linear Filter Trap
[] Tester's Headache: Silent Evidence in Testing
[] Tester's Headache: Challenges with Communicating Models II
[] Tester's Headache: Challenges with Communicating Models III

1 comment: