Skip to main content
The GitHub integration connects your repositories to TestDino for automated test reporting.

​
How does it work?

It provides visibility into test outcomes by posting AI-generated summaries directly to commits and pull requests. This allows teams to review test health and identify failures without leaving the GitHub UI. Once configured, the integration works automatically:
  • Detects Playwright runs from GitHub Actions and attaches results to the commit/PR.
  • Comment includes a link back to the TestDino run.
  • Branch Mapping controls where comments appear.
  • Post GitHub CI Checks (pass/fail) based on your quality gate settings.
  • Now you can block merges until the required test conditions are met.
With both comments and CI checks enabled, teams can see detailed summaries in the PR conversation and enforce quality rules directly through GitHub’s status checks. (see: GitHub CI Checks User Guide.)

​
Quick Start Steps

​
1. Install the app

Open the GitHub Marketplace listing for TestDino | Playwright Reporter, then click Install & Authorize. Install the app

​
2. Select repositories

Choose your Organization. Then, grant access to all or specific repositories. Select repositories

​
3. Configure Comments

In Settings → Integrations → GitHub, customize the connection. Click the ⚙️ icon on the GitHub card to open the GitHub Comment Settings Configure Comments
Note:
  • Branch Mapping (in settings) must be configured before configuring the comments setting.
  • In GitHub Settings (⚙️ on the GitHub card), map branch patterns per environment and toggle comments for PR and Commits.
  • Environment overrides take precedence over global defaults.

​
4. Configure CI Checks

Similarly, open the CI Checks tab. Here you can:
  • Toggle Enable GitHub Checks
  • Enter Mandatory Tags (optional)
  • Set a default Pass %
  • Choose Flaky Handling
  • Configure Environment Overrides for your own environments like PROD, STAGE, or DEV (see: Environment Overrides).
Once saved, TestDino will start sending pass/fail status checks to GitHub for matching commits and pull requests. (see: Quality Gate Settings)

​
4. Run CI

Push code or open a PR; your Playwright workflow triggers as usual. TestDino receives the test results and posts both:
  • A PR comment (if enabled)
  • A GitHub CI Check (if enabled)

​
Why this helps

  • Review faster with immediate test feedback directly in pull requests, eliminating the need to switch contexts.
  • Accelerate debugging with AI-driven failure analysis delivered into the relevant commit or PR.
Status checks, API keys, and CI optimization.

GitHub Status Checks

Configure PR status checks and quality gates

Azure DevOps

View test runs inside Azure DevOps

TeamCity Integration

Upload Playwright reports from TeamCity

Getting Started

Initial TestDino setup