Test Case

Test Cycle Terms A Test Case is a set of predefined steps that must be followed and
executed by a tester in order to test specific features and
Client or Customer functionalities of a product, such as exercising a particular program
A company that has engaged Applause and the uTest Community to path or verifying compliance with a specific requirement. It is
test their product. primarily used in two stages:

 Within the development to ensure a feature has been built as

designed
Test Cycle  On a regular basis as part of the general QA processes to ensure the
One specific test of a company's product. Each individual test cycle wanted test coverage
includes numerous testers and can vary greatly from other test
cycles depending on the cycle setting, type, etc. In the test cycle, You will learn more in Slots, Test Cases, and Reviews course.
testers must carefully follow the instructions in the test cycle's
overview to find bugs on the in scope product, execute test cases,
submit reviews, or conduct usability studies, if available. Tester
Note: That, not all test cycles include slots, test cases, reviews or A member of the uTest community who participates in test cycles by
usability surveys. This differs from cycle to cycle. finding bugs, providing feedback, or performing test cases.

Bug Report Test Team Lead (TTL)

Is a written summary of a specific error or defect (bug) in a product's The Test Team Lead (TTL) is the primary point of contact for testers.
features or functionality. A bug report should contain all the required The TTL helps testers within test cycles and reviews all submitted
information to understand, reproduce, and fix the bug. bug reports and test cases.
To submit a bug report, a tester just needs to click on the
blue Report Issue button from the test cycle header. A bug report
form contains several fields which need to be filled by the tester Test Engineer (TE)
properly and by following the issue reporting instructions of the cycle. The Test Engineer (TE) builds the test cycle, assembles the testing
You will learn more in Bug Reports course. team and is responsible for the overall execution of the test cycle.

Testing Service Manager (TSM)

The Test Architect (TA) title has been replaced by TSM. The Testing Once the test cycle testing phase ends the test cycle gets locked. No more
Service Manager works directly with the client. They manage a team bugs reports or test cases can be submitted. Our team and customer will
of TTLs and TEs to identify and provide appropriate solutions for the continue reviewing all the reported bugs and submitted test cases.
client’s testing, feedback or research needs.
In next courses we will discuss every step in detail.

Community Manager (CM) Test Cycle Statuses

Community Managers are members of the Community Management A uTest test cycle has 4 statuses. Let's learn about them.
Team (CM). The Community Management Team's goal is to help our Pending Activation
global community to learn how to be excellent testers, to get
opportunities for paid projects, and to connect with fellow testers  The cycle is scheduled to be activated
across the community and the globe. Meet the uTest Community  The tester can read the overview and understand the instructions
Management team from here.  The tester can claim a slot
 The tester cannot test the product, report any bugs, execute test cases or submit
reviews
Test Cycle Process at uTest Active

tLet’s get a general overview of how test cycles work inside uTest.  The cycle is active and the tester can test the product
 The tester can report/edit bugs, execute test cases and submit reviews
Invitation
Locked
Once a new test cycle is ready uTest sends out invitations to matching
testers, we already discussed how uTest selects testers for a test cycle.  The tester cannot report anymore bugs or submit test cases
Testers need to read the overview carefully then accept the test cycle  The tester can edit bug reports, test cases, or communicate in the chats
invitation.  Submitted work will be reviewed

Testing & Reporting Closed

Testers understand the requirements and start testing the process. A test  The test cycle is completed and all submitted work is reviewed
cycle usually runs for 2-3 days and in this phase, testers can submit bugs  Nothing can be done within the test cycle at this stage
and complete test cases.  Testers can only review the test cycle details and review their submitted work

End of the test cycle

 Bonus Instructions: Information about bonus requirements and directions on
Test Cycle information

procuring a bonus.

