uTester Bill of Rights and Code of Conduct
uTest strives to create a consistent and level playing field. In our never-ending pursuit of fairness, we have defined a uTester Code of Conduct and a Bill of Rights. This is something we arrived at after countless hours of internal debate and discussion with testers, customers, and partners. As a living document, we will edit and add to these tenets over time, but the goal of them is to ensure fair treatment of all parties and to create a work environment that is sustainable, enjoyable, and effective.
uTester Code of Conduct
Our community is a vital part of what uTest is and does. Whether you participate in a paid test cycle, re-tweet our blog, or tell colleagues about us, you represent the uTest brand and all 70,000+ uTesters in every one of these interactions. The code of conduct sustains a level playing field and advance the uTest experience for all parties – customers and testers alike. Therefore, we take violations very seriously and reserve the right to suspend your account while investigations are underway. Furthermore, violations may result in temporary or permanent account suspensions in order to protect the integrity of the community.
As a uTester, you are expected to…
- Never publicize customer information outside the uTest Platform – including customer/product name or any information revealed in a test cycle. This includes testing a competitor's application and sharing information in any way. A recommended practice is to disable all applications with sharing functionality while you test. Due to the severity of this violation, infractions will result in the permanent suspension of your account.
- Never use file sharing sites to host any information from your testing sessions - instead, always attach relevant files directly onto the uTest platform (30MB limit per file; up to five files per report.)
- Never discuss or question payouts in front of customers, whether via bug reports, chat, disputes, or Tester Messenger. All comments related to payouts should be directed to the project manager.
- Never contact customers outside of the uTest platform. Additionally, never contact project managers unless it is related to a test cycle that is pending, active or locked.
- Always be professional and polite when communicating with other testers, project managers, and especially customers (via chat, reports, disputes, and the Tester Messenger). The uTest project manager is available to review your comment before you share with a customer.
- Always follow test cycle instructions and utilize the test cycle’s Chat to clarify any questions (however, do not post a bug to the chat and request if it is valid or not.)
- Never create more than one uTest account or payment account or share your uTest account or payment account with anyone else.
- Never falsify information in your tester profile (e.g. legal name, location, hardware) and never use emulators, simulators, remote-machines or beta software for testing, unless otherwise instructed by a uTest employee.
- Never create a “placeholder” bug report, only to alter its content later.
- Never ask, whine or beg the customer or project manager to approve your work or remove you from a cycle. If you believe your bug was rejected mistakenly, dispute the rejection directly from the test cycle or contact the Project Manager if you have more than five rejected bugs.
uTester Bill of Rights
As a uTester, you have certain rights in your engagement with uTest and its customers. These serve to protect you from unfair treatment, ensure consistency across our community, and enable you to be a productive uTester.
As a uTester, you have the right to…
- Be treated fairly and professionally by uTest and its customers
- Be paid accurately and in a timely manner, twice per month via PayPal or Payoneer
- Receive clear scope, instructions and payouts for each test cycle before you accept or decline
- Decline a test cycle if you do not wish to participate
- Receive timely updates about changes to test cycle scope or payout
- Ask questions about the scope of a test cycle via the Chat and receive clarifications during a test cycle in a timely fashion (email firstname.lastname@example.org if you do not receive a response within 24 hours)
- Have your reports reviewed within 35 days of the test cycle becoming locked (contact email@example.com if this is not the case)
- Dispute a rejected report within the stated rules and monthly limits
- Contact a project manager about any pending, active or locked test cycle, so long as the question is professional (email firstname.lastname@example.org if you do not receive a response within 24 hours)
- Contact a community manager if your question is not about a specific test cycle, preferably via the uTest Forums (otherwise via email@example.com)