-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Pickles Doc compatibility for scenario outlines #83
Comments
@videege I cannot speak to pickles too much, unfortunately, not yet. By looking at the commit history, I see that @csurfleet implemented that compatibility. Maybe he could help. @csurfleet any thoughts? |
@videege did you find the answer to your question, or is it still an issue? |
This is still an issue for my team, but I haven’t investigated it any further.
… On Jan 9, 2020, at 6:25 PM, Tengiz Tutisani ***@***.***> wrote:
@videege did you find the answer to your question, or is it still an issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@videege so sorry, I only just spotted this! I'm actually hooking in PicklesDoc to some Scenario Outlines at the moment, so I'll hopefully have got this confirmed and bottomed for you in the next couple of weeks |
We use Pickles (https://github.com/picklesdoc/pickles) to package up our results and feature files as a nice readable website as part of our CI/CD process. Currently, Pickles is able to match test results to scenarios correctly for everything but scenario outlines - these all end up blank in the Pickles output despite having entries in the test output.
I am generating a XML results file by running
dotnet test --test-adapter-path:. --logger:xunit -r /results
. Scenario outline results in the file look like this:I'm not sure if the issue is with Xunit.Gherkin.Quick or PicklesDoc not interpreting correctly (it claims to understand 'xunit2' results files, but I'm not sure if this is universal or just SpecFlow-specific xunit results.), so I figured I'd ask.
The text was updated successfully, but these errors were encountered: