-
-
Notifications
You must be signed in to change notification settings - Fork 469
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
Detailed Output vs Test Report - Skipped #2220
Comments
Thanks for the report. We could however update the placeholder-value for |
Thanks for the feedback. Is there any way I can assist with this, so we can have the change to be part of the next release? I'm new to the code base of pester, but I'm up for the challenge to see if I can fix it and do the PR. Just need some pointers, then I can test local and see if my scenario can be handled or not. |
Absolutely, contributions are always welcome 😃 As for the code:
|
Still interested in submitting a PR @Splaxi? 🙂 |
Yeah - but when I tried the last time, I couldn't find a way to solve the issue. So I feel that I'm smart enough to tackle the challenge, regardless of me having the issue 🤦♂️ |
Looking back at it months later - it wasn't my best explanation 😄 |
Checklist
What is the issue?
It seems that the logic with expanding the path of a given test, is being handled differently when we are talking about the detailed output and the output object.
The detailed output expands the path of each test / describe:
But the output object looks like this:
Expected Behavior
I would expect the expanded path to work the same way as the detailed output, so when you are generating NUnit/JUnit files, the would reflect the same values.
Steps To Reproduce
No response
Describe your environment
No response
Possible Solution?
No response
The text was updated successfully, but these errors were encountered: