📄Revvy Bounty Testing: P1 and P2 Definitions & Testing

Purpose

This guide outlines Revvy’s structured bounty testing plan for Connections, Code, Pull Requests, and Pipelines tabs. It defines:

• Systematic testing of all visible buttons and workflows.

• Clear P1, P2 issue categorization for consistent reporting.

• Eligibility requirements for testers to qualify for bounties through real-world workflow validation.

---

Pre-Requisites for Bounty Eligibility

To qualify for bounties, testers must complete the following:

1. Connect at least 3 Salesforce orgs (Developer, Sandbox, Production).

2. Retrieve at least 50,000 metadata components from one org to test scalability (e.g., ApexClasses, Triggers, Objects).

3. Create at least 4+ branches, 2+ pull requests, and complete a merge workflow.

4. Create and run at least 1+ pipeline with the following operations:

   • Deploy

   • Validate

   • Rollback

   • Manual Step

5. Test all buttons for:

   • Functionality

   • Stability

   • Correct workflow execution

6. Document issues with:

   • Clear reproduction steps

   • Screenshots or videos

   • P1 or P2 labels for validation

Note: Refer to the Revvy Advanced Certification Hands-On Scenario Guide for workflow examples and branching strategy details.

---

Priority Definitions

Priority	Definition	Examples	Bounty Weight
P1	The task affects customers	Cannot deploy, retrieve metadata, or create PR	High
P2	The task affects customers, but there is a non-technical workaround	Validate fails but deploy works; partial metadata retrieval	Medium

---

Testing Scope

1. Connections Tab

Buttons to Test

• ➕ Add Connection

• 🔄 Retrieve

Test Requirements

• Add Developer, Sandbox, and Production org connections successfully.

• Retrieve metadata (e.g., ApexClasses, Triggers, Objects) from all connected orgs.

• Verify metadata count, types, and retrieval accuracy.

Priority Examples

Priority	Definition	Examples
P1	Add Connection or Retrieve fails, affecting customers	OAuth fails, retrieval never completes, no metadata retrieved
P2	Partial retrieval or UI issues with non-technical workaround	Missing metadata types, requires manual refresh, stuck spinners

---

2. Code Tab

Buttons to Test

• ➕ Create Branch

• ➕ Add Components

• 🚀 Deploy (with sub-options):

  • Validate

  • Overwrite Protection

  • PreDeploy Fix

Test Requirements

• Create branches and verify they reflect correctly.

• Add components accurately for deployment.

• Test all deploy sub-options (Validate, Overwrite Protection, PreDeploy Fix).

• Validate-only deployments.

• Verify deployment results and sub-option functionality.

Priority Examples

Priority	Definition	Examples
P1	Create Branch, Add Components, or Deploy fails, affecting customers	Cannot create branches, deploy button unresponsive, validate always fails
P2	Partial deploy sub-option issues with non-technical workaround	Overwrite protection Not working, PreDeploy fix fails

---

3. Pull Requests Tab

Buttons to Test

• ➕ Create Pull Request

• ✅ Merge

• 📄 Components Changed

Test Requirements

• Create PRs between branches.

• View diffs in “Components Changed” section.

• Merge PRs and verify changes reflect on the target branch.

Priority Examples

Priority	Examples
P1	PR creation or merge fails, affecting customers
P2	Diff issues with non-technical workaround

---

4. Pipelines Tab

Buttons to Test

• ➕ Create Pipeline

• ▶️ Run Pipeline

• ⚙️ Pipeline Operations:

  • Deploy

  • Validate

  • Rollback

  • WebHook

  • Manual Step

Test Requirements

• Create pipelines with Deploy, Validate, Rollback, WebHook, and Manual Step operations.

• Run pipelines and verify execution flow.

• Confirm accurate status updates (e.g., Pending, Success, Failed).

Priority Examples

Priority	Examples
P1	Create Pipeline or Run Pipeline fails, affecting customers
P2	Some pipeline operations fail with non-technical workaround

---

Bounty Eligibility Rules

To earn bounties, testers must:

1. Test every button for functional correctness and end-to-end workflow completion.

2. Document issues via case submission with:

   • Reproduction steps

   • Screenshots or videos

   • P1 or P3 labels (verified by Revvy team)

3. Test across all tabs:

   • Connections: Add, Retrieve

   • Code: Create Branch, Add Components, Deploy (Validate, Overwrite, PreDeploy Fix)

   • Pull Requests: Create, Merge, Components Changed

   • Pipelines: Create, Run, Operations (Deploy, Validate, Rollback, WebHook, Manual Step)

---

Bounty Payout Structure

Priority	Payout Range	Condition
P1	$10	Validated as blocking and reproducible
P2	$5	Validated as affecting customers with a non-technical workaround

---

Submission Steps for Bounty Program

1. Open Revvy.io’s Intercom Messenger (bottom-right corner).

2. Select Submit Bounty Testing.

3. Upload all screenshots or videos.

4. Submit all bugs and feature requests via support tickets

5. Click Submit.

   

---

Support

Stuck? We’ve got you covered! 💬 Open Intercom Messenger to:

• Ask a question

• Report a bug

• Send a message

Our team is here to ensure your success.

---

Additional Notes

• Ensure all reported issues are reproducible and include sufficient evidence (e.g., screenshots, videos).

• The Revvy team reserves the right to validate and categorize reported issues.

• For workflow inspiration, review the Revvy Advanced Certification Hands-On Scenario Guide.