Capybara: Acceptance test framework for web applications
1–10 of 20 posts
Re: Capybara: Acceptance test framework for web applications
#2so, yet another later on top of seleniun or I'm missing something?
Re: Capybara: Acceptance test framework for web applications
#3so, yet another later on top of seleniun or I'm missing something?
I think you're missing a "y" ;)
Re: Capybara: Acceptance test framework for web applications
#4I was disappointed that the subtitle wasn't "tighter and tighter testing". http://i.imgur.com/1aD54YR.jpg
Re: Capybara: Acceptance test framework for web applications
#5Sigh - more ruby rubbish. There are much cleaner and better and frankly less 'magic' tools available. Find them, use them, say no to ruby!
Re: Capybara: Acceptance test framework for web applications
#6If you liked this, you might also like the following: https://github.com/webdriverio/cucumber-boilerplate , not as detailed as Capybara but similar
Re: Capybara: Acceptance test framework for web applications
#7Capybara has been a part of my/our workflow for a while; I'm curious why this is on the frontpage -- is there a specific update I'm missing?
Either way, I really enjoy Capybara -- especially being able to jump between different drivers for various reasons.
Re: Capybara: Acceptance test framework for web applications
#8so, yet another later on top of seleniun or I'm missing something?
Selenium is one of the many drivers it can use. This is a DSL for driving a browser.
Re: Capybara: Acceptance test framework for web applications
#9Capybara's a great too that we use heavily at https://www.incoin.io. One of the hangups we had is with multiple API endpoints being hit for a particular page. In some instances the first API request would finish and Capybara would assume that loading is done, when really there's another API request pending meaning our promises haven't yet finished and tests would fail randomly.
In order to prevent this you need to delay Capybara's processing so that all requests have finished using a request counter. Information is here: http://tonyhb.com/stop-treading-water-with-marionette-and-ca...
Other than that, Capybara is absolutely amazing. It doesn't replace manual UI testing by any means, though it provides a lot of confidence knowing we haven't broken critical components of our app.
Re: Capybara: Acceptance test framework for web applications
#10Sigh - more ruby rubbish. There are much cleaner and better and frankly less 'magic' tools available. Find them, use them, say no to ruby!
Care to at least elaborate which tools you're referring too? That way you'd at least contribute something to the discussion but a snark.