In betaThe Keystone GitHub App provides the easiest way to integrate testing into your GitHub workflow with automatic test management and no configuration required. This will be ready for general usage soon.
Why GitHub App?
Zero Configuration
- No API keys in your repo
- Suite selection in Keystone UI
- Automatic branch detection
- Smart test promotion
Branch-based Testing
- Tests track their creation branch
- Automatic promotion on PR merge
- Dev overrides for staging URLs
- Production-ready test management
PR Status Checks
- Automatic check creation
- Real-time status updates
- Detailed failure reports
- Direct links to test results
Test Isolation
- Branch-specific test runs
- Staging URL overrides
- Clean test promotion
- No test pollution
Quick Start
1
Install GitHub App
Visit the GitHub Marketplace and install the Keystone Tests app to your organization or repository.
2
Authorize & Configure
After installation, you’ll be redirected to Keystone to:
- Select your default test suite
- Enable PR testing
- Configure branch promotion rules
3
Add Workflow
Create
.github/workflows/keystone.yml:4
Create & Merge
Tests created on feature branches automatically promote to production when PRs merge.
How It Works
Development Workflow
Test Promotion
When a PR is merged, all tests created on that branch are automatically:- Promoted to production status - marked as stable
- Cleared of dev overrides - staging URLs removed
- Ready for monitoring - available for scheduled runs
Configuration
In Keystone UI
Configure your GitHub App settings:- Basic Settings
- Advanced Settings
- Default Suite: Which test suite runs on PRs
- Branch Rules: Which branches trigger tests
- Required Checks: Make tests required for merging
In Your Repository
The only configuration needed in your repo:suite_id: Override the default suite for specific workflowswait_for_results: Set tofalsefor async executionfail_on_error: Set tofalseto allow PR merge despite test failures
Security
Permissions
Permissions
The GitHub App requires minimal permissions:
- Read: Repository metadata, pull requests
- Write: Commit statuses, checks
- No code access: We never read your source code
Authentication
Authentication
- OAuth flow for initial setup
- App installation tokens for API calls
- No long-lived credentials stored
- Automatic token rotation
Common Patterns
Feature Development
Monitoring Setup
Once tests are promoted:- They run on production URLs
- Available for scheduled execution
- Can be included in monitoring suites
- Alert on failures

