Pickles 0.7 Released

[Jeffrey Cameron]

Good day everyone,

Another milestone was reached in the Pickles project today as we release version 0.7.  This release has benefited from a variety of committers, both regular and new.  Major highlights include:

- A new Graphical User Interface (GUI) runner.  Much thanks to Dirk Rombauts for his hard work on this runner.  It features a Metro interface and shows you all of the available options on one page for generating living documentation.

- Replaced the MarkdownSharp parser with the MarkdownDeep parser.  This allows you to use more advanced formatting in your descriptions, including tables!

- Various bugfixes

As always, you can either use NuGet to install the Powershell runner, download the .zip file from GitHub or visit the Pickles project on the CodeBetter TeamCity instance.  Please report any issues either here or on the github project.

There are a lot of possible enhancements listed on the github site.  Dirk and myself are the only regular contributors right now, it would be great if someone else would be able to step up and volunteer some time.  I would really like to hear from anyone with Java experience as it would be great to produce a version of pickles on the JVM to run in Maven/Ant/Ivy builds.

Thank you to every single person who contributed to this release.  It's very encouraging to see people stepping up and helping out.  

[Tim Mader-Brown]

Thanks for all your work on Pickles.  I did notice one bug.

The "Generate" button is only available if the user selects a different Test Results File than the default one.

[Jeffrey Cameron]

Thanks Tim,

Would you report this in the new pickles location,   https://github.com/picklesdoc/pickles ?  I just turned on the Issues tab (you may not have been able to see it before).

Thanks

[Simon D]

Hi Jeff,

 

Great tool, enjoy using it. Just wondered if you had multiple "example" tables within a single Scenario Outline on your development roadmap. At our company a few of us use the following format (from "The Cucumber Book") for some of our Scenario Outlines:-

 

Scenario Outline: Password validation

Given ...

When ...

Then ...

 

Examples: Too short

 Passwords are invalid if less than 4 characters

 

| Password | Valid or invalid |

| abc           | invalid              |

| ab1           | invalid              |

 

Examples: Letters and Numbers 

  Passwords need both letters and numbers to be valid

 

| Password | Valid or invalid |

| abc1           | valid               |

| abcd           | invalid            |

| abcd1         | valid               |

 

Currently our Pickles output under 0.7 is something like the following:-

 

Password validation

 

Examples

| Password | Valid or invalid |

| abc | invalid |

| ab1 | invalid |

| Password | Valid or invalid |

| abc1 | valid |

| abcd | invalid |

| abcd1 | valid |

 

Interested in your thoughts. Whilst there are ways around this for us such as using multiple scenarios or creating one bigger example table for the scenario, I think the extra readability you get from having multiple documented examples within a single "Scenario Outline" is worth it.

 

 

Kind Regards,

Si

[Jeffrey Cameron]

Apparently you learn something new every day!  I had never seen multiple example blocks ... ever!  I see how they could be handy and I'll incorporate support ASAP!

Would you add an issue to here, please? https://github.com/picklesdoc/pickles

Thanks for bringing this up

[Simon D]

Hi Jeff,

 

Issue now submitted.

 

Many thanks,

Si