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

Generated Cucumber JSON missing the uri property #609

Open
rdasan opened this issue Apr 19, 2021 · 3 comments
Open

Generated Cucumber JSON missing the uri property #609

rdasan opened this issue Apr 19, 2021 · 3 comments

Comments

@rdasan
Copy link

rdasan commented Apr 19, 2021

Hi I'm using Pickles to generate Cucumber Json format from my Test Results file. However I see that the generated cucumberResults.json is missing the uri property. I am planning to use the generated cucumber json to publish the cucumber results back into a BDD JIRA plugin and that plugin requires the correct Cucumber JSON format that includes a uri property in the generated Cucumber Json.

I see that this issue has been mentioned earlier in this closed issue : #278

#278 (comment)

Are there any plans to support this moving forward?

@isitgeorge
Copy link

+1

Also missing id properties from both the top level feature and child objects of the elements array.

@ericcmmi
Copy link
Member

Yes, I would like to address this issue. Most of the issues that Dirk closed before he handed off the project will be reopened and worked eventually. Most of my time so far has been spent trying to get the dotnet standard/core version working. I have most of it functional but still have some unit tests failing. Once I get past that roadblock I'll start addressing more of the functionality issues.

@ghost
Copy link

ghost commented Sep 18, 2021

I have the same issue as @rdasan as now the only way to convert SpecFlow results into Cucumber json is via official SpecFlow runner SpecRun, requiring online account binding and relying on Mono, also conflicting with SpecFlow xUnit runner. My use case is Linux-based CI and MacOS-based development environment, so I look into Pickles or SpecNuts.
Another way is to contribute to SpecFlow itself, like asked here.
Maybe to the xunit runner directly, maybe to the LivingDocumentation generator.
But I see pickles as the best option, especially with the recent dotnetcore support

ghost pushed a commit to CoverGo/pickles that referenced this issue Sep 20, 2021
Update filesystem abstraction nuget package System.IO
Make related changes to tests: 
use IDirectoryInfo instead of DirectoryInfoBase, 
IFileSystemInfo instead of FileSystemInfoBase,
IFileInfo instead of FileInfoBase


Update DocumentFormat.OpenXML package, but still have xml-related error on MacOS during unit tests 
Use filesystem to build paths 
Do not use Windows-specific filepaths like "c:\file"
Use Environment.NewLine instead of \r\n

Update NFluent to compare strings thinking less of different line endings on different platforms

picklesdoc#609
ghost pushed a commit to CoverGo/pickles that referenced this issue Sep 20, 2021
Produce test result value according to
https://github.com/cucumber/cucumber-json-schema

Update existing cucumber tests to run on non-windows platform
picklesdoc#609
ericcmmi pushed a commit that referenced this issue Sep 22, 2021
* Update tests to launch on non-windows platform

Update filesystem abstraction nuget package System.IO
Make related changes to tests: 
use IDirectoryInfo instead of DirectoryInfoBase, 
IFileSystemInfo instead of FileSystemInfoBase,
IFileInfo instead of FileInfoBase


Update DocumentFormat.OpenXML package, but still have xml-related error on MacOS during unit tests 
Use filesystem to build paths 
Do not use Windows-specific filepaths like "c:\file"
Use Environment.NewLine instead of \r\n

Update NFluent to compare strings thinking less of different line endings on different platforms

#609

* Update cucumber json report format to match official json schema

Produce test result value according to
https://github.com/cucumber/cucumber-json-schema

Update existing cucumber tests to run on non-windows platform
#609

* Add feature uri to cucumer json report

Add feature base uri parameter to command line

* Add feature and step id, hidden field to Cucumber json report

* Make Pickles.CommandLine packable as dotnet tool

Update csproj to not use deprecated fields
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants