An After for a RailsWorld should execute before the transaction is rolled back
Reported by Luke Melia | December 3rd, 2008 @ 08:38 PM
I am interested in doing some database examination after each scenario runs, so I added an After block to my env.rb, but it runs after the scenario's DB transaction has been rolled back. I'm going to experiment with ways to work around this, but I figured I'd open a ticket because it seems unintuitive.
Comments and changes to this ticket
-
Luke Melia December 5th, 2008 @ 05:46 PM
I made my particular scenario work by calling Cucumber::Rails.use_transactional_fixtures after I declare my After block.
Hardly ideal, though. Not sure what the best solution is. Seems like a similar problem to before_filter, prepend_before_filter, etc. in Rails.
-
Aslak Hellesøy December 7th, 2008 @ 06:32 PM
- no changes were found...
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
TreeTop based implementation of rbehave (a.k.a. Story Runner, a.k.a. Feature Runner)
Joseph Wilk