-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AfterScenarioListener does not fire #76
Comments
Thinking more closely, this is perhaps something i should register myself in my BaseContext, no? |
"require": { |
I am testing a pull request that has been submitted that looks to resolve the Can you provide the fixture you are using in the form on a sample scenario and step definitions and I will run this to ensure its all resolved. |
I just used the standard one from the "How to"-section:
First time the test fails, and upon running it again it complains about "sql-duplicate-key-warning". |
Hello,
I noticed that when running my test a second time, the fixtures from the previous run isn't cleaned and I get an "sql-duplicate-key-warning". Going through the code it looks like the AfterScenarioLister isn´t registered anywhere and subsequently never fires after the test suite is run.
The text was updated successfully, but these errors were encountered: