Skip to content

Add a mechanism by which a performable may be excluded from the report #362

@craigfowler

Description

@craigfowler

Very rarely, some performables don't belong in the report because they represent background noise. An example of this is CSF.Screenplay.Selenium.Tasks.BeginCollectingLogsWithJavaScriptIfApplicable. When it appears in logs it's often irrelevant because all it does is choose the next performable (or whether to execute a performable at all).

What I'm thinking of here is to use an attribute such as [ExcludeFromReport] upon the performable. If a performable with this attribute is reported-upon, it's simply skipped and not added to the report, as it if did not occur.

Metadata

Metadata

Assignees

No one assigned

    Labels

    reportsIssues which relate to Screenplay reports
    No fields configured for Feature.

    Projects

    Status
    Todo

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions