cucumber / cucumber/vscode

Scenario Outline - changes to steps not recognised unless you comment out the Examples/Scenarios table

Open
#268 2 comments 0 reactions 0 assignees View on GitHub
:bug: bug
Dominant language
TypeScript
Stars
88
Forks
33
PR merge metrics
No merged PRs in 30d

Description

### 👓 What did you see?

For tests that have Scenario Outline with Examples/Scenarios table - changes to steps are not recognised unless you comment out the Examples/Scenarios table.

### ✅ What did you expect to see?

If an existing step is amended or a new step is added, I would expect it to be recognised as a new step and given the option to define the step in a steps class.

### 📦 Which tool/library version are you using?

Cucumber for VSCode 1.10.0
Reqnroll.xUnit 2.2.1

### 🔬 How could we reproduce it?

Create a test with Scenario Outline and Examples/Scenarios table - make a change to a step, or add a new step. Observe that the step is not recognised as being new, and needing to be defined - until you comment out the Examples/Scenarios table, will then be recognised as being new and give you the option to define the step.

### 📚 Any additional context?

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.