FirstQA Documentation

Your complete guide to Ovi AI — confidence at speed through alignment, test automation, and expert QA.

1. What is FirstQA?

FirstQA gives startups confidence at speed. Ovi AI prevents bugs by creating alignment before coding starts, generates test scenarios and automated tests, reviews every PR, and connects you with expert human QA when needed. It's your first QA hire—without the headcount.

2. How It Works

1. 🔗 Connect Your Tools: One-time setup with GitHub, Bitbucket, Jira, or Linear
2. 📋 Ticket Review: Ovi analyzes tickets before coding—surfacing gaps, risks, and edge cases
3. 🧪 Test Recipe: Get actionable test scenarios engineers can run before code review
4. 🔍 PR Review: Every pull request analyzed for bugs, risks, and test coverage
5. 🤖 Test Automation: E2E automated tests generated and integrated into CI/CD
6. 👥 Manual Testing: Senior QA engineers for complex flows when you need them

3. Getting Started

Option A: GitHub App (for PR Analysis)

1. Install the GitHub App: Install FirstQA on your repository. Choose which repos to enable.
2. Open a Pull Request: Create or update a PR in your enabled repository.
3. Automatic Analysis: Ovi automatically analyzes your PR—bugs, risks, test scenarios, and release readiness.
4. Request Human QA: Add a comment with /test for comprehensive manual testing.

Option B: Chrome Extension (for Ticket Analysis)

1. Install the Extension: Add the FirstQA Chrome Extension from your account dashboard.
2. Navigate to a Ticket: Open any Jira or Linear ticket in your browser.
3. Click Analyze: Ovi analyzes the ticket—surfacing gaps, edge cases, risks, and test scenarios before coding starts.

4. Ovi AI - Your AI QA Engineer

Ovi creates alignment and confidence at every stage of development:

Ticket Analysis (Before Coding)

• 📋 Requirements Review: Surfaces missing requirements, ambiguity, and edge cases
• ⚠️ Risk Flags: Identifies potential issues before code is written
• 🧪 Test Scenarios: Generates test cases engineers can use to validate their work
• 🤝 Alignment: Ensures engineers, QA, and PM share the same understanding

PR Analysis (During Code Review)

• 🔍 Change Review: Analyzes code changes, identifies bugs, and generates smart questions
• 🧪 Test Recipe: Creates actionable test scenarios specific to the changes
• 📊 Impact Analysis: Identifies affected modules, test coverage gaps, and risks
• ⚠️ Release Readiness: Production readiness score (1-10) with confidence assessment

Test Automation

• 🤖 E2E Test Generation: Ovi generates automated end-to-end tests for your changes
• 🔄 CI/CD Integration: Tests integrate seamlessly into your pipeline
• 🛠️ Auto-Maintenance: Tests are updated as your codebase evolves

Production Readiness Scoring

5. Requesting Human QA Testing

To request comprehensive manual QA testing, 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.

/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!

6. What Happens Next?

1. Your test request is received by our expert QA 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.

7. Understanding Reports

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

### 🐞 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

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! 🚀

8. Pricing Preview

Here's what we're thinking. Final pricing confirmed before launch. Early access users get special pricing.

9. Frequently Asked Questions (FAQ)

10. Need Help or Have Questions?

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

• Contact us via the Contact form
• Schedule a demo call
• Email us at support@firstqa.dev
• Visit our Support page