Note: Some sections may not be displayed, depending on the cycle setting,
Once you accept a test cycle, you can access the information related to it. uTest type, etc.
organizes all information related to a test cycle into several tabs. Let’s discuss
each tab. Slots
This tab contains all the available slots for the cycle. Slots guarantee you a
Overview
position inside the testing team. You can claim or unclaim slots from here.
We already discussed the Overview tab. It contains all information Always remember to read the slot description and to ensure that you have
regarding the test cycle. The Overview tab consists of the following met all of the requirements in the slot before claiming it.
sections:
We will discuss more about slots in next courses.
 Description: A short description of the product being tested.
 In Scope: Information about what devices and environments are in scope and Announcements
should be used, what should be tested, what customer is looking for and any Announcements are important messages sent to both accepted and/or
additional information which may be important. invited testers by TTL, TE or TSM for the cycle. It is important that testers
 Out Of Scope: Information about what should not be tested, what customer is understand the announcements and follow what it says. Ignoring
not looking for. announcements can result in rejected work.
 Setup Instructions: Information related to how to setup or access the testing
product. Some announcements need to be acknowledged otherwise you cannot
 Issue Reporting Instructions: Information related to issue report formatting, like continue testing, click on the Acknowledge button present on the
title format, what attachments are required. announcement to acknowledge it.
 Test Case Instructions: Information related to test cases, like turnaround time,
claiming instructions. Builds
 Special Instructions: Any extra instructions which is very important and testers
should follow. Contains version and new changes information about the product build
 Attachments: Contains any attachments related to the cycle, like product build, which is being tested.
screenshots, videos.
 Team Contact Information: Information related TTL, TE and TA for the cycle and Issues
how to contact them, also hours of availability.
 Payouts: Information about payout rates for Test Cases, Bugs, Tester Review. Issues tab is a list of bugs which are reported in the cycle. Testers can
 Specified Environment: Information about the environments you can use in the search, sort and filter the issues from this page. Some cycles may contain
particular cycle. known issues inside the issues tab, known issues will have a blue bookmark
 Special Requirements: Information about the special requirements for the test icon.
cycle. You must fulfil the requirements to participate in the cycle.
Test Cases
Test cases tab contains available and claimed test cases. Testers can open an that.
individual test case and complete that from this page. Testers can search,
sort and filter the test cases from here as well.
Reporting
Reviews
Reporting is when testers submit information about an app, website or
A review form for you to submit, depending on the test cycle this may or product in a test cycle. There are four different methods of submitting
may not be present. reports:
 Bug Reports
My Earnings  Test Cases
 App Reviews
Shows information about your earnings in that test cycle.
 Usability Studies

Tester Scorecard Submitting a Bug Report

Contains a scorecard which shows the testers participating in the cycle order
Follow these steps when writing a bug report in a test cycle:
by their rank in the cycle. The rank is calculated by the total points a tester
receives for his/her work.
1. Recreate the bug for verification
2. Verify that the bug is unique by checking reported issues
Cycle Feedback 3. Refer to the overview for specific reporting instructions
From here testers can provide feedback on the test cycle. The survey has 5 4. Prepare required attachments (screenshots, browser logs, Charles Proxy
log, etc.)
rating-based questions, and an open comment field to add additional
5. Click on the Report Issue icon within the test cycle header
information if needed. This feature gives testers the ability to share their
6. Fill out the bug report form, review your work and submit
views and gives the TSMs valuable insight into how test cycles are being
set up and run. This survey has also been added to the uTest Mobile App.
Note: Only TSMs have access to the reports. Submitting a Test Case
Follow these steps when submitting a test case in a test cycle:

Reporting 1. Carry out all the test case steps and upload the required attachments as
described
Testing 2. Click Pass if you have not encountered a bug while carrying out a step
3. Click Fail if you have encountered a bug while carrying out a step
As we already know testing is the process of evaluating a product to find o If the bug has already been reported by another tester, put its id in the
defects. In the previous track we already discussed testing. So once you Actual Result field and click Fail
start testing you may find a bug which you want to report or maybe you o If the bug has not been reported by other testers, click Fail & Report
want to execute a claimed test case, in this course we will explain how to do Issue, then fill the issue report form and submit the issue
4. Review the steps and make sure everything is correct
 5. Click Submit Results, specify the spent time and click Finish The Test Cycle Chat is the main communication method for testers to ask
