Webrat kills selenium rc while it hasn't started it
Reported by Fjan | November 25th, 2009 @ 07:52 AM
This is not so much a bug as a feature request to make Webrat even more awesome than it already is.
When using Webrat with Selenium it fires up 2 servers and kills them afterwards. When writing a lot of Ajax test I would like to leave the selenium server up and running to avoid the jetty startup time. Currently, if I start up selenium RC by hand then webrat will correctly use it. The problem is that Webrat will kill selenium RC at the end of the test task even though it didn't start it.
It would be great if Webrat would only kill selenium RC if it was the process that actually started it. (Alternatively, some kind of start-up option that indicates to leave selenium RC running would be fine too)
No comments found
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Ruby Acceptance Testing for Web applications.
People watching this ticket
- Nobody is watching this ticket.