Test Execution DEV environment - NextensArelB/SwaggerGenerationTool GitHub Wiki

Objective To validate whether the US is working as per the user requirements and acceptance criteria or not.

Who QA

What Execution of the the US under test

When When the coding of a US is completed by the developer and the functionality is merged to the DEV environment

How

Prepare test data (if applicable)
Perform the test
When testing, have Management Portal and the Console (F12) open to see if odd/strange things are occuring on the background
Register the test results:
- when test cases are described in the test task, register the results in the test task
- when test cases are described in a test case, run the test case and register the results
- when test cases are described in a separate document (excel or word), register the results in this document
- when testing new UI or complex functionality, make screen prints of the result
- when testing XBRL, compare with desktop (if applicable), check with VTS and save results
In case of deviations, determine if it is a bug (described in US) or a change (not described in US)
- Create bug or task on the board, for more info see Bugs
- Discuss or inform DEV on bug/taks found
Retest bugs:
- Describe what has been tested, including the regression cases
- Add screenprints, xbrl etc
When testing is complete:
- If possible: have PO/BA testing/accepting the functionality
- Demo functionality to rest of the team including PO/BA
- Check if DoD is complete
Determine which tests will be testautomated

Tools