6. Read messages from the TTL if your test case was messaged and respond questions and get answers related to a uTest project. You can access the
quickly Test Cycle Chat by clicking on the chat icon in the [Link] header or by
opening [Link]
Submitting a Review
Follow these steps when writing a review in a test cycle: Things to do in the Cycle Chat

1. Once you are done reporting bugs, open the Review tab and write a  Ask test cycle related questions
review about the product  Help out fellow testers by answering their questions only if you know the answer
2. Make sure your feedback is complete, and all the fields have full, clearly  Clarify scope questions
written sentences, so the review is helpful to the customer  Be professional (Customers see the chat messages)
 Check previous messages for answers before posting a question
Submitting a Usability Study  Make sure to use only English when asking questions in Chat
Follow these steps when submitting a usability study:
Things not to do in the Cycle chat
1. Carefully read the requirements which can be found in the overview, slots
tab, or slot description  Asking about payouts
2. Provide robust answers to all survey questions  Requesting the TTL/TE or customer to review your bugs
3. Give complete narration to all videos  Disputing your rejected issues
4. When finished click on Study Complete button to submit  Being rude and unprofessional
5. Upload required screenshots or videos  Do not use All caps to draw attention

If you are concerned about your questions privacy or the nature of the
Communication question is complicated, you can ask the TTL to send you a private
message. Or in case you want to escalate to the TE please, review the email
When you test in the uTest test cycles you may have questions or section for escalations.
confusions sometimes. We know that, so we offer testers easy and various Tagging in the Chat room
ways to communicate with the testing team inside a test cycle.
There are 4 main types of communication in a test cycle:  A tester and TTL can mention @testername to be highlighted in the chat room for
that tester or the TTL name. Only that tester or TTL will see their own name
 Test Cycle Chat highlighted in the chat room
 uTest Project Chat Channel  A tester can mention @ttl to be highlighted in the chat room. Only the TTLs
 Tester Messenger assigned to that cycle will see the highlighted @ttl in the chat room
 E-mail  TTL can mention @all to be highlighted for all users in the chat room. This will
help to get the attention of everyone in the chat room
Test Cycle Chat
 Red Chat notification icon for mentions along the right-hand side of the Chat screen for easy visibility that won't
interrupt the rest of the view of Chat.
 When you are @mentioned by name in a chat room, a number will display within
the red dot to denote that you have specifically been @mentioned in a message
Chat Reactions

Search Testers will be able to “react” to Chat messages using a variety of pre-set
reactions: 👍👎✔ ✖ 👀 +1. This will help the testing teams in distinguishing
The uTest chat allows testers to find specific messages that have been sent who has seen a message or if multiple testers are having the same
by a tester, TTL, TE, TSM, or customer within the chat by using keywords. question/problem, etc.

1. Open the cycle's Chat How to use Chat reactions feature:

2. Click on the Search textbox field
3. Type the word or phrase you're looking for in the Search field, and then 1. On a message in Chat, click the 3 dots on the right-hand side
press Enter key or click on the Search button 2. Select one of the available reaction options: 👍👎✔ ✖ 👀 +1
o Count of matching results, showing how many times the keyword or 3. Your own reaction will appear in blue - others’ reactions will appear in
phrase appears in the Chat grey
o Matching results will be highlighted in yellow in the Chat, so they can be 4. If you re-click your own reaction, it will go away
easily spotted 5. If you want to react to a message that another fellow tester has already
o Next/Previous buttons enable you to scroll to the next/previous instance reacted to, simply click on the reaction icon, and it will increase the count
of a term appearing in the Chat by 1 and if you want to remove it, then click on it again
o If no matching search results are present in the Chat, “No message
found” will appear In addition to that, you will be able to see the number of people who
reacted, but will not be able to see the names of the people who reacted. A
Note: Only exact matches will be highlighted in yellow in the search box. user with TTL, TE, or TSM privileges will also be able to see the names of
These matches can be scrolled by using the next/previous buttons. Partial those who reacted and the timestamp of each reaction.
matches will appear in bold throughout the chat, but will not be highlighted The benefit of this feature is to decrease the amount of clutter in Chat, as
in yellow. questions/announcements can be acknowledged without asking the same
Threaded messages question numerous times.

