To have After each Scenario Like it has background which executes Before Each Scenario

[vdubbaka]

🤔 What's the problem you're trying to solve?

Unable To perform certain steps after each scenario that is similar of background which is before each scenario.
Problem: Set of 3 steps needs to run after most of the scenarios (400 scenarios) if it had After_Scenario that would be really helpful and reduces (~1200) steps.

✨ What's your proposed solution?

To have after each scenario that is similar of background which is before each scenario.
Nice to Have:
Before Each Feature
Before Each Scenario - Like Backgroud but with ability to exclude certain scenarios
After Each Feature
After Each Scenario

Like create a user before each scenario and delete the user after each scenario

⛏ Have you considered any alternatives or workarounds?

No response

📚 Any additional context?

No response

[luke-hill]

Would an after hook that is tagged not suffice?

https://cucumber.io/docs/cucumber/api/#scenario-hooks

[mpkorstanje]

Agreed. Feature files describe the systems behavior. Cleaning up after your tests isn't part of the systems behavior so cleanup isn't a problem that should be solved in a feature file.

Rather you could solve this by keeping track of your created users in your step definitions and then deleting them in an after hook. Something like:

Given "I've created a user" {
    world.user = // create user here
}

After {
  if world.user != null {
    // delete user
 }
}

[vdubbaka]

It uses API to delete user's data and user with admin token. It is not as in creating on user and deleting it.

[luke-hill]

I'm unsure how this is affected by or requires cucumber to manage.

If you require an API token you need to store and manage this yourself in something like an env variable / token

As @mpkorstanje said above. A simple way to delete / track users is above. Also linked to the hooks page where you can add more/less granularity or nuances that you may need