Code of Conduct

 

Rules of Engagement 

  1. Do not share project payment information publicly or privately with other community members.
  2. Treat everyone with respect.
  3. Do not post sexually implied or explicit content within the community or send unwanted and inappropriate private messages.
  4. Do not post or transmit any message that is libelous or defamatory.
  5. 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., @$#%*).
  6. Do not create more than one account or use another member’s account at any time.
  7. Do not falsify information in your profile, including your name, location, and areas of expertise.
  8. Do not inflate your company’s products or services or deflate your competitor’s products or services.
  9. Do not harvest or collect any member identifying information by any means for the purpose of sending unsolicited email or other communications.
  10. Do not copy or use any material found on the site unless you have expressed permission.
  11. Do not post any infringing content to the site.
  12. Do not post unauthorized commercial advertising anywhere on the  site, including your profile.

Code of Conduct for Projects

As a Tester, you are expected to:

  1. Never publicize customer information outside the 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.
  2. Never use file sharing sites to host any information from your testing sessions - instead, always attach relevant files directly onto the  platform (80MB limit; up to five files per report.)
  3. Never discuss or question payouts in front of customers, whether via bug reports, chat, disputes, or Messenger. All comments related to payouts should be directed to the manager.
  4. Never contact customers or Test Team Leads outside of the  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./
  5. Always be professional and polite when communicating with other testers, project managers, and especially customers (via chat, reports, disputes, and the Tester Messenger). 
  6. Always follow test cycle instructions by reading the Cycle Scope thoroughly and any announcements in Chat. Additionally, 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.)
  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  account or payment account or share them with anyone.
  9. Never falsify information in your tester profile, including but not limited to your name, location, hardware, software, payment instrument information and any other profile information available to be stored.
  10. Never use emulators, simulators, remote machines, beta software, or “jailbroken” devices for testing, unless otherwise instructed. When testing, all third party VPNs, SSH tunnels, proxy server connections, IPSec connections and other software or connections that could be used to track and transmit sensitive information—including but not limited to test application performance, features, capabilities and test instructions, results and artifacts—must be completely disabled while participating on any  Project or removed entirely from the test environment/device used for testing.
  11. Never ask or solicit 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.
  12. If a project requires you to download an Application or test/data artifact to your device, always promptly delete such Application or artifact from your device upon the completion of the project unless otherwise instructed by an employee.
  13. If a project requires you to access a password-protected or non-public website, never access such website after the completion of the project unless otherwise instructed by an employee or the cycle TTL., and always promptly delete any test or data artifacts from your device upon completion of the project.
  14. If a project requires the use of a proxy server, third party VPN or other connection or software that could be used to track and transmit device information, including features and behaviors of other installed applications, the connection or software must always be disabled or removed from the device when participating on any other project.


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