Skip to content

Record ExpectedTask creation location in console-subscriber tests #461

Open
@hds

Description

@hds

What problem are you trying to solve?

When a test asserts on mulitple expected tasks, it may not be clear which one fails in the case of a failure.

How should the problem be solved?

Record the panic location when creating the ExpectedTask and put #[track_caller] on the constructor.

Metadata

Metadata

Assignees

No one assigned

    Labels

    S-featureSeverity: feature. This is adding a new feature.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions