Prerequisites

Requirement	Details
GitHub App	Bouncer GitHub App installed on your repository
TestParty Account	Enterprise license with Bouncer Plus enabled
Repository Access	Admin permissions to approve GitHub App installation
Security Clearance	Organization approval for GitHub App permissions (if required)

Note: Bouncer Plus uses the same GitHub App as Bouncer. If Bouncer is already installed, you only need to enable the Bouncer Plus toggle—no additional installation required.

Step 1: Install the Bouncer GitHub App

If you haven't already installed Bouncer:

1. Go to the GitHub App installation link: https://github.com/apps/testparty-bouncer/installations/select_target

2. Select the repository where you want to enable Bouncer Plus.

3. Grant the required permissions (read/write to PRs and code).

Enterprise Security Considerations

If your organization has GitHub App approval policies:

• Security review: Provide your security team with TestParty's SOC 2 documentation.

• AI governance: TestParty has passed AI governance reviews at enterprise organizations—request documentation from your TestParty representative.

• IP allowlisting: If required, request a stable IP from TestParty for your allowlist configuration.

• Org-level rules: Your DevOps team may need to configure bypass rules to allow the bot to open PRs and write to the repository.

Step 2: Enable Bouncer Plus

1. Log into your TestParty account at https://app.testparty.ai

2. Navigate to your project dashboard.

3. Locate the Bouncer Plus section (below Bouncer metrics).

4. Toggle Bouncer Plus to enabled.

Bouncer Plus will begin indexing your repository. This typically completes within minutes.

Step 3: Configure Settings

Target Branch

Specify the branch that Bouncer Plus PRs will merge into.

Options:

• Main branch: PRs merge directly into main or master.

• Dedicated feature branch: Create a branch like accessibility-fixes to isolate changes. This allows grouped QA testing before merging to main.

Reviewers

Assign 2–3 reviewers who will be tagged on every Bouncer Plus PR.

Recommendations:

• Distribute across team members to prevent bottlenecks.

• Include at least one developer familiar with the codebase.

• Consider including someone with accessibility expertise.

Auto Mode

Mode	Behavior
Automatic	After a PR is merged or declined, Bouncer Plus automatically queues the next file for review.
Manual	You click "Review Next File" to trigger each review.

Start with manual mode to get familiar with the workflow, then switch to automatic once your team has a review rhythm.

Step 4: Verify File Indexing

Before deep processing, review the first few files to ensure Bouncer Plus is scanning the right code.

What gets indexed:

• TypeScript files (.ts, .tsx)

• JavaScript files (.js, .jsx)

• Other front-end files relevant to UI rendering

What gets excluded:

• Localization files

• Configuration files

• Non-UI code (backend, utilities)

• Generated files

If you need custom exclusion patterns (e.g., legacy code marked for deprecation, generated files), contact TestParty support.

Troubleshooting Installation

Issue	Solution
GitHub App won't install	Verify you have admin permissions on the repository. Check if org policies require approval.
No files indexed	Ensure the repository contains front-end files (JS, TS, JSX, TSX). Check that Bouncer Plus is enabled in project settings.
Blocked by org policy	Work with your DevOps/security team to allowlist the TestParty GitHub App. Provide SOC 2 documentation if required.
IP blocked	Request a stable IP from TestParty for your allowlist configuration.
Authentication errors	Confirm the GitHub App installation is active. Reinstall if necessary.

Previous: Overview

Next: Workflow