To support hooks

[jlin412]

hooks are not supported feature yet

[stevepkuo]

Is it possible to add a BeforeFeature hook? Such that whatever I specify in BeforeFeature will run before each feature file? (Such as clearing the test database)

[lgandecki]

@stevepkuo I don't think you shouldn be running things before feature itself, your scenario should be independent, and they should start with a clean state everytime. That's what you can use Background functionality for

[BenoitAverty]

How would the hooks work ? Would they be defined in the feature files ? In the steps file ? (but then the question is, where are they placed).

I'd be happy to attempt a PR but I'm not sure how we want to design this.

[lgandecki]

I think we would probably want to design it to resemble the cucumberjs hooks:

https://github.com/cucumber/cucumber-js/blob/master/docs/support_files/hooks.md

So, in step definitions.
I’m not sure what are the rules for how the before would work - do we make them work on file basis?

A good attempt might be to install cucumberjs and play with their functionality and then try to reflect it here.

The beforeAll afterAll might be the easiest to start :-)

[BenoitAverty]

It seems that the hooks are "global" in the sense that we can't restrict them to a specific feature or scenario (which is normal I think). I think it might be better to define them in their own support file or folder with a new configuration option, similar to the ste_definitions folder.

[lgandecki]

Yeah, I think that makes sense actually.
But that's more of a pattern. If someone wants they should be able to put those anywhere.

[jlin412]

actually, you can have tagged hook where you restrict hooks based on scope of tags

[victorheid]

What is the advised if i need to have my database reset after every scenario? The scenario is independent each time, but in my case I rely on an external service that needs to be reset

[lgandecki]

is background step not suitable for that?

[victorheid]

@lgandecki Although I forgot about the Background steps (thanks for remind myself!), I was trying to attach something like the beforeEach, to just wipe the api application after every Scenario.

It can be done through the Background steps as well I guess, just a preference if you want to have the api wipe/refresh as a step.

Do you have any opinion about this? Does CCP support Contexts BTW?

[andrei-ciocan]

  @before-hook1
  @before-hook2
  @after-hook3
  Scenario: Do Something
    Given I do something
    When I do something else
    Then something else should happen

Could we support adding those kind of hooks inside the .feature files? It would be really helpful controlling what you want to run and when, so you don't repeat unnecessarily a large amount of code when you have a chain of actions that reuses a certain feature. Inside step_definitions or hooks folder we could have the implementation.