Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for gherkin contexts

Open
#2,815 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript, node.js
Domain
testing

Research direction

No repository file, test, or entry point is identified in the issue. Start by tracing CodeceptJS's Gherkin configuration and the event-based workaround, then define how the shown default, tag, and role contexts should select step-definition paths and how that behavior will be verified.

Written by the indexing model from the issue text.

Description

What are you trying to achieve?

I would like to organize files with steps by context, similar to codeception:

"gherkin": {
  "features": "./features/*.feature",
  "contexts": {
    "default": ["./step_definitions/steps.js"],
    "tag": {
      "fastlogin": ["./step_definitions/fastlogin.js"]
    },
    "role": {
      "admin": ["./step_definitions/admin.js"]
    }
  }
}
What do you get instead?

This functionality could probably be simulated using events.

Dominant language
JavaScript
Stars
4.2k
Forks
756
Avg merge
2d 9h
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from codeceptjs/CodeceptJS

All issues in codeceptjs/CodeceptJS

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.