I\'m quite new to RoR and programmed a couple of things before discovering Test-Driven-Development. So I tried to write some tests with guard-rspec and capybara. All was fine, but I got some deprecati
I\'m running a Rails 3.0.7 project with Cucumber and Capybara and I have a step definition that checks if a flash[:error] exists:
So I have this spec describe \"visit /signup\" do before(:each) do get signup_path end it \"has an email input field\" do
It fails to click on anchor tag <a href=\"#\" onclick=\"...some js function...;return false;\"> (I know <a href=\"#\"> is a bad practice.)
I\'ve just upgraded to Rails 3.1 and now when I try and run my cucumber (capybara) tests with the @javascript tag I get the following error:
inspired by the episode of railscast (http://railscasts开发者_C百科.com/episodes/275-how-i-test) i tried to add some request specs to my app.
When I run my test with the features, steps, and HTML below the test executes without error (until it fails on the assertion steps), but I can see that no change occurs to the drop-down selects.What a
I\'m trying to write a Sign in integration test for my app + devise by using Capybara. 开发者_运维问答Here is what I have so far:
I\'ve gone round and round trying to come up with the cleanest / easiest way to write request specs for certain pages of my site. I basica开发者_C百科lly need a way to get Capybara to load pages that
I have the following test: it \"I can Sign Up with Facebook\" do visit new_user_registration_path click_link_or_button \'Sign up with Facebook\'
加载中,请稍侯......