Geek Answers Handbook

Why do my cucumber scripts fail when the steps are executed together, but are transmitted singularly at startup?

When I run the scripts of the cucumber as a whole or with the command: cucumber I get 7 unsuccessful steps. When I run them individually with a work tag in the process, they go fine.

I don’t think this is a database problem .. I work with transactions, and I also tried to work without cleaning and clearing the database using the database cleaner .... still does not help.

I tried to start the debugger, but it does not work when I run the cucumber command. It only works on startup with a work tag:cucumber -p wip

I thought it might happen that everything works too fast, and capybara is not checking things properly?

Any ideas?

+5
source share
1 answer

Eureka! I had the same problem for a while - my tests became slower and slower the more I added - also some tests will be random, but only when starting as a whole set - after completing my tests I would just run again and again! everything went. Very disappointing - but the most unfortunate part was speed - lately I upgraded to a snow leopard and compiled everything to 64 bits. Result? My tests went from 7 minutes to 32!

: 64- , , , , , . №2? Webrat , /, javascript, .

, jruby java, 512 . JRuby java- , jruby . , java , . ? :

JRUBY_INVOCATION="jruby -J-Xmx1024m" cucumber

, 7 ! ? ? , !

+2

More articles:


All Articles