{"id":7409,"date":"2020-04-24T13:21:54","date_gmt":"2020-04-24T17:21:54","guid":{"rendered":"https:\/\/jdhitsolutions.com\/blog\/?p=7409"},"modified":"2020-04-24T13:21:57","modified_gmt":"2020-04-24T17:21:57","slug":"importing-pester-results-into-powershell","status":"publish","type":"post","link":"https:\/\/jdhitsolutions.com\/blog\/powershell\/7409\/importing-pester-results-into-powershell\/","title":{"rendered":"Importing Pester Results into PowerShell"},"content":{"rendered":"

Last week, a PowerShell scripting challenge<\/a> was posted on the Iron Scripter web site.  The idea was that when you run a Pester test, you can save the results to a specially formatted  XML file.<\/p>\n

<\/p>\n

Invoke-Pester C:\\scripts\\sample.test.ps1 -OutputFile d:\\temp\\results.xml -OutputFormat JUnitXml<\/pre>\n
<\/p>\n
I get this result.<\/p>\n
\"pester-export\"The challenge was to write a PowerShell command that could take the XML file and recreate this output as much as possible. Here's my result.<\/p>\n
\"pester-import\"I have added a metadata header, but otherwise I think this is a pretty good recreation. Are you curious how I did this? If you want to try your hand at the challenge first, stop reading now.<\/p>\n
Spoiler Alert<\/h2>\n
I wrote my function to recreate Pester results using the JunitXML format. It would be nice at some point to modify the function to be able to handle both XML formats. The function I wrote has a Path parameter . I can specify a value or pipe a file to the command.<\/p>\n
Param(\n        [Parameter(position = 0, ValueFromPipeline, HelpMessage = \"Specify the path to the JunitXML Pester test file.\")]\n        [ValidateNotNullorEmpty()]\n        #verify the file exists and it is an XML file\n        [ValidateScript({\n            If ((Test-Path $_) -AND ($_.split('.')[-1] -eq 'XML' )) {\n                $True\n            }\n            else {\n                #display a custom validation error message\n                Throw \"The file could not be found or wasn't an XML file.\"\n            }\n        })]\n        [Alias(\"pspath\")]\n        [string]$Path\n    )\n<\/pre>\n
The parameter definition is using a few validation tests. The main test is to ensure that the file exists and that it ends in XML. I have other validation later to test if it is a JunitXML file. Yes, I know that I could technically export the results using any file extension, but I'm assuming XML plus I wanted to demonstrate this technique.<\/p>\n
The other feature in the parameter is that I am creating my own custom error message. When you use [ValidateScript()], the scriptblock must give you True or False.  In my case, if the test fails, I am throwing a customized error message.<\/p>\n
\"paramfail-1\"<\/p>\n
PowerShell 7 handles this even nicer.<\/p>\n
\"paramfail-2\"<\/p>\n
At this point it becomes a matter of parsing the XML document.<\/p>\n
Process {\n        Write-Verbose \"Processing $Path\"\n        [xml]$doc = Get-Content -path $Path\n<\/pre>\n
I can look inside the XML to determine if this is a junit file. If it isn't I'll bail out of the command.<\/p>\n
if ($doc.testsuites.noNamespaceSchemaLocation -notmatch \"junit\") {\n            Write-Warning \"Could not import $Path. You must specify a Pester test result file using the JUnitXML format.\"\n            #abort\n            return\n        }\n<\/pre>\n
Otherwise, I'm parsing the document to get the metadata information which is assembled in a here-string and written to the host using Write-Host. In fact, the entire function writes directly to the console using Write-Host. Nothing is written to the pipeline. Although I will show you an option later. For this challenge, using Write-Host is perfectly fine. Another option would be to write a version of my function for PowerShell 7 and use ANSI escapes for the colorization. I'll save that for another time or you can write it.<\/p>\n
Parsing Tests<\/h2>\n
The tricky part was parsing the test results. I had this XML to work with.<\/p>\n
<testcase name=\"Alpha.Should have a value over 1\" status=\"Passed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.465\" \/>\n    <testcase name=\"Alpha.Should fail on a null value\" status=\"Failed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.190\">\n      <failure message=\"Expected $true, but got $false.\" \/>\n    <\/testcase>\n    <testcase name=\"Alpha.Should accept a mandatory Computername parameter\" status=\"Passed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.300\" \/>\n    <testcase name=\"Alpha.Testing.Should have a value of 4\" status=\"Passed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.894\" \/>\n    <testcase name=\"Alpha.Testing.Should run without error\" status=\"Passed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"1.150\" \/>\n    <testcase name=\"Bravo.Should have a value less than 1\" status=\"Passed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.525\" \/>\n    <testcase name=\"Bravo.Should export the gravitational constant\" status=\"Skipped\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.000\">\n      <skipped message=\"\" \/>\n    <\/testcase>\n    <testcase name=\"Bravo.Should run without errors\" status=\"Passed\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"2.357\" \/>\n    <testcase name=\"Bravo.Should run with credentials\" status=\"Pending\" classname=\"C:\\work\\sample.test.ps1\" assertions=\"0\" time=\"0.000\">\n      <skipped message=\"\" \/>\n    <\/testcase>\n<\/pre>\n
The Name attribute is the key item. The first part, up to the first period, is the Describe block. In my sample this is Alpha and Bravo.  Anything after the period is the assertion or the It statement. Unless, there is an intermediate word like 'Testing'. This is a Pester Context element.<\/p>\n
I tried several techniques to pull this text apart. Eventually I settled on using a regular expression pattern.<\/p>\n
[regex]$rx = \"(?^[\\w-_\\s]+(?=\\.))\\.((?(?<=\\.)\\w+(?=\\.))\\.)?(?(?<=\\.).*)\"\n<\/pre>\n
The pattern uses named captures to identify the Describe, Context and Assertion components.<\/p>\n
Looking to learn more about regular expressions in PowerShell? I created an entire course<\/a> on the subject for Pluralsight.<\/p><\/blockquote>\n
I use this pattern to turn each test case into a custom object.<\/p>\n
$tests = $doc.testsuites.testsuite.testcase | Group-Object -property Name\n        Write-Verbose \"Processing $($tests.count) tests\"\n\n        #turn each test into an object using a regex to split\n        $testobj = foreach ($test in $Tests) {\n            $m = $rx.Matches($test.name)\n            [pscustomobject]@{\n                Describe  = $m.groups[2]\n                Context   = $m.groups[3]\n                Assertion = $m.groups[4]\n                TestCase  = $test.group\n            }\n        } #foreach test\n<\/pre>\n
I found this to be much easier to work with. Now I can use commands like Group-Object and ForEach to process the results in an orderly fashion, writing results to the host based east test. I ended up creating a private helper function, _parseTestCase, that would write the result to the host. When you look at the code, you'll see I'm using a Switch statement to determine what symbol and foreground color to use.<\/p>\n
For the summary, I grouped the TestCase node on the Status property as a hashtable. The hashtable keys will things like 'Failed' and 'Skipped'. This makes it easy to get the counts that I need to display.<\/p>\n
#write the summary information to the host in color\n        $testHash = $doc.testsuites.testsuite.testcase | Group-Object -property Status -AsHashTable -AsString\n\n        Write-Host \"Tests completed in $(New-TimeSpan -seconds $doc.testsuites.time)\" -ForegroundColor White\n        Write-Host \"Tests Passed: $($doc.testsuites.tests), \" -ForegroundColor White -NoNewline\n        Write-Host \"Failed: $($TestHash[\"Failed\"].count), \" -ForegroundColor Red -NoNewline\n        Write-Host \"Skipped: $($TestHash[\"Skipped\"].count), \" -ForegroundColor Yellow -NoNewline\n        Write-Host \"Pending: $($TestHash[\"Pending\"].count), \" -ForegroundColor gray -NoNewline\n        Write-Host \"Inconclusive: $($TestHash[\"Inconclusive\"].count)\" -ForegroundColor DarkGray\n<\/pre>\n
The complete code is on Github.
\n