Can Pickle(Living Documentation Generator) be used for gauge specs as it does for Cucumber(gherkin)

[Arish Arbab]

We were using Pickle before for generating the more readable format Cucumber GWT scenarios. Now I was wondering if the same can be used for gauge so that specs are generated in more readable format.

[Srikanth V]

Hi Arish,

Thanks for introducing us to Pickle. It looks very interesting.

I guess you could integrate Gauge with Pickle using the xUnit style xml. If you install the xml-report plugin for gauge, you could generate xml output for your test run that you could feed to Pickle by specifying the Test Result Format.

Please note that Gauge generates JUnit style XML, whereas Pickle supports NUnit/xUnit style. I believe they are compatible, but there might be edge cases that I am unaware of.

Please have a shot at this and let us know how it goes!

best

Srikanth

[Arish Arbab]

Hi Srikanth,

Thanks for your response. But Unfortunately, as of now, pickles only understands .feature file as its input. Gauge has .spec file .

Below is the image which will make you understand how pickle works.

 

I was wondering if we can make Pickle to understand .spec files also rather than files written in Gherkin format.

[Arish Arbab]

HI- Did you get a chance to look at it ? We are planning to move away from cucumber as Gauge seems to be more promising. But It would be very helpful if we can have some features supported by Cucumber in Gauge also. Pickles in this case.

[Srikanth V]

Hi Arish,

I tried to get my head around Pickles a bit more, and started on a simple project to get the two (Gauge and Pickle) together. It seems that there might be work from Pickle side to understand Gauge's .spec files (which are essentially Markdown files).

Now this got me thinking - wouldn't converting Markdown to Html be good enough for you? For documentation purposes?

The execution report serves a slightly different purpose, it has information like pass/fail, values, stacktraces on failure etc. Whereas one of the main reasons we decided on Markdown to author specs, is that it can be ported to html very easily.

Please have a think about the idea of generating html from the markdown spec files directly, and let us know if there is anything that we are missing.

As for other features that you might need, please feel free to open issues on github, we are already working on one issue that you mentioned earlier - writing custom values in reports.

thanks!

srikanth

--
You received this message because you are subscribed to the Google Groups "getgauge" group.
To unsubscribe from this group and stop receiving emails from it, send an email to getgauge+u...@googlegroups.com.
To post to this group, send email to getg...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/getgauge/b917519f-29e1-4d06-8a23-a6dd73a15c84%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Arish Arbab]

Many Thanks for the update !!