#291 ✓hold
Yugui (Yuki Sonoda)

Celerity support patch

Reported by Yugui (Yuki Sonoda) | September 13th, 2009 @ 07:56 AM

I rebased kamal's celerity branch onto brynary's master. And I modified it so that it can work with CRuby too.

My branch is http://github.com/yugui/webrat/tree/feature/celerity .

Celerity is faster than selenium. So it is an useful feature. In the branch, celerity support still has some duplicates with selenium support, so it might need refactoring. But I think the branch is enough usable.

Comments and changes to this ticket

  • Marc-André Lafortune

    Marc-André Lafortune October 21st, 2009 @ 02:59 PM

    +1 for Celerity support.

    While you're at it: Culerity too (should be quite easy if Celerity works).

  • Jeroen van Dijk

    Jeroen van Dijk November 3rd, 2009 @ 08:58 AM

    I also agree that webrat should somehow add Celerity support (and Culerity). I didn't check out this celerity fork.

    @Marc Adding Culerity support isn't that trivial. Celerity needs to be extended for Culerity (see core_ext in dstrelau fork). Since Celerity runs in a seperate JRuby process this needs to be done through the command line when initializing jruby or somehow. You might want to check out http://github.com/dstrelau/webrat, which I didn't get to work. Now I switched back to Selenium which I got to work with (I think) all webrat functionality with just a small hack Gist

    I would like to see an example application with javascript (source on github) which can be used to test whether all adapters succeed. This application would also serve as an example of best practises etc.

    Just my 2 cents.

  • Bryan Helmkamp

    Bryan Helmkamp November 15th, 2009 @ 05:01 PM

    • State changed from “new” to “hold”

    I want to support something like Celerity/Culerity in Webrat eventually, but I don't want to add more adapters before 1.0.

    There's a fair bit of work to be done to get Selenium and Webrat "core" behaving the same pre-1.0, which I'd like to focus on before expanding the adapter set. There's also an API pass that should be done before that timeframe.

    So I'm going to mark this as "hold" for now, and please do continue to play with this functionality. Once 1.0 is out the door, or at least close, let's revisit.

    Cheers,

    -Bryan

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.

New-ticket 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.

Shared Ticket Bins

Pages