Tester Agreement

Tester Agreement

Effective Date: 7 October 2026
Last Updated: 7 October 2026

This Tester Agreement (“Agreement”) applies to individuals who register with or participate in testing projects through TestmeQa, operated by TestmeQa Limited (“TestmeQa”, “we”, “us”, or “our”).

By registering as a tester, accepting a testing project, or submitting testing results through TestmeQa, you agree to this Agreement, our Terms of Service, and our Privacy Policy.

1. Becoming a TestmeQa Tester

To participate as a tester, you must provide accurate information about yourself, including information relevant to your testing skills, experience, devices and availability.

You agree to keep your profile information accurate and up to date.

TestmeQa may review the information provided in your profile when determining eligibility or suitability for testing projects.

Registration does not guarantee that you will receive testing projects.

2. Tester Profile

Your profile may include information such as:

  • Testing experience;
  • Testing skills;
  • Areas of specialisation;
  • Devices;
  • Operating systems;
  • Browsers;
  • Location where relevant;
  • Availability; and
  • Previous project participation.

You must not misrepresent your qualifications, experience, devices or other information.

3. Project Invitations

TestmeQa may invite you to testing projects based on factors such as:

  • Your skills;
  • Experience;
  • Device compatibility;
  • Location;
  • Availability;
  • Project requirements; and
  • Previous testing performance.

You are free to accept or decline a project unless otherwise agreed for a specific engagement.

4. Project Requirements

Before beginning a project, you should review all project instructions carefully.

Project requirements may specify:

  • What should be tested;
  • What should not be tested;
  • Testing environments;
  • Supported devices;
  • Testing dates;
  • Testing procedures;
  • Bug-reporting requirements;
  • Payment terms;
  • Confidentiality requirements; and
  • Other project-specific instructions.

You agree to follow all applicable project requirements.

5. Testing Scope

You may only test systems, applications, features and environments that are expressly included in the project.

Being invited to test a product does not give you unrestricted permission to access the client’s systems.

You must not:

  • Access systems outside the authorised scope;
  • Attempt to access another user’s account;
  • Attempt to obtain administrative access;
  • Test unrelated systems;
  • Perform denial-of-service attacks;
  • Introduce malware;
  • Delete or modify production data;
  • Access unnecessary personal information; or
  • Conduct security testing unless specifically authorised.

If you discover a potentially serious security vulnerability, follow the reporting instructions provided for the project and do not attempt to exploit the vulnerability further.

6. Confidentiality

You may receive confidential information while participating in a project.

Confidential information may include:

  • Unreleased applications;
  • Websites;
  • Features;
  • Product designs;
  • Source code;
  • Business information;
  • Test credentials;
  • Customer information;
  • Screenshots;
  • Screen recordings;
  • Documents;
  • Product roadmaps; and
  • Other non-public information.

You agree to keep all such information confidential.

You must not:

  • Share project information with friends or other testers who are not authorised;
  • Publish screenshots or recordings;
  • Post project information on social media;
  • Share test credentials;
  • Discuss unreleased features publicly; or
  • Use confidential information for personal purposes.

These confidentiality obligations continue after you leave a project or stop using TestmeQa.

7. Test Data and Personal Information

You may encounter personal information while testing.

You must:

  • Access only information necessary for the assigned testing task;
  • Avoid copying unnecessary personal information;
  • Avoid downloading personal information;
  • Not share personal information with others; and
  • Immediately report accidental exposure of sensitive information through the appropriate project channel.

Where possible, testing should use test or synthetic data rather than real customer information.

8. Bug Reports

Bug reports should be:

  • Accurate;
  • Clear;
  • Reproducible;
  • Relevant to the project;
  • Submitted within the required timeframe; and
  • Supported by appropriate evidence where requested.

A useful bug report should generally include:

  • A clear title;
  • Steps to reproduce;
  • Expected result;
  • Actual result;
  • Environment/device information where relevant;
  • Severity or priority where required; and
  • Screenshots, recordings or other evidence where appropriate.

