{"id":3867,"date":"2020-12-07T07:00:00","date_gmt":"2020-12-07T07:00:00","guid":{"rendered":"https:\/\/www.diogonunes.com\/blog\/?p=3867"},"modified":"2021-08-07T13:54:27","modified_gmt":"2021-08-07T12:54:27","slug":"test-strategy-saddest-ppiratee-mnemonic","status":"publish","type":"post","link":"https:\/\/www.diogonunes.com\/blog\/test-strategy-saddest-ppiratee-mnemonic\/","title":{"rendered":"Creating a test strategy using questions"},"content":{"rendered":"

\"\"<\/p>\n

He doesn’t have a test strategy \u261d\ufe0f<\/h3>\n
\n

\ud83c\udfc6 This post was featured<\/strong> in Software Testing Weekly, issue 49<\/a><\/p>\n<\/blockquote>\n

<\/p>\n

The test strategy is defined at the start of the project and it can be revisited and reviewed during the duration of that project. The strategy is usually driven by the testers, yet it should always include feedback from all team members.<\/p>\n

This strategy reveals the way tests will be designed and executed to foster quality. To do so, it needs to answer several questions<\/strong> like what parts of the product will be tested, what test techniques will be used, who will be involved, and how long it will take.<\/p>\n

The number of questions and the detail of the answers depends on your project’s requirements<\/a>, so you will have to choose between a formal and detailed document versus a simple and abridged alternative.<\/p>\n

Mnemonic SADDEST PPIRATEE<\/code><\/h3>\n

Erik Brickarp<\/a> suggests these first five questions before you start testing:<\/p>\n

\n
    \n
  1. What (product) are we testing?<\/li>\n
  2. What should be the main focus of our testing?<\/li>\n
  3. How much resources (time\/people) do we have?<\/li>\n
  4. How should we document our test strategy and results? To who?<\/li>\n
  5. Where can we get information about the product?<\/li>\n<\/ol>\n<\/blockquote>\n

    Those questions cover the most critical aspects of any strategy to test your product. You can use them to generate more questions and detail your strategy even more. As the number of questions increases, we should group them into categories.<\/p>\n

    I took Jared Quinert<\/a>‘s GRATEDD SCRIPTS<\/code><\/strong><\/a> mnemonic and further expanded it with more questions from Erik Brickarp<\/a> and Michael Bolton<\/a>.<\/p>\n

    The result was this mind map, and a new mnemonic<\/a> called SADDEST PPIRATEE<\/code><\/strong>:<\/p>\n

    \"\"<\/a><\/p>\n

    Download: overview mind map<\/a> \/ detailed mind map<\/a><\/p>\n

    Questions<\/h3>\n

    Scope<\/strong><\/p>\n