Rules of Engagement (applies to all uTest Community Members)

  1. Treat fellow members of the uTest Community with respect.
  2. Do not post or transmit any message that is libelous or defamatory.
  3. Do not use inappropriate language with any post or transmitted message, including the use of special characters between letters or in representation of foul language (e.g., @$#%*).
  4. Do not create more than one account or use another member’s account at any time.
  5. Do not falsify information in your uTest profile, including your name, location, and areas of expertise.
  6. Do not inflate your company’s products or services or deflate your competitor’s products or services.
  7. Do not harvest or collect any member-identifying information by any means for the purpose of sending unsolicited email or other communications.
  8. Do not copy or use any material found on the site unless you have expressed permission and consent from uTest.
  9. Do not post any infringing content to the uTest site.
  10. Do not post unauthorized commercial advertising anywhere on the uTest site, including your profile.

Code of Conduct for uTest ‘Expanded Profile’ Members (those who are eligible to receive paid projects)

As a uTester, you are expected to:
  1. Never publicize customer information, 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.
  2. Never use file sharing sites outside the uTest platform to host any information from your testing sessions - instead, always attach relevant files directly onto the uTest platform (100MB limit; up to five files per report.) If you can't attach your file due to size limitations, contact the PM. He or she will grant you access to a secure FTP site that will be able to host the large file.
  3. 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.
  4. Never contact customers or Test Team Leads (TTLs) outside of the uTest platform. Additionally, never contact project managers unless it is related to a test cycle that is pending, active or locked. IF a customer reaches out to you outside of the platform, please contact the project manager first for current cycles or for expired projects.
  5. 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.
  6. Always follow test cycle instructions by reading thoroughly through the cycle’s Scope and any announcements from the TTL/PM in Chat. Additionally, utilize the test cycle’s Chat to clarify any questions (however, do not post a bug to the chat, or email the PM, and request if it is valid or not.)
  7. Complete each assigned task thoroughly and honestly. This includes test cases on both one-time and recurring cycles. Be sure to submit all required documentation for bugs and test cases, and to never recycle work from either your own past submissions or poach others’. Additionally, honestly completing work also includes never creating ‘placeholder’ bug reports for editing at a later time.
  8. Never create more than one uTest account or payment account or share them with anyone.
  9. Never falsify information in your tester profile (e.g., name, location, hw/sw) and never use emulators, simulators, remote machines, beta software, or “jailbroken” devices for testing, unless otherwise instructed by a uTest employee.
  10. Never ask or beg the customer or project manager to approve your work, remove you from a cycle, or make you a favorite tester. 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.

Please note that the CM team, to protect the integrity and fairness of our Community, has the right to upgrade strike value on any of these Code of Conduct violations depending on severity of the infraction.