Supervised Tests on TesterWork Platform: Step-by-Step Guide for Testers

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

This is how an invitation email looks like for Supervised Test, it is also indicated that its a Supervised Test by the "S" in the test code, in this example PWT-S-4.

By pressing Join the test you you are redirected to the Test Details tab where you are presented with the test details and where you can confirm your participation.

You can only confirm your participation to a test from your tester work profile, on the Test Cycles tab.

By pressing "Confirm and join" the test you automatically confirm your participation.

After joining a test you will see that the test is still ongoing and with a deadline of max 24h.

If the test is overdue, that means we are looking for more results.

If you select "Leave this test", a dropdown will appear with a few reasons for you to choose from.

1. "I am finished testing" - only press this after you finish your test case execution to be able to join another Supervised test if you were invited to it

2. "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.

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

The test chat can be accessed from the top right of the test that you have succesfully joined.

In the chat you can communicate with fellow testers, participating in the test and the test managers.

On this tab you can see all the information about this test.

Please read this tab carefully before starting the test as it describes the environment in which you need to test.

On this tab you will find the Tester specification document, a link to the bug tracker and also the build for you to use.

• 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

On this tab you will see the test cases, but first you will need to select the device you will be testing on.

When selecting your device, please check the tester spec if there are any specific devices or OS in scope.

After selecting your device, you will be able to see all the test cases assigned to you.

You can also change the device you are testing on while the test is ongoing.

You can open any test case you want from the Test Cases tab, there is no need to perform them in a specific order, although it is better to do them in order since they might relate to one another.

Depending on how the Test Managers set up the test, the test cases might have multiple steps that can have a status.

In this case you can change the status of the overall preconditions and overall steps.

The overall result needs to reflect the status of the steps and preconditions.

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 an attachment.

After submitting the result click submit and move to the next test case

Please note that test managers might set up the test so that the attachments are required for passed test cases.

Also note that after you submit your results you will no longer be able to edit the test case.

After submitting your result, this popup will ask you if you are certain of you result and move to the next test case

You may select the checkbox for this message to not be present on your next test case.

If you do not select the checkbox it will reappear for all the test cases moving forward.

After submitting your results you may move safely to the next test case

After failing a step in the test case, a comment box will appear.

Comment box

In this comment box you will need to write the reason for failing this test case.

Please write the explanation in a way that describes the issue encounter.

As mentioned before the overall results needs to reflect the results from the preconditions/steps.

In case one, or more, are failed, the overall result should also be failed.

After selecting fail, on the overall result, a comment box and text box for tracker issue will appear.

Just as before, in the comment box you will need to write the reason for failing this test case.

Tracker Issue ID field

In this field you will need to add the Issue ID (Bug ID) of the issue that is failing your test case.

Please note that as of now you can only add one issue ID.

The issue ID (Bug ID) can be found in the tracker

After submitting the bug ID and comment you may attach the evidence of the issue

Please note that after submitting your response you cannot edit it later unless a Test Manager requests an edit.

Please contact a Test Manager if you made a mistake while submitting your results.

Attachments

For failed and blocked test cases, attachment are required.

In case the Bug ID submitted in this test case is reported by you, you may add the same attachment as in the reported issue.

If the issue was not reported by you, you will need to attach a image/video where its visible that you encountered the same issue.

This is very similar to "Fail".

The only difference between Blocked and Fail is selecting the reason, by choosing one of the reasons, as shown in the image below.

After submitting the reason for blocking a step, the overall result should also be blocked.

Please note that if you fail the first step and block the rest, the overall result should be "Fail"

After blocking the overall result, your reason should be the same as blocking the step.

After which the process is very similar to Fail.

The details you leave in the comment box should be similar to this example.

After leaving the comment on which issue is blocking you, add the Bug ID that blocks you in the Tracker Issue ID field.

After you are sure of your response click submit.

Please note that after submitting your response you cannot edit it later unless a Test Manager requests an edit.

Please contact a Test Manager if you made a mistake while submitting your results.

After submitting the previous steps, add an attachment that shows that you are blocked from testing.

After Skipping a step, in the test case, a comment box will appear.

In this comment box you will have to write the reason for skipping the step.

The reason needs to be described clearly and the reason needs to be valid.

Since you are skipping a step it means you are unable to perform that step, thus the overall result needs to match.

Please note that "Skipped" test cases are not paid. So please skip only the test cases that are not possible to complete and for which you cannot report an issue.

Just like skipping a step, a comment box will appear, where you will need to state the reason for skipping the test case.

Skipped test cases do not require an attachment, however, if the test managers decide that the reason for the skip is not valid, you will receive an edit request to retest the test case.

When a Test Manager sends an Edit Request, you will receive an email notification that notifies you about what the test manager want you to edit.

After you read the request press "Edit test case" and it will redirect you to the test cases that needs editing.

If you have received a request you can edit everything in the test case.

When adding a Known Issue from the known issues list, you still need the bug ID, however the Bug ID is not the one at the top, its the one in the bug summary (in this example its not PWT-130-KI-2, the correct one is PWT-115-6)

Add the known issue Bug ID in the issue ID field, just the same as for normal Bug IDs.

After finishing your edit request and adding all your information, select "Submit" and the test managers will be able to see your edits.