Usage when submitting forms

[natritmeyer]

Usage when submitting forms

[andyw8]

(edited the original post to correct a few things)

[tmertens]

@andyw8 Your implementation looks correct. You must explicitly specify which page you are interacting with.

[andyw8]

Ok. So how do I avoid using a page model which potentially doesn't correspond to the page that was actually rendered? Should I be checking displayed? before calling load in each place where I expect to be redirected?

[tmertens]

Can you give me an example? I'm not sure I understand how you could
'potentially' use a page model different than the page expected. If you are
writing tests, you should know in advance what page you will be landing on
after performing some action.

e.g. If I click the 'Login' link on the home page, I expect to be
redirected to the login page and hence I know to a LoginPage object for
interactions corresponding to the Login page.

Can you provide a simple example of where this fails for you?

On Fri, Oct 11, 2013 at 3:18 PM, Andy Waite [email protected]:

Ok. So how do you avoid using a page model which potentially doesn't
correspond to the actual page being rendered? Should I be checking
displayed? before calling load in each place where I expect to be
redirected?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-26168973
.

[tmertens]

I should add that if you are expecting to be redirected by some action
(e.g. home_page.login_link.click ), you shouldn't be calling
'LoginPage#load' at all as it will override the login_link click redirect
action and simply tell Capybara to load the login page's URL as specified
in the LoginPage class rather than following the actual redirect from the
click.

e.g. assuming we have HomePage and LoginPage classes:

let(:home_page) { HomePage.new }
let(:login_page) { LoginPage.new }

context "Login Link"
  scenario "redirects to the login page"
    home_page.load
    expect(home_page).to be_displayed
    home_page.login_link.click
    expect(login_page).to be_displayed
  end
end

On Fri, Oct 11, 2013 at 3:25 PM, Tim M [email protected] wrote:

Can you give me an example? I'm not sure I understand how you could
'potentially' use a page model different than the page expected. If you are
writing tests, you should know in advance what page you will be landing on
after performing some action.

e.g. If I click the 'Login' link on the home page, I expect to be
redirected to the login page and hence I know to a LoginPage object for
interactions corresponding to the Login page.

Can you provide a simple example of where this fails for you?

On Fri, Oct 11, 2013 at 3:18 PM, Andy Waite [email protected]:

Ok. So how do you avoid using a page model which potentially doesn't
correspond to the actual page being rendered? Should I be checking
displayed? before calling load in each place where I expect to be
redirected?

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/51#issuecomment-26168973
.

[andyw8]

Got it! Wasn't obvious from the README, I'll send a PR to add that info if I have a chance.

[natritmeyer]

@andyw8 happy for me to close this? Good to hear from you again :)