-
## 1. Provide a general summary of the issue in the Title above
`(Get-Item 'TestDrive:').FullName` resolves to something like `/tmp/81aefdf3-1fb6-40c6-9ec6-01939211013c` on macOS, but its realpath …
-
In the pull request #959 new assertions were added.
Quotation from the pull request description
> Add -Because parameters to all assertions Fixes #312
> Add -BeLessOrEqual and -BeGreaterOrEqual…
-
### Question
I'm trying to create a Share extension that has access to my host application's database. The problem is that users already have the SQLite file created and populated. I know the path…
-
I think it would be awesome if we could provide a new syntax word which would map roughly to the syntax of Where-Object such that all of the PowerShell operators would work for assertions.
The logica…
-
#### Details of the scenario you tried and the problem that is occurring
This appears to be similar to #457. This test broken sometime between PR #445 and #447, although no relevant code has changed …
-
In Pester 3.x I frequently used the following pattern with `Assert-MockCalled`:
```powershell
Describe 'System under test' {
It 'Does something useful' {
Mock MockedCommand {}
…
-
As I understand it, using Pester 4 the better practice is to use named parameters with `Should` to compose assert statements. The following is an example of such use:
```PowerShell
$r | Should -b…
alx9r updated
5 years ago
-
I would like to propose an alternative method of making testcases parameterizes (or: 'data driven'):
A test script written as follows:
foreach($describe in (1..2)) {
Describe "Dy…
-
When using parameterized tests, the tests get executed (with missing parameter data) when the testcases are empty or $null
Describe 'Defect: Empty Test Set results in executing tests.' {
…
-
## General summary of the issue
I'm looking for an easier way to write unit tests for tests, both positive and negative tests, as well as ensuring tests are skipped or marked as inconclusive when …