It follows the specific model around as well. If I change order of the
fit
table or not (the fit table has 20 rows of different models all being
exercised the same way, they are part of a replication tool that copies
a
database). The only time it passes is when I run the feature
independently.
I guess I’ll have to look at what the difference is between ( rake
features
|| cucumber features/* ) and cucumber features/specific.feature and try and
hunt down what beginning state I could be missing.
I guess I’ll have to look at what the difference is between ( rake
features || cucumber features/* ) and cucumber
features/specific.feature and try and hunt down what beginning state I
could be missing.
If you are using cucumber with rails and used the rails generator you
should find in your generated features/steps/env.rb file (In the latest
cucumber version 0.1.9 this is in features/support/env.rb):
Yes, I was already using the transactional fixtures. This wasn’t the
problem.
The final problem was actually two code bugs. One on a trigger in the
database and the other was a namespace confliict in my code.
Those two combined basically had me totally confused
It follows the specific model around as well. If I change order of the
fit table or not (the fit table has 20 rows of different models all being
exercised the same way, they are part of a replication tool that copies a
database). The only time it passes is when I run the feature independently.
Are you running using Webrat or Selenium/Watir?
Yes! Running webrat, latest trunk version (as of yesterday anyway).
Though
this feature doesn’t use it specifically, webrat is loaded with a
require
line in the features/steps/env.rb file.
This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.