Installation
Install FixSense as a GitHub App and start analyzing CI failures in under 2 minutes.
Prerequisites
Before installing FixSense, make sure you have:
- A GitHub, GitLab, Azure DevOps, or Bitbucket Cloud account
- At least one repository with Playwright or Cypress tests
- A CI pipeline that runs your tests (GitHub Actions, GitLab CI, Azure Pipelines, or Bitbucket Pipelines)
Step 1: Install the GitHub App
- Go to FixSense and click Get Started
- Sign in with your GitHub account
- Click Install GitHub App
- Select the repositories you want to monitor
- Approve the required permissions
FixSense only needs read access to your code and CI logs, plus write access to post PR comments and create fix branches.
Step 2: Configure Playwright for FixSense
FixSense parses JUnit XML test results. Add the JUnit reporter to your playwright.config.ts:
reporter: [
['junit', { outputFile: 'test-results/results.xml' }],
['html'], // keep your existing reporter
],Then make sure your CI workflow uploads the results as an artifact:
- name: Upload test results
if: always()
uses: actions/upload-artifact@v4
with:
name: playwright-report
path: test-results/
retention-days: 7Without the JUnit reporter, FixSense cannot parse test failures. The default html or list reporters are not supported for analysis.
Recommended CI settings
For best results with FixSense, we recommend these settings in playwright.config.ts:
retries: 0, // Let FixSense see real failures — retries mask flaky tests
headless: true, // Required for CI (no display server)If you use retries, FixSense will still analyze failures but may miss flaky tests that pass on retry. Setting retries: 0 gives FixSense the most accurate data for flakiness detection.
Step 3: Trigger a CI Run
Once installed, FixSense automatically monitors your CI pipeline. To test it:
- Open a Pull Request with a change that might affect your tests
- Wait for your tests to run in CI
- If any tests fail, FixSense will post an analysis comment on the PR within 30 seconds
Step 4: View Your Dashboard
Visit your FixSense Dashboard to see:
- Total analyses used this month
- Auto-fix usage
- Recent failure analyses
- Failure trends over time
Permissions Explained
| Permission | Why We Need It |
|---|---|
| Contents (Read & Write) | Read test files for context, push auto-fix branches |
| Pull Requests (Read & Write) | Post analysis comments on PRs |
| Actions (Read) | Download CI failure logs |
| Issues (Read & Write) | Create issues for persistent failures |
| Workflows (Read & Write) | Enable auto-fix workflow via dashboard |
| Metadata (Read) | Basic repository information |