Testing Party Tutorial

Learn how to participate in testing parties, submit bugs, and climb the leaderboard!

Getting Started

1
Login with RegardingWork

Use your RegardingWork Hub account to login. If you don't have an account yet, click "Create Hub Account" on the login page.

2
Browse Testing Parties

From the dashboard, you'll see all available testing parties. Each party has a unique ID (like TP001) that you can use to quickly find it. Active parties are shown at the top.

Joining a Testing Party

3
Apply to Join

Click on a testing party to view its details. If you haven't applied yet, click the "Apply" button. Your application will be reviewed by the IT manager.

4
Wait for Approval

Once you apply, your status will show as "Application Pending". When approved, you'll see "✓ Approved" and can start testing!

Submitting Bug Reports

5
Find Bugs

Test the application thoroughly. Look for issues with functionality, user experience, visual problems, or errors in the console.

6
Document Your Findings

For detailed bug reports with screenshots and developer console logs, use https://my.contentinvestments.com. This helps IT managers understand and reproduce the bug.

7
Submit the Bug

Fill out the bug submission form with:

  • Title: A clear, concise description of the bug
  • Bug Link: Link to your detailed bug report (from contentinvestments.com)
  • Description: (Optional) Brief summary of the issue

Click "Submit Bug" to send your report.

Earning Points & Leaderboard

8
Bug Ratings

After you submit a bug, the IT manager will review it and assign a rating from 0-10 based on:

  • Severity of the bug
  • Quality of documentation
  • Usefulness for the development team
9
Climb the Leaderboard

Your total points from all rated bugs are displayed on the party's leaderboard. The more quality bugs you find and report, the higher you'll rank!

Tips for Success

🎯 Best Practices
  • Be thorough: Include steps to reproduce, screenshots, and console logs
  • Be clear: Write bug titles that quickly describe the problem
  • Be specific: Note the exact page, feature, or action that caused the bug
  • Check for duplicates: Review existing bug reports before submitting
  • Test systematically: Go through all features and user flows