Test Case execution guide (Spreadsheet)

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

If you prefer listening, you can check out this step-by-step video guide here.

Check the information from the Invitation Email and confirm your participation

1. Open the invitation email and check the information

Pay extra attention to the following elements:
- The Assigned device & environment
  - Each assignment has to be completed on the correct device or using the specific requirements mentioned in the invitation email.
    - This may include the device to test on, browser, language, connection type, mobile network, etc.
    - Important: If you don’t have that device, have updated the OS, or no longer meet the specific requirements, please let the Test Manager know by replying to the invitation email (using the “Reply all” function).
- Deadline
  - In order to be eligible for payment, you will have to finish the test cases before the deadline. If you have any problems or questions, please contact the Test Manager by replying to the invitation email. Please use the “Reply all” function or raise a ticket via Zendesk detailing the situation.

Example of an email invitation:

2. Confirm your participation by replying to the email using the “Reply all” function

Once you have verified that you are available, have access to the assigned device/environment, and can perform the assignment by the deadline outlined, you must Confirm your participation by replying to the email using the “Reply all” function.
- This step is very important - if we don’t receive your confirmation in a couple of hours, you will be replaced with another tester!
- Once you confirm your participation, you can start testing right away; you don’t have to wait for any other confirmation email.
If you cannot participate for any reason, please reply to the email notifying us that you are not available so we can assign the task to another user.

Check the testing instructions

1. Before you start testing, make sure to thoroughly read the Tester Specification document

The Tester Spec can be found in the invitation email, by accessing the Test Cycle page link
- This document contains all the details about the project: info about the app/website under test, the scope of the test, the link to the app, the bug tracker, and additional details

Please make sure to read the Tester Spec very carefully before you start to execute the test cases and familiarize yourself with the testing instructions, the scope of the test, and any requirements related to the application/website under test or bug reporting procedures!

2. Access your assigned Test Case document

Your assigned TC document can be found in the invitation email, by accessing the Test Case document link.
- Work only on the document provided. Do not create copies, and do not try to execute the test cases in any other way unless otherwise instructed.
Note: Some test cases have a different format than the TC document example on this page, the most common format for our test cases is the one exemplified on this page but sometimes you may receive a Test Case in a slightly different format (more details in the next section).

Example:

Legend:

Device + OS version & Browser cells (header): you will have to add the details of the device used for the test, usually assigned to you in advance and mentioned in the email
TC-ID: the TC-ID has to be included in the bug reports (in case you report bugs)
Section & Subsection & Test Case Name: no actions are needed. These columns are simply the names of the specific test-case flows and are used for identification purposes
Steps to reproduce: In the “Steps to reproduce” column, you will find the steps you have to perform
Expected Results: In the “Expected Result” column you will find the intended behavior that should be observed after following the aforementioned steps
Status: You will have to select a status based on the outcome observed. There are 4 options to choose from: Pass, Fail, Blocked, and Skip this test
Attachment URL (Required for Failed or Blocked): You will have to add an attachment ONLY for Failed or Blocked test cases
- Note: Attachments must be added ONLY as TesterWork URLs
  - 1. If you reported a bug related to a failed/blocked TC: Open the attachment from your bug report, copy the Public URL, and paste it into the TC document
  - 2. If you did not report a bug related to a failed/blocked TC (the bug was already reported by another tester), you will have to record the behavior on your device and upload the screenshot/video on your TesterWork profile page (Attachments section), copy the generated URL and paste it into the TC document

Actual result (Required for Failed or Blocked): You will have to mention the actual results ONLY for Failed or Blocked test cases
Related issues (BUG ID): You will have to add Bug ID/s ONLY for Failed or Blocked test cases
Remarks: You can add any remarks related to the test cases (if any) for additional context or clarification

How to Complete the Test Case Document

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)

Important Notes

Some test cases have a different format than the TC document example on this page. The following scenarios are not frequent; the most common format for our test cases is the one exemplified on this page but sometimes you may receive Test Cases in a different format:
- For some Test Cases, you don’t have to add any Attachments - if you don’t see an Attachment column in the TC doc it means that attachments are not required at all (not even for failed test cases)
- For some Test Cases, you will have to add video recordings at the end of each TC section - this will be mentioned in the TC doc and Tester Spec
- For some Test Cases, you will have to add Attachments for every flow, including Passed results - this will be mentioned in the Tester Spec
- Some Test Cases have to be executed directly on our platform - you will receive all the info in the Invitation email
  - Before starting the Test Case execution, thoroughly review the Tester Spec and Email Invitation to check for additional information regarding the Test Case execution (if any).

