Skip to content

update test framework and tests to support 4x version of Pester #6064

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
adityapatwardhan merged 8 commits into from
Feb 5, 2018
Merged

update test framework and tests to support 4x version of Pester #6064

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
7d14e24
Test fixes and changes needed to support Pester 4.0.8
JamesWTruher Nov 14, 2017
0bbf9c5
Replace 'Should Contain' with new 'Should FileContentMatch' assertion
JamesWTruher Jan 26, 2018
59c3333
Use the current version of pester and install it in modulesDir
JamesWTruher Jan 26, 2018
69467a4
Simplify logic for relative path test.
JamesWTruher Jan 27, 2018
86bd7d7
In some environments it is possible that computer name is 'localhost'…
JamesWTruher Jan 29, 2018
3f8df89
[feature] Add link for migrating tests from Pester v3 to v4
JamesWTruher Jan 30, 2018
fc368ba
[feature] update invoke-item test to handle the case where multiple n…
JamesWTruher Jan 30, 2018
9cc7e8f
Fix spelling issue with Pester 4x, calling it Pester 4 should be suff…
JamesWTruher Feb 2, 2018
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions build.psm1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -662,7 +662,8 @@ function Restore-PSModuleToBuild

if($CI.IsPresent)
{
Restore-PSPester -Destination $modulesDir
# take the latest version of pester and install it so it may be used
Save-Module -Path $modulesDir -Name Pester
}
}

