-
## 1. General summary of the issue
An It test looking for a PowerShell module (psm1) file in a PowerShell manifest (psd1) file is failing.
## 2. Describe Your Environment
(Details obtained ma…
ghost updated
3 years ago
-
I currently have custom [Assert-Error](https://bitbucket.org/splatteredbits/blade/src/tip/Blade/Functions/Assert-Error.ps1?at=default&fileviewer=file-view-default) and [Assert-NoError](https://bitbuck…
-
## 1. General summary of the issue
There's this strange thing... I wrote some test code for a script. In the test the script is called correctly but the code after calling the script, the actual test…
-
Hey everyone,
Many thanks for your amazing product! I would like to propose a new feature to Pester
### 1. General summary of the issue
Allow users to specify a custom `$OutputFormat` function …
-
## Question
Pester uses BOM inconsistently in files with UTF8. Only some files, like `Mock.ps1`, `Mock.Tests.ps1` etc. use BOM, while the rest use UTF8 without BOM.
CI failed for PS v3/v4 in #1745…
-
## 1. General summary of the issue
When comparing two arrays with "Should -Be", in the output the arrays are truncated to the first 10 elements, but it isn't obvious this is happening.
## 2. Des…
-
As mentioned in #804 there is no documentation about Should and how it compares arrays. Add it or wait for Should refactoring to add it.
-
`101 | Should -BeIn (1..100)`
prints the following error message:
> Expected collection @(1, 2, 3, 4, 5, 6, 7, 8, 9, 10) to contain 101, but it was not found.
This is misleading since the ex…
-
`Get-ShouldOperator` shows:
```
NAME
Should-Be
```
on the top, and does not show aliases. It would be nice to replace the name section with this:
```
NAME
Be
ALIASES
EQ
…
-
## 1. General summary of the issue
When the Gherkin feature of Pester attempts to find step definitions for the scenarios in feature files, it makes a bad assumption about the possible location(s) …