Test Case Status instructions

There are 4 statuses: Pass, Fail, Blocked, and Skip this test, 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 Steps to Reproduce column 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 instructed otherwise in the Tester Spec document)
- Example of Pass test cases:

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)
- Follow these steps in the case of a failed Test Case:
  - Status: Select the Fail status
  - Related Issues: Check the bug tracker to see if a bug was already reported by another tester (in the ongoing test cycle or known issues list found in the bug tracker or Tester Spec):
    - 1. If the bug can be found in the tracker copy/paste the BUG ID into the Related Issues cell
    - 2. If you don’t find the bug in the bug tracker, please submit a bug report and copy/paste the BUG ID into the TC document
  - Attachment URL: Add the attachment for the failed test case (Attachments must be added ONLY as TesterWork URLs):
    - 1. If you reported a bug related to a failed/blocked TC: Open the attachment from your bug report, copy the Public URL, and paste it into the TC document
    - 2. If you did not report a bug related to a failed/blocked TC (the bug was already reported by another tester), you will have to record the behavior on your device and upload the screenshot/video on your TesterWork profile page (Attachments section), copy the generated URL and paste it into the TC document
  - Actual result: Mention the actual result encountered after following the Steps to Reproduce

Important notes for Failed test cases

DO NOT add more than 1 attachment link in the ‘Attachment URL’ cell
If more than one Bug ID is reported for one TC make sure you separate the Bug IDs from one another by using a comma and leaving a space (e.g.: PWT-20-1, PWT-20-2, PWT-20-3)

Example of Failed test cases:

Blocked 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
- 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, and BUG ID
Follow these steps in the case of a blocked Test Case:
- Status: Select the Blocked status
- Related Issues: add the BUG ID into the Related Issues cell
- Attachment URL: Add the attachment for the failed test case (Attachments must be added ONLY as TesterWork URLs):
  - 1. If you reported a bug related to a failed/blocked TC: Open the attachment from your bug report, copy the Public URL, and paste it into the TC document
  - 2. If you did not report a bug related to a failed/blocked TC (the bug was already reported by another tester), you will have to record the behavior on your device and upload the screenshot/video on your TesterWork profile page (Attachments section), copy the generated URL and paste it into the TC document
- Actual result: Mention the actual result encountered after following the Steps to Reproduce

Important notes for Blocked test cases

DO NOT add more than 1 attachment link in the ‘Attachment URL’ cell
If more than one Bug ID is reported for one TC make sure you separate the Bug IDs from one another by using a comma and leaving a space (e.g.: PWT-20-1, PWT-20-2, PWT-20-3)

Example for Blocked test case:

Skip this test 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 this test and add the reason for skipping it into the Remarks cell.
- 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 this test based on the received instructions.

Example of Skip this test case:

Do’s and Don'ts

Do’s

Make sure to always confirm or decline your participation in the test case by replying to the invitation using the Reply All option
Test only on the assigned device/environment mentioned in the Test Case Invitation email
Before you start testing, make sure to thoroughly read the 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 test cases only on the Test Case document shared with you in the Invitation email.
You are allowed to edit ONLY the following fields:
- The TOP rows where you might be requested to add some information about the device, OS, browser version, etc. used in the current test
- The columns:
  - Status
  - Attachment URL (Required for Failed or Blocked)
  - Actual result (Required for Failed or Blocked)
  - Related issues (BUG ID)
  - Remarks
Complete the task before the deadline
Complete the test cases following the instructions from this page + Tester Spec instructions
If you receive a 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 replying to the invitation email (Reply All)

Don't's

Don’t test on other devices than the one assigned to you in the Email Invitation (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. One step at a time.
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.
If Attachments (videos/screenshots) are needed, do not upload G-Drive links or any other cloud service - all Attachments have to be uploaded as TesterWork URLs
Do NOT edit any of the following columns:
- TC ID
- Section
- Subsection
- Test Case Name
- Preconditions
- Steps to Reproduce
- Expected Results