Resolve testing issue where selenium is poluting our cucumber DB
Reported by baphled (at boodah) | May 11th, 2010 @ 04:23 PM | in 0.8.2
It seems that once we run selenium it is saving its data to the test environment, making our cucumber steps fail once selenium has been run. Though the two should be using different DB's it seems this is not the case.
This should also be taken into account when running cucumber tests and they fail.
Comments and changes to this ticket
-
baphled (at boodah) July 4th, 2010 @ 02:06 PM
- Milestone set to “0.8.2”
- Milestone order changed from “0” to “0”
-
baphled (at boodah) July 15th, 2010 @ 11:46 AM
- State changed from “new” to “resolved”
- Milestone order changed from “14” to “0”
Issue seems to be resolved with the latest version of cucumber and rspec, not quite sure how this was fixed but modified the enhanced settings to use db_cleaner
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Bridging the gap between clients and developers
baphled (at boodah)