GetYourTester User Guide

Everything you need to know to get the most out of on-demand manual QA for your GitHub pull requests.

1. What is GetYourTester?

GetYourTester is an on-demand manual QA/testing service that integrates directly with your GitHub pull requests. Request a test with a simple comment, and receive expert bug reports and usability feedback before you merge.

2. How to Get Started

  1. Install the GitHub App: Install GetYourTester on your repository. You can choose which repos to enable it for.
  2. Open a Pull Request: Create or update a PR in your enabled repository.
  3. Look for the Welcome Message: The GetYourTester bot will comment on your PR with instructions.

3. How to Request a Test

To request a manual QA round, simply add a comment to your PR that starts with /test. You can include details about what you want tested, browsers/devices, and any special requirements.

Example test request comment:
/test

Please run a full manual QA on this PR. Here's what I'd like you to focus on:
- Main goal: Verify the new user onboarding flow (sign up, email verification, and first login).
- Browsers: Chrome (latest), Firefox (latest), Safari (latest).
- Devices: Desktop and mobile (iPhone 13, Pixel 6).
- Test data: Use test email addresses (e.g., test+onboarding1@myapp.com).
- What to look for:
  - Any blockers or bugs in the onboarding steps
  - Usability issues or confusing UI
  - Broken links, typos, or missing error messages
  - Accessibility issues (keyboard navigation, screen reader basics)
  - Edge cases (weak passwords, invalid emails, slow network)
- Environment: https://staging.myapp.com
- Test user: testuser / password: Test1234!

4. What Happens Next?

  1. Your test request is received by the GetYourTester team.
  2. Testing usually begins within 4 hours (often much faster).
  3. You'll receive comments in your PR with bug reports, usability feedback, and a final test report when everything is verified.

5. Understanding Bug Reports & Test Reports

Bug reports and test reports are posted as comments in your PR. Here's what they look like:

Bug Report Example
### 🐞 Bug Report

Summary:
After submitting the sign-up form with a valid email and password, the app shows a "Something went wrong" error and does not create the account.

Steps to Reproduce:
1. Go to https://staging.myapp.com/signup
2. Enter a valid email and password
3. Click "Sign Up"
4. Observe the error message

Expected Result:
User account should be created and redirected to the email verification page.

Actual Result:
An error message appears: "Something went wrong. Please try again later." No account is created.
Final Test Report Example
### ✅ Final Test Report

Scope:
- Full manual QA of the new user onboarding flow
- Browsers: Chrome, Firefox, Safari (latest)
- Devices: Desktop (Mac, Windows), Mobile (iPhone 13, Pixel 6)

Summary:
All critical and high-priority issues have been fixed. The onboarding flow now works smoothly across all tested browsers and devices.

Results:
- No blockers or major bugs found
- Minor UI issues from previous round have been fixed
- Usability is good, error messages are clear
- Accessibility is improved (labels, focus order)

Recommendation:
Ready to merge! 🚀

6. Frequently Asked Questions (FAQ)

During early access, your first few test requests are free. If you find value, you're welcome to support the project via BuyMeACoffee. Future pricing will be announced.

All tests are performed by Ovi Donciu (15+ years QA experience) and a small group of trusted expert testers. You always get real, human feedback.

Acceptance, regression, exploratory, UI/UX, API, performance, and basic accessibility testing. If you have special requirements, just mention them in your /test comment.

Testing usually starts within 4 hours of your request, and first results are typically delivered within 4–24 hours.

Yes! Just include your requirements in the /test comment. The more details you provide, the better the coverage.

7. Need Help or Have Questions?

If you have questions, want to give feedback, or need support, you can: