You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pester version : 5.3.1 C:\Users<name>\Documents\PowerShell\Modules\Pester\5.3.1\Pester.psm1
PowerShell version : 7.2.2
OS version : Microsoft Windows NT 10.0.17763.0
Steps to reproduce
Use the pester configuration as described above and upload the code coverage into Azure Devops
I tried this, and you are right. For files that are deeper in the directory structure it does not work. There is another format based on JaCoCo available that is called CoverageGutters which works for me just fine in azdo:
I am using your configuration, I just changed the output format to this:
OutputFormat = 'CoverageGutters'
You can also use this for make coverage work in your VSCode, if you use that:
General summary of the issue
The code coverage XML file which is being generated by Pester-5 New-PesterConfiguration isn't compatible with Azure Devops.
Pester Configuration:
The code coverage XML file that is being generated by the deprecated Pester 4 switches is functioning properly with Azure Devops.
Describe your environment
Pester version : 5.3.1 C:\Users<name>\Documents\PowerShell\Modules\Pester\5.3.1\Pester.psm1
PowerShell version : 7.2.2
OS version : Microsoft Windows NT 10.0.17763.0
Steps to reproduce
Use the pester configuration as described above and upload the code coverage into Azure Devops
Expected Behavior
Current Behavior
Possible Solution? (optional)
We managed to fix this issue by altering the XML after it is being created.
The text was updated successfully, but these errors were encountered: