Skip to content

Review of examples for Should need to be done due to changed syntax #875

@it-praktyk

Description

@it-praktyk

The quote from incoming Pester v. 4.0.7 RTM

New assertion syntax with assertions as parameters to Should, that allows richer assertion vocabulary. Instead of Should Not Be 10 you should write Should -Not -Be 10

A documentation of project needs to be reviewed and aligned to address that preferred syntax.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions