Handle Failures/Results with Azure ADO

[rcoughtrey]

I'm trying to understand failure handling with pester; here is what I want to do:

Inside the 'IT' I have a test that calls a function to confirm a location. Inside that function I have a try catch loop as well as retry loop. This allows me to catch the failure if the command fails or if the value were trying to get cannot be found. For example the DB does not have the data we would retry 5 times every 10 seconds.

$global:getLocation = GET-Location-LocNum -urlLocation $urlLocation -domain locations -cert $locationsCert -Headers $headers -locNum 1111
$global:getLocation | Should -Not -BeNullOrEmpty

What I'm seeing is that if all the tests pass and have no failures in my try catch there are no issues

Now if I get a failure in the assertion or if a failure occurs in the function try/catch or retry loop then I never get any test results.

Here is the failure on the test

##[error] [-] Confirm location 2.88s (2.88s|3ms)
##[error] Expected case sensitive like wildcard $null to match '55555', but it did not match.
##[error] at $global:postlocation | Should -BeLikeExactly $global:getlocation,
##[error] at , /home/vsts/work/1/s/Automation/Pipeline-Automation/api-e2e-automation/Tests/API-e2e-automation.ps1:87

here he the tests output

Tests completed in 80.44s
Tests Passed: 10, Failed: 1, Skipped: 0 NotRun: 0

##[error]PowerShell exited with code '1'.
Finishing: API e2e Automation

Looking in my ADO results it never tries to parse the results. I get no errors about no files so thats not the issue:

ADO task

• task: PublishTestResults@2
  inputs:
  testResultsFormat: 'NUnit'
  testResultsFiles: '**/Test-Pester.XML'
  ADO pipeline
  Evaluating: SucceededNode()
  Result: False

[rcoughtrey]

Dang it... Fixed noticed my ADO config was misaligned

• task: PublishTestResults@2
  inputs:
  testResultsFormat: 'NUnit'
  testResultsFiles: '**/Test-Pester.XML'
  condition: succeededOrFailed() <------- Was in the wrong spot under inputs :(