Expand Down Expand Up @@ -987,7 +988,7 @@ function Start-PSPester {
Write-Warning @"
Pester module not found.
Restore the module to '$Pester' by running:
Restore-PSPester
Save-Module Pester -Path '$binDir/Modules'
"@
return;
}
Expand Down
20 changes: 12 additions & 8 deletions docs/testing-guidelines/WritingPesterTests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,11 @@
### Writing Pester Tests
Note that this document does not replace the documents found in the [Pester](https://github.com/pester/pester "Pester") project. This is just
some quick tips and suggestions for creating Pester tests for this project. The Pester community is vibrant and active, if you have questions
about Pester or creating tests, the [Pester Wiki](https://github.com/pester/pester/wiki) has a lot of great information.
Note that this document does not replace the documents found in the [Pester](https://github.com/pester/pester "Pester") project.
This is just some quick tips and suggestions for creating Pester tests for this project.
The Pester community is vibrant and active, if you have questions about Pester or creating tests, the [Pester Wiki](https://github.com/pester/pester/wiki) has a lot of great information.
As of January 2018, PowerShell Core is using Pester version 4 which has some changes from earlier versions.
See [Migrating from Pester 3 to Pester 4](https://github.com/pester/Pester/wiki/Migrating-from-Pester-3-to-Pester-4) for more information.



When creating tests, keep the following in mind:
* Tests should not be overly complicated and test too many things
Expand All @@ -16,7 +20,7 @@ Here's the simplest of tests
Describe "A variable can be assigned and retrieved" {
It "Create a variable and make sure its value is correct" {
$a = 1
$a | Should be 1
$a | Should Be 1
}
}
```
Expand All @@ -27,7 +31,7 @@ If you need to do type checking, that can be done as well
Describe "One is really one" {
It "Compare 1 to 1" {
$a = 1
$a | Should be 1
$a | Should Be 1
}
It "1 is really an int" {
$i = 1
Expand All @@ -42,7 +46,7 @@ alternatively, you could do the following:
Describe "One is really one" {
It "Compare 1 to 1" {
$a = 1
$a | Should be 1
$a | Should Be 1
}
It "1 is really an int" {
$i = 1
Expand Down Expand Up @@ -136,7 +140,7 @@ $testCases = @(
Describe "A test" {
It "<a> -xor <b> should be <expectedresult>" -testcase $testcases {
param ($a, $b, $ExpectedResult)
$a -xor $b | Should be $ExpectedResult
$a -xor $b | Should Be $ExpectedResult
}
}
```
Expand All @@ -151,7 +155,7 @@ The following example illustrates simple use:
Context "Get-Random is not random" {
Mock Get-Random { return 3 }
It "Get-Random returns 3" {
Get-Random | Should be 3
Get-Random | Should Be 3
}
}
```
Expand Down
4 changes: 2 additions & 2 deletions test/powershell/Modules/Microsoft.PowerShell.Core/Import-Module.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@

It "should only load the specified version" {
Import-Module TestModule -RequiredVersion 1.1
(Get-Module TestModule).Version | Should Be "1.1"
(Get-Module TestModule).Version | Should BeIn "1.1"
Copy link
Member

@SteveL-MSFT SteveL-MSFT Jan 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't BeIn only used for validating if the left side is contained in the collection on the right side? Don't understand why this isn't just Be?

Copy link
Collaborator Author

@JamesWTruher JamesWTruher Jan 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as it turns out, there are multiple loaded modules which are named TestModule, thus a comparison with "Be" fails because it's a collection. I didn't want to rearchitect the tests.

Copy link
Member

@SteveL-MSFT SteveL-MSFT Jan 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Got it. Closed.

}
}

Expand Down Expand Up @@ -192,7 +192,7 @@ Describe "Import-Module should be case insensitive" -Tags 'CI' {
Import-Module testMODULE
$m = Get-Module TESTmodule
$m | Should BeOfType "System.Management.Automation.PSModuleInfo"
$m.Name | Should Be "TESTMODULE"
$m.Name | Should BeIn "TESTMODULE"
Copy link
Member

@SteveL-MSFT SteveL-MSFT Jan 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't BeIn only used for validating if the left side is contained in the collection on the right side? Don't understand why this isn't just Be?

Copy link
Collaborator Author

@JamesWTruher JamesWTruher Jan 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above

Copy link
Member

@SteveL-MSFT SteveL-MSFT Jan 30, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Closed

mytest | Should BeExactly "hello"
Remove-Module TestModule
Get-Module tESTmODULE | Should BeNullOrEmpty
Expand Down
2 changes: 1 addition & 1 deletion test/powershell/Modules/Microsoft.PowerShell.Core/Out-Default.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ Describe "Out-Default Tests" -tag CI {
"@

& $powershell -noprofile -command $script | Should BeExactly 'bye'
"TestDrive:\transcript.txt" | Should Contain 'hello'
"TestDrive:\transcript.txt" | Should FileContentMatch 'hello'
}

It "Out-Default reverts transcription state when used more than once in a pipeline" {
Expand Down
2 changes: 1 addition & 1 deletion test/powershell/Modules/Microsoft.PowerShell.Management/Clear-Content.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,7 +64,7 @@ Describe "Clear-Content cmdlet tests" -Tags "CI" {
# we could suppress the WhatIf output here if we use the testhost, but it's not necessary
It "The filesystem provider supports should process" -skip:(!$IsWindows) {
clear-content TESTDRIVE:\$file2 -WhatIf
"TESTDRIVE:\$file2" | should contain "This is content"
"TESTDRIVE:\$file2" | should FileContentMatch "This is content"
}

It "The filesystem provider should support ShouldProcess (reference ProviderSupportsShouldProcess member)" {
Expand Down
5 changes: 2 additions & 3 deletions test/powershell/Modules/Microsoft.PowerShell.Management/FileSystem.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -378,8 +378,7 @@ Describe "Handling of globbing patterns" -Tags "CI" {
BeforeEach {
$file = New-Item -ItemType File -Path $filePath -Force
}
AfterEach
{
AfterEach {
Remove-Item -Force -Recurse -Path $dirPath -ErrorAction SilentlyContinue
Remove-Item -Force -LiteralPath $newPath -ErrorAction SilentlyContinue
}
Expand Down Expand Up @@ -1392,7 +1391,7 @@ Describe "UNC paths" -Tags 'CI' {
$testPath = Join-Path "\\localhost" $systemDrive
& $cmdlet $testPath
Get-Location | Should BeExactly "Microsoft.PowerShell.Core\FileSystem::$testPath"
$children = { Get-ChildItem -ErrorAction Stop } | Should Not Throw
$children = Get-ChildItem -ErrorAction Stop
$children.Count | Should BeGreaterThan 0
}
finally {
Expand Down
14 changes: 7 additions & 7 deletions test/powershell/Modules/Microsoft.PowerShell.Management/Move-Item.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ Describe "Move-Item tests" -Tag "CI" {
Move-Item $source $target
test-path $source | Should be $false
test-path $target | Should be $true
"$target" | Should ContainExactly "This is content"
"$target" | Should FileContentMatchExactly "This is content"
}

Context "Move-Item with filters" {
Expand Down Expand Up @@ -49,7 +49,7 @@ Describe "Move-Item tests" -Tag "CI" {
$newBarPath | Should Exist
$booPath | Should Exist
$fooPath | Should Exist
$newBarPath | Should ContainExactly $barContent
$newBarPath | Should FileContentMatchExactly $barContent
}
It "Can move to different directory, filtered with -Exclude" {
Move-Item -Path $filePath -Destination $moveToPath -Exclude "b*" -ErrorVariable e -ErrorAction SilentlyContinue
Expand All @@ -58,7 +58,7 @@ Describe "Move-Item tests" -Tag "CI" {
$newFooPath | Should Exist
$booPath | Should Exist
$barPath | Should Exist
$newFooPath | Should ContainExactly $fooContent
$newFooPath | Should FileContentMatchExactly $fooContent
}
It "Can move to different directory, filtered with -Filter" {
Move-Item -Path $filePath -Destination $moveToPath -Filter "bo*" -ErrorVariable e -ErrorAction SilentlyContinue
Expand All @@ -67,7 +67,7 @@ Describe "Move-Item tests" -Tag "CI" {
$newBooPath | Should Exist
$barPath | Should Exist
$fooPath | Should Exist
$newBooPath | Should ContainExactly $booContent
$newBooPath | Should FileContentMatchExactly $booContent
}

It "Can rename via move, filtered with -Include" {
Expand All @@ -77,7 +77,7 @@ Describe "Move-Item tests" -Tag "CI" {
$barPath | Should Not Exist
$booPath | Should Exist
$fooPath | Should Exist
$renameToPath | Should ContainExactly $barContent
$renameToPath | Should FileContentMatchExactly $barContent
}
It "Can rename via move, filtered with -Exclude" {
Move-Item -Path $filePath -Destination $renameToPath -Exclude "b*" -ErrorVariable e -ErrorAction SilentlyContinue
Expand All @@ -86,7 +86,7 @@ Describe "Move-Item tests" -Tag "CI" {
$fooPath | Should Not Exist
$booPath | Should Exist
$barPath | Should Exist
$renameToPath | Should ContainExactly $fooContent
$renameToPath | Should FileContentMatchExactly $fooContent
}
It "Can rename via move, filtered with -Filter" {
Move-Item -Path $filePath -Destination $renameToPath -Filter "bo*" -ErrorVariable e -ErrorAction SilentlyContinue
Expand All @@ -95,7 +95,7 @@ Describe "Move-Item tests" -Tag "CI" {
$booPath | Should Not Exist
$fooPath | Should Exist
$barPath | Should Exist
$renameToPath | Should ContainExactly $booContent
$renameToPath | Should FileContentMatchExactly $booContent
}
}
}
2 changes: 1 addition & 1 deletion test/powershell/Modules/Microsoft.PowerShell.Management/Rename-Item.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,6 @@ Describe "Rename-Item tests" -Tag "CI" {
Rename-Item $source $target
test-path $source | Should be $false
test-path $target | Should be $true
"$target" | Should ContainExactly "This is content"
"$target" | Should FileContentMatchExactly "This is content"
}
}
4 changes: 2 additions & 2 deletions test/powershell/Modules/Microsoft.PowerShell.Management/TimeZone.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,15 +63,15 @@ Describe "Get-Timezone test cases" -Tags "CI" {
It "Call with ListAvailable switch returns a list containing TimeZoneInfo.Local" {
$observedIdList = Get-TimeZone -ListAvailable | Select-Object -ExpandProperty BaseUtcOffset
$oneExpectedOffset = ([System.TimeZoneInfo]::Local).BaseUtcOffset
$observedIdList -eq $oneExpectedOffset | Should Be $oneExpectedOffset
$oneExpectedOffset | Should BeIn $observedIdList
}

## The local time zone could be set to UTC or GMT*. In this case, the .NET API returns the region ID
## and not UTC. To avoid a string matching error, we compare the BaseUtcOffset instead.
It "Call with ListAvailable switch returns a list containing one returned by Get-TimeZone" {
$observedIdList = Get-TimeZone -ListAvailable | Select-Object -ExpandProperty BaseUtcOffset
$oneExpectedOffset = (Get-TimeZone).BaseUtcOffset
$observedIdList -eq $oneExpectedOffset | Should Be $oneExpectedOffset
$oneExpectedOffset | Should BeIn $observedIdList
}

It "Call Get-TimeZone using ID param and single item" {
Expand Down
5 changes: 3 additions & 2 deletions test/powershell/Modules/Microsoft.PowerShell.Utility/ConvertFrom-StringData.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,8 +65,9 @@ bazz = 2
It "Should work for multiple lines" {
{ ConvertFrom-StringData -StringData $sampleData } | Should Not Throw

$(ConvertFrom-StringData -StringData $sampleData).Keys | Should Be "foo", "bar", "bazz"
# keys are not order guaranteed
$(ConvertFrom-StringData -StringData $sampleData).Keys | Should BeIn @("foo", "bar", "bazz")

$(ConvertFrom-StringData -StringData $sampleData).Values | Should Be "0","1","2"
$(ConvertFrom-StringData -StringData $sampleData).Values | Should BeIn @("0","1","2")
}
}
4 changes: 3 additions & 1 deletion test/powershell/Modules/Microsoft.PowerShell.Utility/ConvertTo-Html.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -138,7 +138,9 @@ After the object

It "Test ConvertTo-HTML meta with invalid properties should throw warning" {
$parms = @{"authors"="John Doe";"keywords"="PowerShell,PSv6"}
($customObject | ConvertTo-HTML -Meta $parms 3>&1) -match $parms["authors"] | Should Be $true
# make this a string, rather than an array of string so match will behave
[string]$observedProperties = $customObject | ConvertTo-HTML -Meta $parms 3>&1
$observedProperties | Should Match $parms["authors"]
}

It "Test ConvertTo-HTML charset"{
Expand Down
36 changes: 18 additions & 18 deletions test/powershell/Modules/Microsoft.PowerShell.Utility/Export-Alias.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,46 +63,46 @@ Describe "Export-Alias DRT Unit Tests" -Tags "CI" {

It "Export-Alias for Default"{
Export-Alias $fulltestpath abcd01 -passthru
$fulltestpath| Should ContainExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should FileContentMatchExactly '"abcd01","efgh01","","None"'
}

It "Export-Alias As CSV"{
Export-Alias $fulltestpath abcd01 -As CSV -passthru
$fulltestpath| Should ContainExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should FileContentMatchExactly '"abcd01","efgh01","","None"'
}

It "Export-Alias As CSV With Description"{
Export-Alias $fulltestpath abcd01 -As CSV -description "My Aliases" -passthru
$fulltestpath| Should ContainExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should ContainExactly "My Aliases"
$fulltestpath| Should FileContentMatchExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should FileContentMatchExactly "My Aliases"
}

It "Export-Alias As CSV With Multiline Description"{
Export-Alias $fulltestpath abcd01 -As CSV -description "My Aliases\nYour Aliases\nEveryones Aliases" -passthru
$fulltestpath| Should ContainExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should ContainExactly "My Aliases"
$fulltestpath| Should ContainExactly "Your Aliases"
$fulltestpath| Should ContainExactly "Everyones Aliases"
$fulltestpath| Should FileContentMatchExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should FileContentMatchExactly "My Aliases"
$fulltestpath| Should FileContentMatchExactly "Your Aliases"
$fulltestpath| Should FileContentMatchExactly "Everyones Aliases"
}

It "Export-Alias As Script"{
Export-Alias $fulltestpath abcd01 -As Script -passthru
$fulltestpath| Should ContainExactly 'set-alias -Name:"abcd01" -Value:"efgh01" -Description:"" -Option:"None"'
$fulltestpath| Should FileContentMatchExactly 'set-alias -Name:"abcd01" -Value:"efgh01" -Description:"" -Option:"None"'
}

It "Export-Alias As Script With Multiline Description"{
Export-Alias $fulltestpath abcd01 -As Script -description "My Aliases\nYour Aliases\nEveryones Aliases" -passthru
$fulltestpath| Should ContainExactly 'set-alias -Name:"abcd01" -Value:"efgh01" -Description:"" -Option:"None"'
$fulltestpath| Should ContainExactly "My Aliases"
$fulltestpath| Should ContainExactly "Your Aliases"
$fulltestpath| Should ContainExactly "Everyones Aliases"
$fulltestpath| Should FileContentMatchExactly 'set-alias -Name:"abcd01" -Value:"efgh01" -Description:"" -Option:"None"'
$fulltestpath| Should FileContentMatchExactly "My Aliases"
$fulltestpath| Should FileContentMatchExactly "Your Aliases"
$fulltestpath| Should FileContentMatchExactly "Everyones Aliases"
}

It "Export-Alias for Force Test"{
Export-Alias $fulltestpath abcd01
Export-Alias $fulltestpath abcd02 -force
$fulltestpath| Should Not ContainExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should ContainExactly '"abcd02","efgh02","","None"'
$fulltestpath| Should Not FileContentMatchExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should FileContentMatchExactly '"abcd02","efgh02","","None"'
}

It "Export-Alias for Force ReadOnly Test" {
Expand All @@ -124,9 +124,9 @@ Describe "Export-Alias DRT Unit Tests" -Tags "CI" {
$_.FullyQualifiedErrorId | Should be "FileOpenFailure,Microsoft.PowerShell.Commands.ExportAliasCommand"
}
Export-Alias $fulltestpath abcd03 -force
$fulltestpath| Should Not ContainExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should Not ContainExactly '"abcd02","efgh02","","None"'
$fulltestpath| Should ContainExactly '"abcd03","efgh03","","None"'
$fulltestpath| Should Not FileContentMatchExactly '"abcd01","efgh01","","None"'
$fulltestpath| Should Not FileContentMatchExactly '"abcd02","efgh02","","None"'
$fulltestpath| Should FileContentMatchExactly '"abcd03","efgh03","","None"'

if ( $IsWindows )
{
Expand Down
3 changes: 2 additions & 1 deletion test/powershell/Modules/Microsoft.PowerShell.Utility/Get-Variable.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,7 +145,8 @@ Describe "Get-Variable" -Tags "CI" {
It "Should not be able to clear a global scope variable using the local switch" {
New-Variable globalVar -Value 1 -Scope global -Force

Get-Variable -Name globalVar -Scope local -ErrorAction SilentlyContinue | Should Throw
Get-Variable -Name globalVar -Scope local -ErrorAction SilentlyContinue -ErrorVariable removeGlobalAsLocal
$removeGlobalAsLocal.FullyQualifiedErrorId | Should Be "VariableNotFound,Microsoft.PowerShell.Commands.GetVariableCommand"
}

It "Should be able to get a global variable when there's one in the script scope" {
Expand Down
3 changes: 2 additions & 1 deletion test/powershell/Modules/Microsoft.PowerShell.Utility/Invoke-Item.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,7 +67,8 @@ Describe "Invoke-Item basic tests" -Tags "Feature" {
Get-Process -Name $notepadProcessName | Stop-Process -Force
Invoke-Item -Path $notepad
$notepadProcess = Get-Process -Name $notepadProcessName
$notepadProcess.Name | Should Be $notepadProcessName
# we need BeIn because multiple notepad processes could be running
$notepadProcess.Name | Should BeIn $notepadProcessName
Copy link
Collaborator

@iSazonov iSazonov Feb 3, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In line 67 we kill all notepad processes.

Copy link
Collaborator Author

@JamesWTruher JamesWTruher Feb 5, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in CI this is probably ok - on a dev box, not so much - the fix for this should be part of the generalized test review

Stop-Process -InputObject $notepadProcess
}
} else {
Expand Down
5 changes: 3 additions & 2 deletions test/powershell/Modules/Microsoft.PowerShell.Utility/New-Variable.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,8 +85,9 @@ Describe "New-Variable" -Tags "CI" {
}

It "Should not be able to set the name of a new variable to that of an old variable within same scope when the Force switch is missing" {
New-Variable var1
(New-Variable var1 -ErrorAction SilentlyContinue) | Should Throw
New-Variable var1
New-Variable var1 -ErrorAction SilentlyContinue -ErrorVariable newWhenExists
$newWhenExists.FullyQualifiedErrorId | Should Be "VariableAlreadyExists,Microsoft.PowerShell.Commands.NewVariableCommand"
}

It "Should change the value of an already existing variable using the Force switch" {
Expand Down
4 changes: 2 additions & 2 deletions test/powershell/Modules/Microsoft.PowerShell.Utility/Out-File.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,8 +11,8 @@ Describe "Out-File DRT Unit Tests" -Tags "CI" {
$tempFile = Join-Path -Path $TestDrive -ChildPath "outfileAppendTest.txt"
{ 'This is first line.' | out-file $tempFile } | Should Not Throw
{ 'This is second line.' | out-file -append $tempFile } | Should Not Throw
$tempFile |Should Contain "first"
$tempFile |Should Contain "second"
$tempFile |Should FileContentMatch "first"
$tempFile |Should FileContentMatch "second"
Remove-Item $tempFile -Force
}
}
Expand Down
8 changes: 4 additions & 4 deletions test/powershell/Modules/Microsoft.PowerShell.Utility/Remove-Event.Tests.ps1
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,27 +12,27 @@ Describe "Remove-Event" -Tags "CI" {

It "Should remove an event given a sourceidentifier" {
{ Remove-Event -sourceidentifier PesterTimer }
{ Get-Event -ErrorAction SilentlyContinue | Should Not Contain PesterTimer }
{ Get-Event -ErrorAction SilentlyContinue | Should Not FileMatchContent PesterTimer }
}

It "Should remove an event given an event identifier" {
{ $events = Get-Event -sourceidentifier PesterTimer }
{ $events = $events.EventIdentifier }
{ Remove-Event -EventIdentifier $events }
{ $events = Get-Event -ErrorAction SilentlyContinue}
{ $events.SourceIdentifier | Should Not Contain "PesterTimer" }
{ $events.SourceIdentifier | Should Not FileMatchContent "PesterTimer" }
}

It "Should be able to remove an event given a pipe from Get-Event" {
{ Get-Event -sourceidentifier PesterTimer | Remove-Event }
{ Get-Event -ErrorAction SilentlyContinue | Should Not Contain "PesterTimer" }
{ Get-Event -ErrorAction SilentlyContinue | Should Not FileMatchContent "PesterTimer" }

}

It "Should NOT remove an event given the whatif flag" {
{ Remove-Event -sourceidentifier PesterTimer -whatif }
{ $events = Get-Event }
{ $events.SourceIdentifier | Should Contain "PesterTimer" }
{ $events.SourceIdentifier | Should FileContentMatch "PesterTimer" }
}
}
}
Loading