Skip to content

Cucumber scenario uid changes with the worker slot and the scenarios selected #576

Open

Description

@vishnuv688

Problem

When the service cannot read a Cucumber scenario's line from WDIO (no pickle uri/line), generateStableUid in packages/service/src/reporter.ts falls back to a hash that includes the worker slot (cid) and WDIO's scenario uid, which is the scenario's position among the pickles of the run (example-${item.uid}).

Neither is a property of the scenario. The same scenario gets a different dashboard uid when it:

  • runs in a different worker slot, or
  • runs in a narrower run (--spec file:line, a tag filter, or a single-scenario rerun from the dashboard), which renumbers the pickles.

The dashboard then lists it as a new row instead of updating the existing one, so Rerun and Preserve & Rerun compare against the wrong row. Plain scenarios reach this fallback (the login-fail.feature scenario in examples/wdio/cucumber does).

Found while working on #575, which removed parent from this hash. cid and the pickle index are still in it.

Proposal

Key the fallback on properties of the scenario only: the feature file path and the scenario's own line, read from the feature file, plus its title. Drop cid and the pickle index.

How we will know it worked

A reporter test feeds the same scenario with different cid values and pickle indexes and gets the same uid; a full run and a single-scenario rerun give the scenario the same row in the dashboard.

Activity

  1. self-assigned this
    on Nov 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions