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
I don't feel very active here. There are only 69 members.
How is it possible to use Variables for Describe and It blocks in V5? It is not necessarily the -TestCases parameter that helps me out. Im testing various command line tools, each test tool goes into its own file (command.Tests.ps1) so it would be neat to use the "command" as variable from the filename in the it and Describe copes (Descript "test ${command}" ..)
Using BeforeAll with $global:command="foo" is problematic because if pester is called with -Path on a directory with multiple tests. the global variable overrides during execution all other files too,.. i had weird behavior.
I have a function which uses some Azure Cli commands, for example:
$appRegistration = az ad app create `
--display-name $name `
--reply-urls $replyUrls `
--oauth2-allow-implicit-flow true `
--available-to-other-tenants false `
-o json |
ConvertFrom-JsonHow can I mock az ad app create and assert the parameters with Assert-MockCalled? I don't find anything about that
@dgroh
Mocking an executable is not possible. At least not to my knowledge.
In this scenario I create a 'wrapper' function that calls the executable. This 'wrapper' function can be mocked.
Mocking an executable is not possible. At least not to my knowledge.
In this scenario I create a 'wrapper' function that calls the executable. This 'wrapper' function can be mocked.
function Invoke-AzureCli {
switch ($isWindows) {
$True {
$AssertPath = Test-Path -Path 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\wbin\az.cmd'
}
$False {
switch ($IsLinux) {
$true {
$AssertPath = Test-Path -Path '/usr/bin/az'
}
Default { throw "Unsuported operating system detected '$PSVersionTable.OS'" }
}
}
}
if ($AssertPath -eq $False) {
throw "Azure CLI not found!`nThis function requires Azure CLI to be available on this system.`nhttps://docs.microsoft.com/en-us/cli/azure/install-azure-cli"
}
az $args
if ($LASTEXITCODE -ne 0) {
throw 'Execution failed'
}
}
(This is only like my second time using Gitter, and first time trying to Pester 5 in ernest)
The pester.dev documenation isn't clear to me what exactly $PesterPreference is compared to a PesterConfiguration, and why I would want to use one method over the other, or why either are even necessary when I just want to run a test and see the actual output?
https://pester.dev/docs/usage/configuration#pesterpreference
1 reply
Just doublechecking before raising an issue: in Pester 5.3 there seems to be no way to get codecoverage parameters like function/startline/endline passed into Pester anymore? The legacy parameter set doesn't accept a hashtable for
-CodeCoverage (well it does but it turns it into the string "System.Collections.HashTable" and PesterConfiguration.CodeCoverage only has Paths and enforces that to be a string array. Is this something which is being worked on?
Cannot read property '0' of undefined
Does anybody know what seems to be the problem ?
I reinstalled powershell extension just to make sure, but no bueno. Tests work fine when executed outside of vscode
Using latest Pester, vscode, Powershell extensin, pwsh
Powershell extension logs show nothing interesting
[Error - 16:32:42] Microsoft.PowerShell.EditorServices.Services.PowerShellContextService: Execution of the following command(s) completed with errors:
Microsoft.PowerShell.Core\Get-Command Send-Ping -ErrorAction Ignore
|
Anyway, when I remove all the code and leave just
Describe 'Pinging' {} it still fails, but without any error