Skip to content

[Requirement]: RUNNING telemetry records from a wait with on-change emission #157

Open

Description

@hln33

Operation / suite

New operation (describe below): telemetry

Behavior to cover

An execution with a wait, with the telemetry plugin configured to emit on change. The suite receives one or more RUNNING records before the terminal SUCCEEDED record.

Why it matters

telemetry-1 covers only the terminal record. RUNNING records exercise record ordering, record count, and the in-progress operation state.

Expected cross-SDK behavior

The same ordered list of records in every SDK. The requirement YAML format from #144 already supports an ordered list of expected records.

Follow-up from #144. Review: #144 (review). Tracking issue: #63.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions