When running cucumber with backends like selenium or culerity, there
are two processes involved: one for your application (server) and
another one for cucumber. It means there are two different MySQL
connections: one in each process. SQL transactions are bound to
database connections; it means cucumber cannot rollback a transaction
initiated by your app's server.
HTH,
Julien.
> --
> You received this message because you are subscribed to the Google Groups "Cukes" group.
> To post to this group, send email to cu...@googlegroups.com.
> To unsubscribe from this group, send email to cukes+un...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/cukes?hl=en.
>
>
--
Julien Biezemans - j...@jbpros.com
JBpro's Interactive - http://www.jbpros.com/
+32 495 60 32 79
It's a bug: https://github.com/aslakhellesoy/cucumber-rails/pull/113
Should be fixed in the next release.
Aslak
> I don't have any tags on my scenarios, and it seems to run when you
> don't.
>
You're welcome - hope this works for you
Would it possible to pass options to the DatabaseCleaner.strategy
= :trunaction call inside the database_cleaner.rb hook? I've placed a
copy of the setup into the local support dir for now to override it
for the @javascript tag before block, I needed to add the :except =>
[tables_here] as option and couldn't work out a nicer way to do it.