Mark Step Definition as Obsolete
Hi,
Say, I have a gherkin step "Given I want to work with numbers" and corresponding step definition as follows.
[Given(@"I want to work with numbers")]
public void IWantToWorkWithNumbers()
{
//Old way of working with numbers
}
This step definition has been used by several feature file and scenarios and I don't want to change this. The old way of doing things is still good but we want to replace it with new way of working with numbers(hypothetical scenario).
What can I do to keep the old step definition as is (to avoid breaking existing scenario) but write a new step definition with same binding [Given(@"I want to work with numbers")] and a newer step definition and any newly written scenarios with the same gherkin step map to the new step definition.
Please sign in to leave a comment.
Comments
0 comments