Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The variable PesterOutputFormat is not set which result in the wrong filename #355

Closed
johlju opened this issue Mar 31, 2022 · 1 comment · Fixed by #356
Closed

The variable PesterOutputFormat is not set which result in the wrong filename #355

johlju opened this issue Mar 31, 2022 · 1 comment · Fixed by #356
Labels
bug The issue is a bug.

Comments

@johlju
Copy link
Collaborator

johlju commented Mar 31, 2022

The variable PesterOutputFormat is not set at this time. PesterOutputFormat should default to 'NUnitXML' but can also be set through the build.yaml, so the filename generation should happen after it determined if either OutputFormat or OutputPath is set, where if the latter is set, not filename generation should happen at all.

$pesterOutputFullPath = Get-SamplerAbsolutePath -Path "$($PesterOutputFormat)_$pesterOutputFileFileName" -RelativeTo $PesterOutputFolder

Expecting to generate:

NUnitXml_SqlServerDsc_v16.0.0-support.Windows.PSv.7.2.2.xml

but instead ends up as:

_SqlServerDsc_v16.0.0-support.Windows.PSv.7.2.2.xml
@johlju
Copy link
Collaborator Author

johlju commented Mar 31, 2022

The DSC Community Azure Pipelines template includes a task to upload the Test result, that task assumes the filename can be found using the pattern NUnit*.xml, Currently when using Pester 5 test results are not uploaded due to this bug. It is possible to hardcode a OutputPath in build.yaml as a workaround.

@johlju johlju added bug The issue is a bug. help wanted The issue is up for grabs for anyone in the community. in progress The issue is being actively worked on by someone. and removed help wanted The issue is up for grabs for anyone in the community. labels Mar 31, 2022
@johlju johlju removed the in progress The issue is being actively worked on by someone. label Mar 31, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug The issue is a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant