Skip to content

Gherkin Linter

Actions
A Github Action to parse and validate your feature files (gherkin / cucumber)
0.0.1
Latest
Star (3)

gherkin-linter-action

A Github Action to parse and validate your feature files (gherkin / cucumber)

Usage

Based on the gherkin-lint library this action validate your feature files.

Since the feature files can be edited by any team member a linter is the minimum check you should add before running your test suites

If all your feature files are in a folder called tests, run it like this:

name: E2E Test

on: [push]

jobs:
  Gherkin-lint:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v1
    - uses: restqa/[email protected]
      with:
        path: 'test/'
        config_file: 'test/.gherkin-lintrc'

To specify some rule you can add the configuration file .gherkin-lintrc into your root folder. (see rules on the gherkin-lint library)

Do you know RestQa ?

Restqa is an open automation framework based on Gherkin. A few step and your Test automation framework is setup. No dependency the framework is ready to be plug to all your project components Give a try 🚀

References

Keywords

  • test automation
  • Gherkin
  • Cucumber
  • End to End
  • E2E
  • Quality assurance
  • QA
  • Continuous integration
  • RestQa

Gherkin Linter is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.

About

A Github Action to parse and validate your feature files (gherkin / cucumber)
0.0.1
Latest

Gherkin Linter is not certified by GitHub. It is provided by a third-party and is governed by separate terms of service, privacy policy, and support documentation.