floehopper + capybara   14

dockyard/capybara-email
"Test your ActionMailer emails with Capybara".
capybara  email  testing  ruby 
11 weeks ago by floehopper
Saving Time with CI
I'm unconvinced this is a good solution - in fact I think it breaks the whole idea of continuous integration. I think it would be better to look at other ways to have a test suite that ran fast enough that each developer is happy to run it locally.
continuous  integration  rubyonrails  jasmine  capybara  webkit  cucumber 
february 2012 by floehopper
capybara-webkit
"A capybara driver that uses WebKit via QtWebKit".
capybara  ruby  testing  webkit 
january 2012 by floehopper
Testing AJAX with Test::Unit
"So, I figured with a little capybara and a little therubyracer, I could test my javascript with real route calls".
testing  javascript  therubyracer  capybara 
october 2010 by floehopper
Issues - jnicklas/capybara - GitHub
"No, that doesn't make sense either. Embedding V8 in Ruby like therubyracer does, and then combining it an emulated DOM (env.js), has potential as a Capybara driver, but that's basically the same as capybara-envjs (except for V8 over spidermonkey)".
capybara  env.js  v8  dom  therubyracer  ruby  driver 
october 2010 by floehopper
Common implementation and tests across the rhino and johnson versions of envjs - Env.js | Google Groups
Question from Chris about why the envjs codebase used by capybara-envjs has diverged from the Rhino related version of envjs.
env.js  capybara  cucumber  fork  diverge  testing 
september 2010 by floehopper

Copy this bookmark:



description:


tags: