Skip to content

Instantly share code, notes, and snippets.

View artm's full-sized avatar

Artem Baguinski artm

  • Performation B.V.
  • Emmen, NL
  • 18:25 (UTC +02:00)
View GitHub Profile
nl:
devise:
failure:
invited: "U bent reeds uitgenodigd, accepteer de uitnodiging die u heeft ontvangen per mail om uw account te accepteren."
invitations:
send_instructions: "Een uitnodigingsmail aan %{email} is verstuurd."
invitation_token_invalid: "De uitnodigingscode is ongeldig!"
updated: "Uw wachtwoord is ingesteld. U bent nu ingelogd."
updated_not_active: "Uw wachtwoord is ingesteld."
no_invitations_remaining: "Geen uitnodigingen over."
@pezz
pezz / renoise.md
Last active November 23, 2022 15:28
How to use Renoise on a system without f*#$ing it over and doing your head in
@juliocesar
juliocesar / testing_front_end_rspec_capybara.md
Created October 21, 2010 23:51
Testing front-end for a Sinatra app with RSpec and Capybara

Testing front-end for a Sinatra app with RSpec and Capybara

I've used Cucumber quite a bit on my last job. It's an excellent tool, and I believe readable tests are the way to the future. But I could never get around to write effective scenarios, or maintain the boatload of text that the suite becomes once you get to a point where you have decent coverage. On top of that, it didn't seem to take much for the suite to become really slow as tests were added.

A while ago I've seen a gist by Lachie Cox where he shows how to use RSpec and Capybara to do front-end tests. That sounded perfect for me. I love RSpec, I can write my own matchers when I need them with little code, and it reads damn nicely.

So for my Rails Rumble 2010 project, as usual, I rolled a Sinatra app and figured I should give the idea a shot. Below are my findings.

Gemfile