Important Note: The images contained on this page are examples, this may vary depending on the assignment!
Joining a Supervised Test
When you’re invited to take part in a Supervised Test, there are two ways you can join:
1. Email Invitation
Your email invite for a Supervised Test will look the same as for any other test but here’s the giveaway:
The Test ID will always have an “S” in the cycle name.
You’ll also see the deadline for participation.
Simply click the “I’m ready to test” button in your email.
This will take you straight to the Test Details page on your Tester Work profile (make sure you’re logged in!).
Here, you’ll see all the details about the test and can confirm your participation.
2. From Your Tester Work Profile
You can also confirm your spot directly from your Tester Work account:
Go to the Test Details page for the Supervised Test.
Hit “Confirm and join” to lock in your participation.
✅ Remember: You’re only officially part of the Supervised Test once you press “Confirm and join” on your profile. Clicking the button in your email just gets you to the right place!
Examples:
Email Invitation
TesterWork
Test is currently full
If, after pressing the button ‘Confirm and Join’, you are prompted with the following message, please try again a bit later, and inform any Test Manager via email, Slack, or Zendesk Support.
Test Details & Scope
Test Details Tab
The Test Details tab is your go-to spot for all the key information about a test. Here’s what you’ll find:
Type of test – Shows how many Test Cases are included in this test.
Test objective – Explains the main goal of the test so you know exactly what you’re looking for.
Languages to test in – Tells you which language(s) to use when testing the client’s app. If no language is specified, English is the default.
Environment – Lists the platform and OS versions in scope. Make sure to choose a device that matches these requirements.
-
Deadline – Shows when the test is due.
Sometimes tests can go beyond the initial deadline and if that happens, Test Managers will update you.
Need an extension or have deadline-related questions? Reach out to the Test Manager.
Payment Details – States the maximum amount you can earn once you complete all assigned Test Cases.
Test participation guidelines – Provides general instructions that apply to any test you join.
This way, you can review the details at a glance and ensure you’re fully prepared before confirming your participation.
Example:
Scope Tab
The Scope tab is your toolkit for the test. Everything you need to get started is here. You’ll find:
Tester specification – Your must-read document before starting. It contains important instructions and requirements for the test.
Application under test – A direct link to download or access the app you’ll be testing.
Bug tracker – The place to report any issues you discover during the test. This link takes you straight to the project’s tracker.
Credentials / Access instructions – If the test requires specific login details or setup steps, you’ll find them here (and also in the Tester Specification document).
Application URLs & resources – Any extra links or resources you might need will be listed here, and again in the Tester Specification document for easy reference.
This way, testers know the Scope tab isn’t just “extra info”, it’s the command center for everything they’ll need during the cycle.
Example:
Test cases – Device selection
Before you can jump into the test cases, you’ll need to pick the device you’ll be using for this test.
Here’s how to get it right:
Head over to the Test Details tab and check the device requirements listed there.
Double-check the Tester Specifications document for any extra details.
Once you’re sure your device matches the requirements, go to the Test Cases tab and select it.
✅ Choosing the correct device is important. It ensures your results are valid and that you’re testing in the exact environment the client needs.
Example:
In case you don’t have any device to select from, as it can be seen in the screenshot below, make sure you have the in-scope device listed in your Devices section. You have to press the Add device button and add the specifics of your device: Device Name + Operating System
Example:
After you select the device and press Start testing, in case you added an incorrect device or browser, you can change it through the Change device or browser link.
Example:
General info
Before diving into execution, take a moment to set yourself up for success:
-
Read the Test Case instructions carefully
Check both the Steps to Reproduce and the Expected Results so you know exactly what to do and what should happen.
-
Follow the steps one by one
Perform each action listed in the Steps to Reproduce and see if the Expected Results actually happen.
-
Set the right status
After checking the Expected Results, choose the appropriate Status for each one.
Some Test Cases have multiple steps or multiple Expected Results, and each can have its own status.
-
Mark the overall Test Case status last
Always update the statuses for individual Steps & Expected Results before setting the status for the whole Test Case.
💡 This approach helps keep your testing accurate, organized, and easy for the Test Managers to review.
Add the relevant information where needed, especially for failed and blocked Test Cases (Bug ID, Attachments, Actual results, Remarks)
You can add only one issue/bug ID per failed/blocked Test Case, so make sure to add the most relevant issue that is failing/blocking the respective Test Case
After submitting a result, you will be able to edit the Test Case if needed. Click on that specific Test Case and then on the Edit Case Results button. You won’t be able to delete an already added attachment, but don’t worry, the moderator or a Test Manager will do it for you.
Example:
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:
Test Case Statuses – How to Mark Your Results
When you finish running a Test Case, you’ll need to set its overall status. Here’s what each option means and when to use it:
✅ Pass
Use this when:
You followed all the Steps to Reproduce exactly as written.
All the Expected Results matched perfectly — no bugs found.
💡 Attachments for Passed cases are only required if the client specifically asks for them (this will be mentioned in the requirements).
❌ Fail
Use this when:
You followed the steps exactly, but the Expected Results didn’t match what actually happened.
What to do for a Fail:
Status: Select Fail.
Tracker Issue ID: Enter the bug ID from the Bug Tracker (e.g.,
PWT-188-1). Report the bug first if it isn’t already logged.Actual Result: Clearly explain why the Test Case failed.
Attachment URL: Provide evidence (screenshots/video) showing all steps in the Test Case and the problem you found.
📌 If even one step fails, the whole Test Case must be marked as Fail.
🚫 I’m Blocked
Use this when:
You can’t complete the Test Case because another bug or issue is stopping you from proceeding.
Example:
If TC-05 tells you to go to Settings but the app crashes, and TC-06 requires you to access a sub-section of Settings, then TC-06 is Blocked because of the bug in TC-05.
What to do for Blocked:
Status: Select I’m Blocked.
Reason & Actual Result: Explain exactly why you can’t continue, referencing the related bug.
Tracker Issue ID: Provide the bug ID that caused the block.
Attachment URL: Show evidence of the blocking issue.
⏭ Skip
Use this when:
You can’t complete a Test Case due to specific requirements or limitations unrelated to bugs.
Example:
A section of the app is unavailable in your country (as noted in the Tester Specifications). You can mark those Test Cases as Skip.
Always explain the reason in the comment box.
📎 Extra Info
Sometimes a Test Case will request extra proof such as additional screenshots, videos, or text notes. If so, you’ll see these instructions right under the Overall Result section of the Test Case.
Example:
This additional info will be requested as a free text field and/or as a message requesting an attachment.
Feedback
You can also leave feedback for each Test Case before submitting the result
Edit Request
In case a Test Case is not completed accordingly or the Test Manager or the assigned moderator 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:
Asking questions
To ask questions regarding the test, you will need to open the Chat where you can speak with Test Managers and other testers.
You will find 3 chats there:
Public chat - where all the testers from the test can write or see messages; Also, the Moderator and the test managers see those messages and can respond to them
Community Test Manager - where only the tester and the moderator can write messages - the Test Managers can see those messages
Tester Work - where only the tester and the Test Managers can write messages; The moderator does not have access to this chat
When you receive a message, you will see a red dot on the Chat button
Then, by opening the chat, you can see in which of the 3 chats the message was received
If the moderator or the Test Manager also tagged you in the message, you will receive an email stating that you’ve been mentioned in a specific test, and you can tap on View Message to read it.
Keep in mind:
Always talk respectfully, do not swear or say rude words
Only ask relevant questions related to the test you are taking part in
Do not write in the Public chat any personal information, and do not send attachments with personal information, as this info can be seen by other testers before a Test Manager can delete it
Finishing or Leaving a test
Finishing the test
After you’ve completed all the assigned Test Cases, they will be marked as Under Moderation and can be modified if necessary
Then, after you’ve resolved all the edit requests, the moderator will approve all the Test Cases, and you won’t be able to make any additional changes, and they will look like this on your side
Leaving a Test
We understand that sometimes life happens, and you may not be able to participate in a test you’ve joined. If that’s the case, you can easily withdraw using the "Leave this test" button on your TesterWork dashboard.
When you click it, you’ll be asked to select a reason:
🚫 I am unable to test
Choose this if something prevents you from participating — for example:
You no longer have the required device
You’re already busy with too many other tests
You can’t meet the deadline
🕒 Personal matter
Choose this if a personal emergency or unexpected situation means you can’t continue testing.
📌 Tip: If you know early on that you can’t take part, leave the test as soon as possible. This helps us offer your spot to another tester and keeps your profile in good standing for future opportunities.
Do’s and Don'ts
Do’s
Make sure to always confirm or decline your participation in the Test Case by joining from the invitation email or the TesterWork profile
Test only on the device/environment mentioned in the Test Details tab and the Tester Specifications document
Before you start testing, make sure to read the Test Details and Tester Specifications document thoroughly
Before beginning the execution, read the Test Case instructions (Steps to Reproduce & Expected Results) to gain a basic understanding of each 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 Test Case document when needed (BUG IDs, Attachments, Actual Results, Remarks)
Complete the task before the deadline - or ask any Test Manager in the Chat for an extension if necessary
Complete the Test Cases following the instructions from this page + Tester Specifications instructions
If you receive an edit request from a Test Manager for your execution, please make sure to answer that request as soon as possible - executions with edit requests still open at the end of the test will disqualify you from receiving the test’s payment
If you have any questions or if you have any type of trouble regarding the Test Case execution, reach out to the Test Managers by accessing the Chat section
Don’ts
Do not reply to the invitation email for a Supervised Test
Don’t test on any devices other than the ones mentioned in the Test Details and Tester Specifications 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, but still complete it within the deadline
If Attachments (videos/screenshots) are needed, make sure to record only the Test Case flows, DO NOT record the Tester Specifications document, Test Case document, bug tracker, email invitation, personal information, etc.
Comments
0 comments
Article is closed for comments.