Secured internal pages with authentication
I read your support blog about how to enable screenshots of internal pages. That works great for the landing page of our website, but what about internal pages?
The scenario is this: I have a page that users can only see when their authenticated that I need to make sure works on different browsers so I want to use cross browser testing. If I put in the URL of the page that needs to be visited there is no login information, and I put the URL of the page where users log in then I don't have a way to tell the screenshot to then go to the authenticated page.
Please let me know how I can accomplish this.
Thanks
Delicious
Digg
StumbleUpon
Propeller
Reddit
Magnoliacom
Facebook
Google
Yahoo
Take a look at this blog post:
http://crossbrowsertesting.com/blog/cross-browser-checks-pages-behind-us...
The screenshot system has an 'advanced options' link that allows you to specify login profiles. This login profile will navigate the screenshot engine though your login process, and will then make a screenshot of the requested page.
A couple things:
1) While setting up the login profile, just take a screenshot of one browser until you get it right. This will keep you from burning time by testing a ton of browsers with a login script that is not working yet.
2) For form based authentication, the login scripts try to automatically determine which element the username, password, and login button are. If it cannot autodetect these, it will allow the customer to specify them. If you have any trouble setting this up - let us know. Send an email via the 'contact us' form under the support tab with the page you want to take a screenshot of, the user name, and the password. We will help setup this login profile.
Thanks
Tony
Tony, I'm going to interject here since I'm a little more familiar with the login process on screenshots and the blog you referenced doesn't answer his question.
Yes, currently the page you want the screenshot of and the page you need to login to must have the same URL. This works if when you request a URL for screenshots, that URL automatically recognizes that you are not logged in and either takes you to a login page, or has a login form on the page. The other case in this process is that when the login form submits to a different URL than the one requested originally, the screenshot process reloads the original requested URL.
Example:
You request screenshots for http://mywebsite.com/non-public-page.html.
If this pages doesn't have a login form or doesn't redirect to a page with a login form, then the login procedure will not work.
If it does have a login form, let's say the authentication completes but takes you to a landing page of http://mywebsite.com/login-successful.html
The screenshot driver will then reload the original URL at http://mywebsite.com/non-public-page.html and begin the screenshot process.
I agree that login profiles should specify a separate URL for login and upon completion should then load the URL requested for screenshots. We may update this is relative near future.
Thanks,
Luke