Test Analysis and Test Preparation - NextensArelB/SwaggerGenerationTool GitHub Wiki

##Objective Describe test approach for Feature

##Who

• Quality engineers (QA)

##What When the design is final and the User Stories are created, QA starts up the test analysis. This is based on the outcome of the PRA: what needs to be tested with what coverage, which attributes are applicable (functional and non-functional), which tests are manual and/or automated

Steps to follow:

• Based on the outcome of the Product Risk Analysis, test approach is determined, where a higher risk will lead to higher test coverage and higher level of test automation:
• Determine which attricbutes are applicable (e.g. Functionality, User Friendliness, Performance, Security)
• Create test cases to cover the attributes
• Indicate which test cases will be for manual tests and which for automated tests
• Create test tasks

Start thinking of test scenarios and put them in test cases in DevOps. What functionalities should be tested? What will you click as a user? What is expected?

Use the Gherkin-format:

1. Given (followed by a state)
2. When (followed by an action)
3. Then (followed by the expected response)

Example: Given I am in Naslag When I click on Nieuws in the secondary navigation bar Then I see Nieuws Landing Page

Make sure your test cases cover all the acceptance criteria of the Feature

##Putting your Test cases in DevOps

1. Go to Azure DevOps, where you are now.
2. In the activity bar, go to Boards>Boards.
3. Hover over the Feature for which you are creating test cases. Tip: try to get think of how the Feature will be divided into User Stories. That way User Stories can easily be tested once finished by a developer. It is also possible to wait with writing these test cases until user stories have been added to the Feature, as long as it doesn't block the Feature development.
4. Click on the three dots in the top right corner and click to "Add test" or if there already is a test like in the example below (this is a User Story, not a Feature), click that flask and an "add test"-button will appear.
5. After clicking one of those two buttons, you can now type the name of your test in the empty field. Tip: make sure that by the name of the test, everyone can understand what is being tested.
6. After you've typed the name, press ENTER and click on your test, this will open a new window where you can enter the steps in Gherkin-format.
7. Finally, don't forget to change the state of your test from 'Design' to 'Ready'.
8. Have your test cases reviewed by a fellow Tester. They may have other insights or notice something that you may have forgotten.

Note: when functionality is too complicated to put it in DevOps, they can also be created in excel and the link to the file can be added in the test task