If you're using the WebKit formatter, or any other formatter for that matter, add this to the @.tm_properties@ either in your $HOME (to apply it to all RSpec bundle output), or in a specific project's @.tm_properties@ file:
I'm excited about the possibilities of tweaking the editor's behavior on a directory-by-directory basis.
…workaround for having to build Chrome for iOS on top of the built-in iOS WebKit engine, the browser needs to use some tricks, such as using AJAX to hit a local HTTP endpoint, to do things like URL verification. Our instrumentation was somehow triggering a bug that caused Chrome for iOS to believe that valid URLs were bad. For now, we have disabled AJAX timing for Chrome for iOS, but we plan to bring it back soon with workarounds for this issue.
‘a.highchartsObject' é …
…:webkit if you want to choose the driver on a per scenario / describe basis. The same applies to @in .
If you're on, when you first run tests using capybara-webkit the OS X firewall might go a little crazy since it works by connecting over a socket. Just approve it and you're on your way.
You may also have issues if you're using transaction fixtures. If so, read the " Transactional Fixtures" section of the Capybara README.
…'s, you need Mozilla's hiring a research engineer to help them build Rust .)If you want to hack on the , or WebKit, you need . Come to think of it, I saw another interesting job ad which required a C background -
I've also seen some very inspiring work in , and everything runs on C.
Anyway, just to end with some useful tips, I haven't gotten into the classic text yet, but I've found …
This solved the problem for Webkit, but not for latest versions of Firefox. Mozilla seems to need at least 15ms timeout, and even this value varies.
A better solution for both engines is to trigger "layout". This is done here by reading clientLeft from an element. There are other …
…use a "transaction" strategy to reset our test environment with:: Webkit. Instead we use the "truncation" strategy, which simple blows away all of the data after each test run.
Why bother with transactions?
Truncation will work just as well with Database explains: "For the README libraries the fastest option will be to use :transaction …::Test as transcations, so why introduce the complexity of two different configurations? The
Codebrag - code review tool with git and support.
Capybara Webkit 1.1.0: - A couple of new features for this automated test tool. and Better ClickFailed debugging
How - memory table saved the day by tossing an entire table into RAM.
Using - How to set up your scripts with Thor as a backbone. as Rake Replacement
If you pop open this file, you'll get to clearly see what Capybara Webkit did when you were trying to click on that button:
There's even a beautiful mouse cursor illustrating the exact location you attempted to click.
If you're using Capybara Webkit 1.0.0, you can update easily.
Edit your Gemfile : gem 'capybara-webkit', '~> 1.1.0'
Update your bundle: % bundle update capybara-webkit
And you're good to go!
We also included …
Thank you to the many Postgres committers for a rock-solid and always-improving database.
Thank you to Allen Ding…