Shoma Gujjar
Jan 29, 2016
visibility 4840
star star star star star star
(2 votes)

Pickles : Living documentation generator

Recently there came a requirement from the business,they wanted to know a high level view of the specification/requirements of an Project. A colleague suggested that feature files written in gherkin statements where ideal for this purpose.

Therefore we had to look for a tool that would translate the feature files to a more business-friendly format (word,pdf,html), so that the business could have a look at it at their convenience without having to reach out developers.

There were 2 main tools that suited this requirement namely:

  1. Relish
  2. Pickles

Relish is based on Ruby plus it comes with a subscription fee. They do have a Free plan, but all your projects will be public!

Pickles is open-source and easily installed via nuget. The documentation can be found here. Pickles can be run via commandline, GUI,PowerShell or MSBuild

Sample Example using CommandLine

Pickle supports Html, Dhtml,word,JSON and Excel formats.

Install Pickles in your project:

using nuget console manager : Install-Package Pickles.CommandLine

Open Command Prompt in Administrator mode – > Navigate to your Specs project and execute the below command

..\packages\Pickles.CommandLine.2.3.0\tools\pickles.exe --feature-directory=C:\BitBucket\TestProj.Specs --output-directory=c:\my-features-output --documentation-format=dhtml

where --feature-directory =  is the path to your test project

--output-directory =  path to your output file

--documentation-format =  format of the output (optional) . The default output is html

If you want the output in word format then set --documentation-format=word

Plus

The above command can be copied to a .bat-file.

Pickles can also be integrated into automated build or continuous integration tool like TeamCity.

Jan 29, 2016

Comments

error Please login to comment.
Latest blogs
Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026

Optimizely DXP: Every Supported Culture, One Searchable Page

Quick one for anyone building multi-language sites on Optimizely DXP. I put together a reference tool listing all 806 supported cultures. More...

Adnan Zameer | Jul 10, 2026 |

A day in the life of an Optimizely OMVP: London Meetup 2026

On 2nd July 2026 the Optimizely London Developer Meetup returned to The Lightwell, and the running theme across the evening was less about individu...

Graham Carr | Jul 10, 2026

Optimizely’s Summer ’26 Roadmap: The CMS Is Starting to Look Less Like a Publishing Tool and More Like Marketing Infrastructure

Optimizely’s Summer ’26 Product Roadmap event was not just a list of product updates. At least, that is not the part I found most interesting. The...

Augusto Davalos | Jul 9, 2026

Optimizely Content JS SDK v2.1.0 — What's New and Why It Matters

  v2.1.0 of the Optimizely Content JS SDK and CLI landed on July 7, 2026. This is a substantial release bringing a wave of capabilities for...

Vipin Banka | Jul 8, 2026