Gherkin-detailer
  • Introduction
  • Examples
  • Glossary
Powered by GitBook
On this page
  • Default execution
  • Custom analysis folder execution
  • Custom output folder execution
  • Custom theme execution

Was this helpful?

Examples

Default execution

"gherkin-detailer": "gherkin-detailer"

This command starts to read all the files contained in the current folder.

All the .feature files will be analysed in order to retrieve all scenarios written with the gherkins.

Once the analysis is done, an html report will be stored in the deafult folder report/gherkin-detailer/.

Custom analysis folder execution

"gherkin-detailer": "gherkin-detailer -a 'documentation/features/'"

This command starts to read all the files contained in the folder documentation/features/.

All the .feature files will be analysed in order to retrieve all scenarios written with the gherkins.

Once the analysis is done, an html report will be stored in the deafult folder report/gherkin-detailer/.

Custom output folder execution

"gherkin-detailer": "gherkin-detailer -o 'output/'"

This command starts to read all the files contained in the current folder.

All the .feature files will be analysed in order to retrieve all scenarios written with the gherkins.

Once the analysis is done, an html report will be stored in the folder output/.

Custom theme execution

"gherkin-detailer": "gherkin-detailer -t 'black'"

This command starts to read all the files contained in the current folder.

All the .feature files will be analysed in order to retrieve all scenarios written with the gherkins.

Once the analysis is done, an html report with a custom black theme will be stored in the deafult folder report/gherkin-detailer/.

PreviousIntroductionNextGlossary

Last updated 6 years ago

Was this helpful?