Threaded messages enable testers and TTLs to reply directly to a message Project Chat Channel
in Chat, and the reply will appear in-line beneath the original message. You
can reply to a specific message by selecting reply from the 3dots menu, then The uTest Project Chat Channel enables Testing Services to communicate
type your reply in the thread section on the right side of the chat. easily about project work with community Testers without relying on third-
party tools.
The number of replies will appear beneath an original message if it already
has replies. Clicking on the number of replies link will open the thread
What is the purpose of the Project Chat? receive any response in chat within 24 hours. Do not ask questions in email
which can be easily asked inside cycle chat.
It is common for testing projects to span multiple test cycles or to require
coordination with testers prior to tests launching. Project Chat Channel will Note that TEs and TSMs are often busy handling hundreds of test cycles
facilitate communication about a project outside of a specific test cycle. and it may take some time for them to reply to your question.
How can I find the Project Chat Channel? Cycle related questions, need to be always addressed to the TE first. If you
do not receive a reply in 24 hours, you can forward the message to the
Testers that have been invited to Project Chat Channel, will be able to find
TSM. You can see the TE and TSM emails in the team communication
the Channel in the Projects section above the Active Test Cycle section in
section in each cycle overview.
the uTest chat left navigation.
When to contact the TE or TSM:

 You suspect there is a tester committing fraud, most common ones:

Tester Messenger  Tester copying another tester's work
 Tester submitting placeholder issues
The Tester Messenger is a tool that is used to communicate within bug
 Tester with multiple accounts
reports and test cases.
 Payout issue
A TTL, TE, TSM or customer can initiate the Tester Messenger by sending
 A problem in communication with the customer (When the customer sends you
a message to the tester. This will automatically send an email notification to
messages in issue reports)
the tester.
 You have a question about an active test cycle, but it is sensitive and you rather
One note of caution: Please communicate professionally with TTLs, TEs, discuss this matter privately
TSMs, and customers. If you wish to dispute an incorrectly rejected issue,  Your question in chat is not being answered for more than 24 hours
you have to use the Dispute feature (Never use the Tester Messenger to
dispute or ask the customer to approve your bug). DO NOT contact the TE and TSM in these situations:

To respond to the message:  Your bug was rejected and you want to know why (Use the "Dispute Rejection" if
you think the bug is valid)
1. Sign into the uTest platform  You have a question about the cycle scope and instructions (Use the cycle chat
2. Open your bug report or test case instead)
3. Click the Messages tab  You have a general uTest question like how to submit bug reports (Check
4. Click New Message the Academy courses)
5. Write a reply in the text field
6. Click Add to send the reply When writing an E-mail, keep in mind these instructions to make
it easier to reply:
Email
 In the email subject, write the test cycle ID with a short description of your
Email should only be used when there’s something urgent (Like not able to
problem
access chat, claim a slot to join the test cycle), confidential or you didn’t
 In the email body, describe your issue/question briefly and precisely including all
information to resolve your problem as fast as possible.
 Always keep communication professional and polite

Best Practices

 Always try to ask questions related to test cycles inside cycle chat
 Do not ask payout related questions in chat, tester messenger
 Do not break the uTest Guidelines
 Always be professional and respect everyone
 Do not make noise, and do not repeat the same the question over and over again