Articles in this section

Test Case execution guide (Supervised Tests)

Avatar
Tester Work
  • Updated
Follow

Important Note: The images contained on this page are examples, this may vary depending on the assignment!

Step-by-Step Guide

Please check the following link for a complete overview of Supervised Tests, where every step is described in more detail:

Below you can find a summary of the instructions detailed in the guide.

Joining a Supervised Test

1. Test Invitation

  • There are 2 ways to join a Supervised Test that you have been invited to:

    • Email Invitation

      • The email invitation, for Supervised Test, looks the same for all the tests and the only important information displayed in the test is the test name, which will always contain a “S” in the cycle name, and the deadline.

      • By pressing the button to join from the email invitation you are redirected to the Test Details tab where you are presented with the test details and where you can confirm your participation.

    • TesterWork Confirmation

      • Participation can only be confirmed from your TesterWork profile by pressing the “Confirm and join” button.

Examples:

Email Invitation1.png

TesterWork2.png

Test Details and Resources

1. Test Details tab

  • The Test Details tab shows important details for this test:

    • Type of test - Will tell you how many test cases there are in this test

    • Objective - Will tell you the main objective of the test

    • Environment - Will tell you the platform and OS that are in scope and you need to select your device based on the details presented here

    • Deadline - Will tell you the deadline for this test, however some tests might take longer than the the deadline presented, in which case the Test Managers will notify you of the change

    • Payment details - will tell you the amount of payment you will be given once you complete the test cases

Example:3.png

2. Resources tab

  • The Resources tab contains several useful links:

    • Tester Specification - Please read the document carefully before starting the test

    • Bug Tracker - Will redirect you to the tracker for the project where you can report the issues that are found in the application

    • Application URL - Link to download/access the application that is under test

Example:

4.pngTest Cases

1. Device Selection

  • Before you can actually access the test cases, on the Test Cases tab, you will have to select your device

    • Please read the device information stated in the Test Details tab and the Tester Specification document before selecting your device.

2. General Info

  • Before beginning the execution, read the test case instructions (Steps to Reproduce & Expected Results) to gain a basic understanding of each individual test case

  • Start following the Steps to Reproduce instructions and check if the Expected Results are met

  • Select a Status based on the Expected Results and add the relevant information where needed, especially for failed and blocked test cases (Bug ID, Attachments, Actual results, Remarks)

  • Some test cases have multiple Steps/Expected Results that can be marked with a status

  • Always select a Status for the Steps & Expected Results before selecting a Status for the overall test case

  • You can add only one issue per failed/blocked test cases, so make sure to add the most relevant issue that is failing/blocking the respective test case

  • After submitting a result you will not be able to edit the test case until a Test Manager request an edit for that Test Case

3. Test Case Status instructions

There are 4 statuses: Pass, Fail, I’m Blocked and Skip, you will have to select the correct status for every test case based on the Expected Results:

Pass status

  • If you have followed all the instructions from the Step part and found all the results listed in the Expected Results it means that there are no issues with that test case and it is passed.

    • You don’t have to add Attachment URLs for Passed test cases (unless the test is set up so you cannot move to the next test case without providing attachments)

Fail status

  • If you have followed all the instructions from the Steps to Reproduce column and found different results than the ones listed in the Expected Results it means that the test case is Failed

    • Important:

      • All Failed test cases must have an Attachment, Actual result, and Related issue/s (BUG ID), otherwise you will not be able to submit the result

      • If one of the steps is marked as Fail, the overall status should also be marked as Fail

    • Follow these steps in the case of a failed Test Case:

      • Status: Select the Fail status

      • Tracker Issue ID: Field cannot be empty and the ID needs to look like: ex. PWT-130-1

      • Actual Result: Needs to explain the reason, in a clear manner, why the test case has failed

      • Attachment URL: Needs to contain all the steps in the test case with the issue encountered

