npm @alex_neo/playwright-azure-reporter 1.23.0
Release v1.23.0

one hour ago

v1.23.0

Released: 2026-11-17

Highlights

One Playwright run, several test plans (#142, #165)

planId now takes a list of plans, or a function that selects them from the test plans of the project. A test case that is in a regression plan and in a release plan is updated in both by one run; tests whose test cases live in different plans are published by one run.

planId: [4, 12, 15],
// or: the regression plan and every release plan that is running today
planId: ({ plans }) => plans.filter((plan) => plan.id === 4 || plan.name.startsWith('Release ')).map((plan) => plan.id),

A test run belongs to one plan, so one test run is created for every selected plan that has test points of the executed tests. The run ids are exported as AZURE_PW_TEST_RUN_IDS (JSON map plan → run) and AZURE_PW_TEST_RUN_ID_<planId>. isExistingTestRun, testRunADO and rootSuiteId work with a single plan only. Details: Multiple Test Plans.

Test runs in the Tests tab of the pipeline (#163, #171)

The new pipelineAssociation option links every run the reporter creates with the Azure Pipelines build, the pipeline job and a classic release, from the predefined pipeline variables. The results then show up in the Tests tab of the build or release stage, and run tags are accepted.

{ pipelineAssociation: true }

Outside Azure Pipelines it does nothing. Values set in testRunConfig win. If Azure DevOps rejects the association, the run is created without it, so it never prevents reporting. No extra token scope is needed; System.AccessToken works too. If you also publish a JUnit file with PublishTestResults, you can drop it now. Details: Associate Runs with the Pipeline Build.

Why a test got no test point (#164)

"No test points found" now says why: the test case is in no plan, only in other plans, outside rootSuiteId, assigned to other configurations, or dropped by testPointMapper. See the new Troubleshooting guide.

All three were verified on a live Azure DevOps organization.

Behaviour changes

  • Default run name: the leading space is gone, " Playwright Test Run" is now "Playwright Test Run". Update anything that matches runs by name.
  • planId is parsed strictly. A numeric string works (planId: process.env.AZURE_PLAN_ID), but a value like '12abc' now disables reporting with a warning instead of being read as 12.
  • testPointMapper that throws skips only that test instead of disabling reporting for the whole run.
  • More than 1000 test points: Azure DevOps cuts a points query at 1000 without any sign. The reporter now fetches the rest, so test cases that are in many plans or configurations no longer end up with "No test points found" (#103).
  • Summary line counts only results Azure DevOps accepted.

Sharding

If you shard, run the reporter once in the merge-reports job instead of in every shard: one run per plan instead of one per shard and plan. See Sharded Runs.

Publishing

Releases are now published from GitHub Actions with npm trusted publishing (OIDC) and carry a provenance statement.

Features

  • feat(reporter): publish one Playwright run to several test plans (514cff5)
  • feat(reporter): associate created test runs with the Azure Pipelines build (9f74305)
  • feat(reporter): read the Azure Pipelines context for the run association (612f886)
  • feat(reporter): explain why a test got no test point (88f7bc9)
  • feat(reporter): accept planId as a string and parse it strictly (a3f9eff)

Bug Fixes

  • fix(reporter): fetch all test points when a points query hits the Azure DevOps limits (1167418)
  • fix(reporter): skip only the test whose testPointMapper throws (6cbd617)
  • fix(reporter): remove the leading space from default run names (115eacb)
  • fix(reporter): count only accepted results in the summary and print the start line once (b3f0a6d)
  • fix(reporter): address the findings of the live check with several test plans (1a72b24)
  • fix(reporter): adjust the pipeline association to the live spike (59d659b)
  • fix(deps): resolve Dependabot security alerts (833bd4b)

Documentation

  • Multiple test plans, sharded runs, troubleshooting, System.AccessToken setup, pipeline association.

Don't miss a new playwright-azure-reporter release

NewReleases is sending notifications on new releases.