@testdino/playwright, which sends results as tests run. The CircleCI Orb and TeamCity guides upload results after the build instead.
Each provider guide includes a working config and troubleshooting, and every guide except TeamCity covers sharded or parallel jobs. Start with the GitHub Actions AI prompt if you use an agent, or pick your provider below.
Use the TestDino Example Repository as a reference for pipeline configuration and project structure.
Cloud CI
GitHub Actions
GitLab
Azure DevOps
AWS CodeBuild
Bitbucket Pipelines
CircleCI Orb
CircleCI CLI
Buildkite
Self-Hosted CI
Jenkins
TeamCity
Harness
Build Systems
Running a monorepo? The Nx guide covers streaming everye2e target to one grouped run.
Jobs that run different commands rather than the same sharded one? Split mode merges hand-partitioned jobs into a single test run.
One test run or several
Eachtdpw test command reports its own test run. Jobs join into one test run only as shards with the same --ci-run-id, split jobs with the same --split-id, or machines in one swarm. A pipeline that runs smoke tests and then the full suite as 2 commands reports 2 test runs.
Each test run is reported on its own:
Keep a suite in one test run when one check should judge all of it. A 90% pass rate applied to each half is not the same as 90% across the whole suite, and a mandatory tag whose tests ran in the other test run shows under Mandatory Tags Not Found. Use several test runs when a part, such as smoke tests, should pass, fail, and notify on its own.
Related
Environment Mapping
Map Git branches to TestDino environments
CI Optimization
Cut CI time and cost after you connect
Troubleshooting
Fix a failed connection or status check