What I've encountered is that IE, FF and Chrome handlle our login dialog differently. I created a "Test as Step" for our login dialog. The "Test as Step" consist of navigating to a URL and populating the username and password. The internal component of our app only supports FF and Chrome, so when I create the internal scripts the test is created against the IE browser which behaves differently than FF and Chrome.
IE handles our login as a dialog, and after the values are successfully entered the WebUI continues through all the remaining steps successfully (of course, because this is the browser I created the test script against).
Firefox treats our login as a dialog. When the WebUI script is executed and after the login values are successfully entered, the browser displays a prompt asking if the values should be remembered. The WebUI test script fails because it doesn't have this step.
Chrome on the other hand treats the login a a element layered on top of the browser default home page. When the WebUI script is executed against Chrome the WebUI never populates the username and password. So the test fails on the first step and all the failure says is "Step did not execute". Not very informative.
Am I going to have to create Login "Test as Step" script for FF and a seperate one for Chrome?
Do I have the option to create my test script in Firefox or Chrome, and not Internet Explorer?
IE handles our login as a dialog, and after the values are successfully entered the WebUI continues through all the remaining steps successfully (of course, because this is the browser I created the test script against).
Firefox treats our login as a dialog. When the WebUI script is executed and after the login values are successfully entered, the browser displays a prompt asking if the values should be remembered. The WebUI test script fails because it doesn't have this step.
Chrome on the other hand treats the login a a element layered on top of the browser default home page. When the WebUI script is executed against Chrome the WebUI never populates the username and password. So the test fails on the first step and all the failure says is "Step did not execute". Not very informative.
Am I going to have to create Login "Test as Step" script for FF and a seperate one for Chrome?
Do I have the option to create my test script in Firefox or Chrome, and not Internet Explorer?
1 Answer, 1 is accepted
0
Hello Kimberley,
You are correct; each browser handles the logon dialog differently. Test Studio was designed to interface with dialogs from each of the four supported browsers. These interactions should be recorded automatically as "Handle '___' dialog" steps, but if not you can add them manually from the Dialogs button in the Add ribbon.
Unfortunately it seems you have found a regression with regards to the Chrome logon dialog. I replicated the issue and filed a bug for it. You can follow the PITS Issue by its ID: 6411. Unfortunately I do have a workaround to offer you for Chrome before this regression is fixed.
I also tested a logon dialog with Firefox 3.6 and 4. I could not reproduce the browser prompting to remember the credentials. I searched for a setting within the browser that might be responsible for this behavior, but nothing jumped out at me. So please tinker with the settings on the Privacy and Security tabs and try again.
Currently you can only record in IE and there are no plans to change that. However, soon we are adding the ability to craft test steps without coding, but outside of a browser. You use the recording surface combined with our built-in DOM Explorer to add elements into the repository. Next, you select the element within Test Studio and select "Add Step." This allows you to add both action and verification steps to your test outside of the browser. So, as long as the elements are located in the page DOM, this could be a viable alternative.
Kind regards,
Anthony
the Telerik team
You are correct; each browser handles the logon dialog differently. Test Studio was designed to interface with dialogs from each of the four supported browsers. These interactions should be recorded automatically as "Handle '___' dialog" steps, but if not you can add them manually from the Dialogs button in the Add ribbon.
Unfortunately it seems you have found a regression with regards to the Chrome logon dialog. I replicated the issue and filed a bug for it. You can follow the PITS Issue by its ID: 6411. Unfortunately I do have a workaround to offer you for Chrome before this regression is fixed.
I also tested a logon dialog with Firefox 3.6 and 4. I could not reproduce the browser prompting to remember the credentials. I searched for a setting within the browser that might be responsible for this behavior, but nothing jumped out at me. So please tinker with the settings on the Privacy and Security tabs and try again.
Currently you can only record in IE and there are no plans to change that. However, soon we are adding the ability to craft test steps without coding, but outside of a browser. You use the recording surface combined with our built-in DOM Explorer to add elements into the repository. Next, you select the element within Test Studio and select "Add Step." This allows you to add both action and verification steps to your test outside of the browser. So, as long as the elements are located in the page DOM, this could be a viable alternative.
Kind regards,
Anthony
the Telerik team
Explore the entire Telerik portfolio by downloading the Ultimate Collection trial package. Get now >>