Quick Reference
| Upload Option | What It Includes |
|---|---|
| JSON only | Test results, no artifacts |
| Image Attachments | Screenshots |
| Video Attachments | Video recordings |
| Trace Files | Playwright traces |
| Full JSON Bundle | Everything |
Prerequisites
Before you start:- A TeamCity project with Playwright tests
- Playwright configured to generate reports (default output:
./playwright-report) - A TestDino account with a project API key
Need an API key? Go to your TestDino project, open Settings → API Keys, and generate one.
Installation Methods
- Install from Administration (Global)
- Install While Adding a Build Step (Quick)
This installs the plugin for all projects in your TeamCity instance.
- Go to TeamCity Administration
- Open Plugins
- Click Browse Plugins (JetBrains Marketplace)
- Search for “TestDino”
- Click Install
- Restart TeamCity if prompted
Adding the Build Step
1
Open Build Steps
- Go to your TeamCity Build Configuration
- Click Build Steps
- Click Add build step
2
Select the Runner
From the Runner Type dropdown, select TestDino - Upload Playwright Report.The recipe configuration form appears.
3
Configure and Save
Fill in the fields based on your setup (see Configuration Reference below), then click Save.
Configuration Reference
| Field | Description | Default | When to Use |
|---|---|---|---|
| Report Directory | Folder containing your Playwright reports (JSON + HTML + artifacts) | ./playwright-report | Change this if your reports live somewhere else |
| TestDino API Token | Your project API key for authentication. Can also be set as TESTDINO_TOKEN environment variable | Required | Always needed for secure uploads |
| HTML Reports | Include the interactive HTML report | Checkbox | Turn on when you want the full Playwright report UI in TestDino |
| Image Attachments | Include screenshots captured during test runs | Checkbox | Helpful for visual debugging and failure analysis |
| Video Attachments | Include video recordings of test executions | Checkbox | Great for debugging flaky tests or complex UI flows |
| Trace Files | Include Playwright trace archives | Checkbox | Use when you need step-by-step debugging with the trace viewer |
| File Attachments | Include extra files like .md, .pdf, .log, or .txt | Checkbox | Useful if your tests generate logs or documentation |
| Full JSON Bundle | Upload everything: JSON + HTML + images + videos + traces + files | Checkbox | Best option for complete analytics in TestDino |
| Custom JSON Report Path | Override the default JSON file location | Empty | Set this if your JSON report has a non-standard path |
| Custom HTML Report Path | Override the default HTML report folder | Empty | Set this if your HTML output is in a custom folder |
| Custom Trace Directory | Override the default trace folder | Empty | Set this if traces are stored separately |
| Verbose Logging | Show detailed debug output in build logs | Checkbox | Turn on when troubleshooting upload issues |
Configuration Examples
- Basic Setup (JSON Only)
- Full Analytics Setup
- Custom Paths Setup
- Screenshots and Videos Only
Upload just the JSON report for quick analytics:
| Field | Value |
|---|---|
| Report Directory | ./playwright-report |
| TestDino API Token | your-api-key |
| All checkboxes | Unchecked |
Using Environment Variables
Instead of entering your API token directly in the build step, use an environment variable for better security.1
Setting the Token
- Go to your TeamCity Build Configuration
- Click Parameters
- Add a new parameter:
- Name:
env.TESTDINO_TOKEN - Value: Your API key
- Type: Password
- Name:
TESTDINO_TOKEN from the environment. This keeps your key out of build logs and makes rotation easier.2
Benefits
- Token stays hidden in build logs
- Easy to rotate without editing build steps
- Shareable build configurations without exposing secrets
Running Your Build
With the recipe configured:- Your Playwright tests run as usual
- Reports and artifacts are generated
- The TestDino recipe collects everything
- Files are uploaded to your TestDino project
- A confirmation message and link appear in the build log
Viewing Results in TestDino
After the upload:
- Open the link from your build log, or go to your TestDino project
- Click Test Runs in the sidebar
- Find your latest run with commit message, branch, and test counts
- Click the run to see the full breakdown
- View AI-powered failure analysis
- Check screenshots, videos, and traces
- See flaky test patterns
- Track trends over time
- Create Jira, Linear, or Asana tickets from failures
Troubleshooting
1. Upload Fails with Authentication Error
1. Upload Fails with Authentication Error
Check your API token:
- Verify the token is correct and hasn’t expired
- Confirm the token belongs to the right TestDino project
- Make sure you’ve entered it in the recipe or set
TESTDINO_TOKENin the environment
2. Report Directory Not Found
2. Report Directory Not Found
Verify your paths:
- Check that your Playwright tests actually ran and generated output
- Confirm the path matches your
playwright.config.jssettings - Try using an absolute path if relative paths aren’t working
3. Upload Succeeds, but Run Doesn't Appear
3. Upload Succeeds, but Run Doesn't Appear
Wait and refresh:
- Uploads can take a few seconds to process
- Check the build log for error messages
- Verify your API token has access to the project
- Click the Sync button in the TestDino Test Runs view
4. Missing Artifacts (Screenshots, Videos, Traces)
4. Missing Artifacts (Screenshots, Videos, Traces)
Enable the right checkboxes:
- Screenshots → Image Attachments
- Videos → Video Attachments
- Traces → Trace Files
5. Build Step Runs Before Tests Finish
5. Build Step Runs Before Tests Finish
Reorder your build steps:
- The TestDino step must run after your Playwright test step
- Drag and drop to reorder in the Build Steps list
6. Need Detailed Logs?
6. Need Detailed Logs?
Turn on Verbose Logging in the recipe settings. This adds extra output to your build log that helps pinpoint where things go wrong.
Best Practices
Keep Your API Token Secure
Keep Your API Token Secure
- Store the token in TeamCity parameters with password type
- Avoid pasting tokens directly in build step fields
- Rotate tokens periodically
Upload What You Need
Upload What You Need
- For quick feedback, JSON-only is fastest
- For debugging failures, add screenshots and traces
- For full analysis, use the Full JSON Bundle option
Run TestDino After Tests Complete
Run TestDino After Tests Complete
Make sure the TestDino step runs after your Playwright tests finish. Consider setting the step to run “Even if build steps fail” so you can see failures in TestDino even when tests don’t pass.
Match Your Report Paths
Match Your Report Paths
If you customize Playwright’s output directories in
playwright.config.js, update the recipe’s custom path fields to match.Use Verbose Logging During Setup
Use Verbose Logging During Setup
Turn on verbose logging when first configuring the recipe. Once everything works, you can turn it off to keep build logs clean.
Related Documentation
TeamCity Integration Overview
Learn about TestDino’s TeamCity integration features and capabilities
Getting Started
New to TestDino? Start here for a complete introduction
API Keys
Create upload tokens
Test Runs
Explore how to view and analyze your test runs in the platform
AI Insights
Discover AI-powered failure analysis and test intelligence