dot loading scripts like that does not work, since parameters must be specified
Instead of dot loading the ps1 once and then calling the underlying script, I just call the script for each test case
Get-PSDrive : Cannot find drive. A drive with the name 'TestDrive' does not exist.
At /usr/local/microsoft/powershell/6.0.0-beta.9/Modules/Pester/4.0.8/Functions/TestDrive.ps1:36 char:14
+ $Path = (& $SafeCommands['Get-PSDrive'] -Name TestDrive).Root
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (TestDrive:String) [Get-PSDrive], DriveNotFoundException
+ FullyQualifiedErrorId : GetLocationNoMatchingDrive,Microsoft.PowerShell.Commands.GetPSDriveCommand
[-] Error occurred in Describe block 1.3s
ParameterBindingValidationException: Cannot bind argument to parameter 'Path' because it is null.
at Clear-TestDrive, /usr/local/microsoft/powershell/6.0.0-beta.9/Modules/Pester/4.0.8/Functions/TestDrive.ps1: line 37
at DescribeImpl, /usr/local/microsoft/powershell/6.0.0-beta.9/Modules/Pester/4.0.8/Functions/Describe.ps1: line 175
at Describe, /usr/local/microsoft/powershell/6.0.0-beta.9/Modules/Pester/4.0.8/Functions/Describe.ps1: line 84
at <ScriptBlock>, /Users/felix/git/ps-nvmw/nvm.Tests.ps1: line 3
at <ScriptBlock>, /usr/local/microsoft/powershell/6.0.0-beta.9/Modules/Pester/4.0.8/Pester.psm1: line 802
at Invoke-Pester<End>, /usr/local/microsoft/powershell/6.0.0-beta.9/Modules/Pester/4.0.8/Pester.psm1: line 817
at <ScriptBlock>, <No file>: line 1
appreciate your help!
Pester looks awesome, can’t believe PowerShell has a BDD-style testing framework better than most non-scripting languages
The error is raised inside Pester
Hi All, I am looking for feedback on a VS extension for Pester.
It is located here:
https://marketplace.visualstudio.com/items?itemName=Jonkers.PowershellPesterTestrunner
The current version has a Test Toolwindow, a Coverage Toolwindow and shows the line hits in misses in the editor.
Any comments and suggestions are appreciated.
@felixfbecker thought so, saw your comment before, but just wanted to confirm with you :)
currently trying to get codecov working
Basically, I'm getting odd behavior when I'm trying to assert that an array is either Empty/Null or NOT empty/null
https://pastebin.com/wTAt3rCq
as an example, see that code.
as an example, see that code.
test-PesterPipelineIssue /Users/me/testingDir/testPester.txt | Should beNullOrEmptyif you change that line to "should not beNullOrEmpty"` you'll see the behavior change, which i really don't understand.
(also, sorry if I'm asking in the wrong place. Please let me know if I should move my question to a different location!)
Disregard!
hello, anybody used the BeforeEachScenario -Tags statement as described in https://kevinmarquette.github.io/2017-04-30-Powershell-Gherkin-advanced-features/#beforeeachscenario. I get the following error: "The expression after '&' in a pipeline element produced an object that was not valid."
I have a function to get environment variable, where I have used Get-EnvironmentVariable function to get the value. While writing pester test, I want to mock [System.Environment]::Get-EnvironmentVariable('XXXX', 'User') inorder to test empty scenario and with value scenrio. Can anyone help on this
@routhrirajan Don't think it is possible to mock that, easiest it to make a wrapper (powershell function) for the method
[System.Environment]::GetEnvironmentVariable() and mock that. Another way might be to make a stub class and load with Add-Type, but not sure it works in this case since the type is already loaded.
Hey @nohwnd I want to take a stab at this pester/Pester#301 . Is it ok? Is there anyone working on something conflicting with this?
Hey guys I am trying to use Pester (4.8.1) for our azure devops pipeline CI build. I have a "publish test" task and
this is what I am doing right nowInvoke-Pester -Script $testFilePath -OutputFile $outputFilePath -OutputFormat 'NUnitXML' -CodeCoverage $psFiles -CodeCoverageOutputFile $codeCoverageOutputFIlePath -EnableExit
My questions is: Is there a way I can put the result in a variable using passthru and and still save all the outputs in the specified files? I want the task to fail if any tests fail but I also have following tasks that shows test result and I want to see which tests failed. With -EnableExit fail it fails the testing task but it skips publishing test result task too
Hello everyone! how can I send parameters for each test case in a suite? currently I had just one test case to call and I do it like this
Invoke-Pester -Script @{Path = 'C:\Turing\Test\Frida-launcher.ps1'; Parameters = @{frida_process_id = '807028544'; frida_user = 'heber.solis@softtek.com'; frida_psw = 'password'}} -OutputFile "frida-results.xml" -OutputFormat "NUnitXML" but I don't know how to do it for every test case in the suite :(. Thanks for any help :)
is there a way to escape special characters in gherkin step names?
i found that trying to use parenthesis or square brackets causes it to stop matching the names of the steps in the features to the names of the actual steps
I tried escaping these with backslash and and the backtick but still can't get it to work
i found that trying to use parenthesis or square brackets causes it to stop matching the names of the steps in the features to the names of the actual steps
I tried escaping these with backslash and and the backtick but still can't get it to work
@kitforbes I have a related requirement. I have a custom module that is requiring AzureAD and AD to be imported. But obviously these are very large and I want to leave them out. I just mock all the Azure calls. Currently the only way I manage this is to exclude the required modules from the custom module's manifest psd1 file