Basic guidelines

• Keep in mind that it is not possible to test everything, our testing is always based on our allocation

• Our testing should be always focussed on manual testing of the new functionalities described in User stories

• When the project is close to UAT phase, it is wise to add some regression tests to cover also previously developed functionalities

• If you don’t have enough allocation for your testing, ask PM for prioritization - even with smaller allocation then we would like to have, we can be very beneficial for the project, but it is important to be clear about the most important User stories we should be focussed on

Testing based on User stories

• Key information for testing should be always in Description part of the User story

• If you need more information, try “Technical description“ part of the User story

• Third option for getting more information for testing is to ask SA or CE

• Note: QA Analyst should not contact customer without permission of PM or SA, please respect it and if you need additional information, contact our team members first

Reporting test results

• Mark the Test as In progress immediately after you start your testing

• If you find a bug during testing, usually one of the following options are good:

  • Write to CE on Teams and if he can fix the issue immediately, wait for the fix and continue in testing

  • Describe the issue in Comments section and change the status of the User story to Rejected and assign the User story to CE for fix

• After successful test move the Test to Passed and move the User story to Accepted dev state and assign it to SA (SA is usually assigning the User story to Customer)