Playwright Reporting with TeamCity

This guide walks through the complete setup of the TestDino TeamCity Recipe, including installation methods, configuration options, examples, and troubleshooting.

Quick Reference

The TestDino TeamCity Recipe uploads Playwright results after each build. This table shows what artifacts each option includes.

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

A TestDino account with a project created
A TestDino API key (Generate API Keys)
A TeamCity project with Playwright tests
Playwright configured with JSON and HTML reporters in playwright.config.js:

playwright.config.js

// ...existing config

reporter: [
  ['html', { outputDir: './playwright-report' }],  // Optional
  ['json', { outputFile: './playwright-report/report.json' }],  // ✅ Required
]

TipWant to get started quickly? Clone the TestDino Example Repository. It includes sample tests and ready-to-use CI configs.

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

Best for administrators who want the recipe available across all projects.

Adding the Build Step

Open Build Steps

Go to your TeamCity Build Configuration
Click Build Steps
Click Add build step

Select the Runner

From the Runner Type dropdown, select TestDino - Upload Playwright Report.The recipe configuration form appears. Select TestDino runner in TeamCity

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 only the JSON report for quick analytics:

Field	Value
Report Directory	`./playwright-report`
TestDino API Token	`your-api-key`
All checkboxes	Unchecked

Upload everything for complete debugging capabilities:

Field	Value
Report Directory	`./playwright-report`
TestDino API Token	`your-api-key`
Full JSON Bundle	Checked

When your reports use non-standard locations:

Field	Value
Report Directory	`./test-output`
TestDino API Token	`your-api-key`
Custom JSON Report Path	`./test-output/results/report.json`
Custom HTML Report Path	`./test-output/html-report`
Custom Trace Directory	`./test-output/traces`
HTML Reports	Checked
Trace Files	Checked

When you want visual artifacts without traces:

Field	Value
Report Directory	`./playwright-report`
TestDino API Token	`your-api-key`
HTML Reports	Checked
Image Attachments	Checked
Video Attachments	Checked

Using Environment Variables

Instead of entering your API token directly in the build step, use an environment variable for better security.

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

The recipe automatically reads TESTDINO_TOKEN from the environment. This keeps your key out of build logs and makes updates easier.

Benefits

Token stays hidden in build logs
Easy to update 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

TipClick the link to view your test run in TestDino.

Troubleshooting

1. Upload Fails with Authentication Error

Check your API token:

Verify the token is correct and hasn’t expired
Confirm the token has access to the right TestDino project
Make sure you’ve entered it in the recipe or set TESTDINO_TOKEN in the environment

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.js settings
Try using an absolute path if relative paths aren’t working

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)

Enable the right checkboxes:

Screenshots → Image Attachments
Videos → Video Attachments
Traces → Trace Files

Or enable Full JSON Bundle to upload everything at once.

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?

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

Store the token in TeamCity parameters with password type
Avoid pasting tokens directly in build step fields
Replace tokens when they expire or if exposure is suspected

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

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

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

Turn on verbose logging when first configuring the recipe. Once everything works, you can turn it off to keep build logs clean.

CI Optimization

Reduce CI time with smart reruns

Environment Mapping

Route test results to Dev, Staging, or Production by branch

Integrations

Connect Slack, Jira, Linear, Asana, and more

TestDino MCP

Access test results and fix issues with AI agents

Getting Started

Installation & Setup

AI & MCP

Guides

Project

Test Management

Organization

Integrations

Data Privacy

Resources

Quick Reference

Prerequisites

Installation Methods

Adding the Build Step

Configuration Reference

Configuration Examples

Using Environment Variables

Running Your Build

Troubleshooting

Best Practices

CI Optimization

Environment Mapping

Integrations

TestDino MCP

​Quick Reference

​Prerequisites

​Installation Methods

​Adding the Build Step

​Configuration Reference

​Configuration Examples

​Using Environment Variables

​Running Your Build

​Troubleshooting

​Best Practices

​Related

CI Optimization

Environment Mapping

Integrations

TestDino MCP

Quick Reference

Prerequisites

Installation Methods

Adding the Build Step

Configuration Reference

Configuration Examples

Using Environment Variables

Running Your Build

Troubleshooting

Best Practices

Related