./nugetz
/
trending/tags

#SpecificationByExample

7 packages tagged with “SpecificationByExample”

pkg

Pickles.CommandLine

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.3↙ 2.0M
SpecificationByExampleBDDSpecFlowGherkinCucumber

Pickles

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.3↙ 1.6M
SpecificationByExampleBDDSpecFlowGherkinCucumber

Pickles.MSBuild

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.3↙ 592.5K
SpecificationByExampleBDDSpecFlowGherkinCucumber
pkg

Pickles.CommandLine.linux

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.3↙ 3.7K
SpecificationByExampleBDDSpecFlowGherkinCucumber
pkg

Pickles.CommandLine.win

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.3↙ 3.9K
SpecificationByExampleBDDSpecFlowGherkinCucumber
pkg

Pickles.CommandLine.osx

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.3↙ 2.3K
SpecificationByExampleBDDSpecFlowGherkinCucumber
pkg

Pickles.CommandLine.net4

**Pickles** is an open source **living documentation** generator that works on feature files written in the *Gherkin* language, popularized in tools like *Cucumber* and *SpecFlow*. *Pickles* can be incorporated into your build process to produce living documentation in a format that is more accessible to your clients. *Gherkin* language files are written in plain text and stored in your source folder. This can make them inaccessible to clients who may not know how to work with source control or who are not interested in seeing all of the source code, just the features. *Pickles* can produce output in different formats: - Static HTML: a set of HTML files with minimal JavaScript - Dynamic HTML: a JavaScript-rich single page app with integrated search - Word: Microsoft Word - Excel: Microsoft Excel - JSON: a custom JSON format - Markdown: a simple output format Optionally, *Pickles* can **integrate test results**, so that your stakeholders know which scenarios pass validation. *Pickles* supports these test formats: - NUnit - MSTest - XUnit - SpecRun - Cucumber JSON

v4.0.1↙ 638
SpecificationByExampleBDDSpecFlowGherkinCucumber