Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Pester testing guideline for tests against thrown errors #4635

Copy link
Copy link
Closed
Closed
Pester testing guideline for tests against thrown errors#4635
Copy link
Assignees
SteveL-MSFT
Labels
Area-Maintainers-Documentationspecific to documentation in this repospecific to documentation in this repoResolution-FixedThe issue is fixed.The issue is fixed.
@bergmeister

Description

@bergmeister
bergmeister
opened on Aug 21, 2017
Issue body actions

As part of PR 4612, it was found that the current guideline here recommends this approach

It "Get-Item on a nonexisting file should have error PathNotFound" {
    try
    {
        get-item "ThisFileCannotPossiblyExist" -ErrorAction Stop
        throw "No Exception!"
    }
    catch
    {
        $_.FullyQualifiedErrorId | should be "PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand"
    }
}

However, @iSazonov suggests here that the guideline should be updated to this pattern:

{ get-item  "ThisFileCannotPossiblyExist" -ErrorAction Stop } | ShouldBeErrorId "PathNotFound,Microsoft.PowerShell.Commands.GetItemCommand"
Reactions are currently unavailable

Metadata

Metadata

Assignees

Labels

Area-Maintainers-Documentationspecific to documentation in this repospecific to documentation in this repoResolution-FixedThe issue is fixed.The issue is fixed.

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions
    Morty Proxy This is a proxified and sanitized view of the page, visit original site.