I’m Blocked status

  • If you can not execute the instructions from the Steps to reproduce column due to an issue reported for a previous TC entry that makes it impossible to access a section, mark the test Case as Blocked

    • Example: TC-05 instructs you to access the Settings section and while executing the test case, the app crashes. The next test case (TC-06) instructs you to reach a subsection of the Settings section. The second Test Case will be Blocked based on the bug submitted for the first test case

    • Important:

      • All Blocked test cases must have an Attachment, Actual result, Reason and Related issue/s (BUG ID), otherwise you will not be able to submit the result

    • Follow these steps in the case of a blocked Test Case:

      • Status: Select the I’m Blocked status

      • Reason: Needs to coincide with the Actual Result and the Issue reported

      • Tracker Issue ID: Field cannot be empty and the ID needs to look like: ex. PWT-130-1

      • Actual Result: Needs to explain the reason, in a clear manner, why the test case was blocked

      • Attachment URL: Needs to contain all the steps in the test case with the issue encountered

Skip status

  • If there is a special requirement that you can not complete due to reasons that are independent of you, mark the Test Case as Skip and add the reason for skipping it into the comment box.

    • Example: You run a general set of Test Cases but you know from the Tester Spec that a section is not available in your Country. You can mark that test case as Skip.

Additional Info

  • Some Test Cases may require additional info, which is displayed below the Overall Result of the respective test case.

  • This addition info will be request as a free text field and/or as a message requesting an attachment.

Edit Request

In case a Test Case is not completed accordingly or the Test Manager requests an edit or a retest, you will receive an Edit Request email with information regarding which test case and the message from the Test Manager with the reason for the request.

Email Example:

5.pngAsking questions

To ask questions regarding the test you will need to open the Chat where you can speak with Test Managers and other Testers.

Keep in mind:

  • Always talk respectfully, do not swear or say rude words

  • Only ask relevant question related to the test you are taking part in

Finishing or Leaving a test

Finishing the test

  • After you’ve completed all the test cases assigned, you can leave the test successfully and join another one by selecting Leave this test → I am finished testing

Leaving the test

  • If by any reason you cannot take part in this test please select one of the following reasons from Leave this test

    • "I am unable to test" - this reason will drop you from the test, reasons can vary from: no longer having the assigned device, taking part in too many tests etc.

    • "Personal matter" - select this when you have a personal emergency and cannot test

Do’s and Don'ts

:check_mark: Do’s

  • Make sure to always confirm or decline your participation in the test case by joining from the invitation email or from the tester work profile

  • Test only on the device/environment mentioned in the Test Details tab and the Tester Specification document

  • Before you start testing, make sure to thoroughly read the Test Details and Tester Specification document

  • Before beginning the execution, read the test case instructions (Steps to Reproduce & Expected Results) to gain a basic understanding of each individual test case

  • Always check the Known Issues List and the bugs reported in the current tracker before submitting a bug

  • Add all the required details in the TC document when needed (BUG IDs, Attachments, Actual Results, Remarks)

  • Complete the task before the deadline

  • Complete the test cases following the instructions from this page + Tester Spec instructions

  • If you receive a edit request from a Test Manager for your execution please make sure to answer that request

  • If you have any questions or if you have any kind of trouble in regards to the test case execution, reach out to the Test Managers by accessing the Chat

:x: Don’ts

  • Do not reply to the invitation email for a Supervised Test

  • Don’t test on other devices than the ones mentioned in the Test Details and Tester Specification document (unless instructed otherwise by a Test Manager)

  • If you confirmed your participation, please do not abandon the execution as this may result in you receiving fewer invites in the future

  • Take your time with the test scenarios and do not rush through them

  • If Attachments (videos/screenshots) are needed, make sure to record only the test case flows, DO NOT record the Tester Spec, TC document, bug tracker, email invitation, personal information, etc.

Related articles

Comments

0 comments

Article is closed for comments.