Setting up a test plan
Goal: Learn how to set up a test plan for an existing feature.
A test plan should list all possible tests that are needed to verify whether the application, or just a singular feature, is doing what it is expected to do. First of all, it should entail both the sunny scenarios, a.k.a. positive tests and often defined as user stories or use cases, and rainy scenarios, a.k.a. positive-negative tests, that is, tests that check that exceptions are handled. Next to that, it should clearly discriminate between tests that should be automated and those that do not have to. Regarding the first ones – those that need to be automated – it needs to be pointed out whether they check the business logic without accessing the UI, a.k.a. headless tests, and those that do need to verify UI specifics (UI tests). And finally, it has to prioritize tests, enabling the team to focus successfully on what needs to be tested beyond any doubt, and thus managing the risks...