9. Prohibited Bug Reporting Practices

You must not:

  • Invent bugs;
  • Deliberately create failures and report them as existing defects;
  • Submit duplicate reports repeatedly;
  • Copy another tester’s report and claim it as your own;
  • Manipulate evidence;
  • Submit reports outside the project scope; or
  • Attempt to generate reports solely to obtain payment.

TestmeQa may reject submissions that do not meet project requirements.

10. Bug Validation

TestmeQa or the relevant client may review submitted reports.

A report may be classified as:

  • Valid;
  • Invalid;
  • Duplicate;
  • Not reproducible;
  • Out of scope;
  • Expected behaviour; or
  • Another category specified by the project.

The applicable project terms may determine whether a submission qualifies for payment.

11. Tester Payments

Where a project provides payment, the project information will specify the applicable payment terms.

Payment may depend on:

  • Completing the assigned testing work;
  • Submitting valid results;
  • Meeting project deadlines;
  • Following project requirements; and
  • Successful validation of submissions.

Fraudulent, duplicated, invalid or unauthorised submissions may not qualify for payment.

Payment methods and payment timelines may vary between projects.

12. Taxes

You are responsible for understanding and complying with any tax obligations arising from payments you receive through TestmeQa.

TestmeQa may be required to collect or report certain information where required by applicable law.

13. Tester Conduct

You agree to behave professionally when interacting with:

  • TestmeQa staff;
  • Clients;
  • Other testers; and
  • Members of the TestmeQa community.

Harassment, threats, discrimination, abusive behaviour, impersonation and other inappropriate conduct are prohibited.

14. Client Communication

Unless a project specifically permits direct communication, testers should communicate with clients through the channels provided by TestmeQa.

You must not use project information to bypass TestmeQa or establish unauthorised arrangements with clients for the purpose of avoiding TestmeQa fees or processes.

15. Intellectual Property

You retain ownership of materials that you created independently before participating in a project.

Testing reports and other project deliverables may be used by TestmeQa and the applicable client for the purposes described in the relevant project and applicable agreements.

You must not submit material belonging to another person without appropriate permission.

16. Account Security

You are responsible for keeping your TestmeQa account credentials secure.

You must notify TestmeQa if you believe someone has gained unauthorised access to your account.

You must not allow another person to use your tester account.

17. Account Suspension or Termination

TestmeQa may suspend or terminate your tester account if you:

  • Violate this Agreement;
  • Submit fraudulent reports;
  • Misuse client information;
  • Breach confidentiality;
  • Perform unauthorised testing;
  • Provide false information;
  • Attempt to manipulate payments; or
  • Engage in other prohibited conduct.

Where appropriate, TestmeQa may provide notice of the reason for the action.

18. Reporting Security or Privacy Incidents

If you accidentally access confidential information, personal data or a system outside the authorised scope, stop the activity immediately and report the incident through the appropriate TestmeQa channel.

For urgent concerns, contact:

help@testmeqa.com.ng

19. No Guarantee of Projects

Joining TestmeQa does not guarantee that you will receive a particular number of projects, assignments or payments.

Project availability depends on client demand, project requirements and tester suitability.

20. Relationship With TestmeQa

Unless a separate written agreement states otherwise, participation as a TestmeQa tester does not by itself create an employment relationship between you and TestmeQa Limited.

You are responsible for complying with applicable laws relating to your participation and any income you receive.

21. Changes to This Agreement

TestmeQa may update this Agreement from time to time.

Where material changes are made, we may provide appropriate notice.

Continued participation in TestmeQa after the updated Agreement becomes effective constitutes acceptance of the revised Agreement.

22. Governing Law

This Agreement is governed by the laws of the Federal Republic of Nigeria, subject to applicable law.

23. Contact

For general support:

help@testmeqa.com.ng

For formal complaints or disputes:

dispute@testmeqa.com.ng

TestmeQa Limited

Website: testmeqa.com.ng

Scroll to Top