Pester icon indicating copy to clipboard operation
Pester copied to clipboard

Pester is the ubiquitous test and mock framework for PowerShell.

Results 280 Pester issues
Sort by recently updated
recently updated
newest added

## 1. General summary of the issue The `Get-AzureRmContext` defines a dynamic ValidateSet for the `Name` Parameter, that checks if the given Name is existing on the current Machine. Using...

Mocking

In order to fix `Get-PackageSource` cmdlet, another level of indirection was introduced which broke other things. Original issue and PR: #1308 #1317 Issue it caused and revert PR: #1519 #1528

Mocking

When running in the context of Mock we should collect errors and fail the MockWith or ParameterFilter, instead of writing the errors to the parent It block.

Mocking

## General summary of the issue When mocking `Out-File` and invoking it in code using `Out-File -FilePath $path -Encoding utf8NoBOM -Force;`, Pester produces this error when executing a test: ```...

good first issue
Mocking
Help Wanted

A typical failure from Assert-MockCalled is: "Expected xyz in module abc to be called at least 1 times but was called 0 times" Working from just that sparse information, though,...

Feature
Mocking

## PR Summary Single item arrays are currently printed as single item without type-specific formatting because `Is-Value` expands them. Arrays with a single string or bool (more types?) will not...

## 1. General summary of the issue While testing out new Code Coverage Reporting capability in Azure DevOps with a dummy PowerShell module, I've noticed, that if my module has...

Code coverage

## 1. General summary of the issue ExcludePath only works for files, not directories, even though the description says it should work for directories. ![image](https://user-images.githubusercontent.com/15258962/83038397-c3d9ff80-9ff1-11ea-8d23-4434665f4d90.png) ## 2. Describe Your Environment...

Documentation

> Should we just rename the Id-property to `GroupId` and use a guid to make it more obvious? It's a public property, but I doubt anyone relies on it and...

## PR Summary Result object was printed when run failed because it was sent to standard output, but never reached variable assignment before `Run.Exit` killed the process causing a text...

Bug