Starting your first project

When you receive an email notification regarding a new active test cycle, sign in to uTest and click on "Test Cycles." Next, click on the appropriate test cycle and read the “Product & Settings” and “Scope & Instructions” sections closely. It is important that you review all instructions and documentation before you start testing to avoid "out of scope" bugs, which will lower your tester rating. In addition, it is suggested that you review the list of "reported bugs" so that you have an idea of what has already been reported (you can view this by clicking on the Bugs & Test Cases link found in every test cycle (or via the master Bugs & Test Cycles link located at the top of the page, and then filter by test cycle). Remember, before you are able to view the testing URL and report a bug, you must accept the Test Cycle Agreement found at the bottom of the Scope & Instructions page.

Also, if you are new to uTest and have not attended a weekly webinar session, please click here (in addition to the live sessions that you can register for, we also provide a previously recorded session for you to view at your convenience).

Recommendations for new uTesters: Before you get started, please register for a uTest Forums account by using the same email address associated with your uTest account. Then, introduce yourself to the community with a few words about your professional testing experience. Next, read more about our Sandbox Program and apply if necessary (most projects are now private and are only viewable to testers who are invited. If you don’t participate in our Sandbox program, you may still occasionally receive public test cycles). Even after you participate in a Sandbox class, it is important to visit the forums on a regular basis to learn more about upcoming projects in need of testers. Before you begin your first test cycle, we advise you to review the New uTester Checklist to ensure that you succeed from your very first endeavor with uTest.

FAQ: I emailed the project manager regarding a new project and have not heard back. Why?

• Certain projects require testers to email screening information to the project manager in order to allocate testing slots to the appropriate testers. If you qualify for the test cycle, you will hear back from the PM Team - typically within 24 hours. If you do not hear back within 24 hours, this means that the number of slots has been filled or there was not a good match between your profile and project requirements.