[Solved] Questions regarding executing tests

[Vincent]

Hello,

When we try to execute tests we have recorded using the recorder an "about:blank" page appears. Does this mean that the beginning step is always expected to be that you navigate to the webpage you will be testing? Is it possible to start the execution of your tests in a page that has already been opened, or do you always have to navigate there first using your script?

Thanks,
Vincent

[Missing User]

Hello Vincent,

The current and next release (2.0) of WebUI requires the launching of a new browser instance by the test script. I believe there is already a feature request to be able to connect to an existing instance of a browser, but I'll check and log this if necessary. Thanks for the feedback.

Best wishes,
Nelson Sin
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Vincent]

Do you know of any work-around to connect ot an existing instance of a browser?

[Missing User]

Hi again Vincent,

Unfortunately, there really isn't a workaround for this currently. Was there a particular scenario you were trying to automate? If you can give us a description or a step by stpe repro, we can possibly try other things that may work for you.

Greetings,
Nelson
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Vincent]

There would be an issue if someone has longer tests, however I think the solution to that would be to make smaller tests.

Currently though, the issue we have is that we must log in through an external application to access the application we will be testing.

[Missing User]

Hi againVincent,

So I would assume the external app launches an authenticated browser session on a successful login attempt?

Also, it wouldn't be possible to launch a browser in WebUI, be prompted to manually login via the external app, then continue testing with the WebUI Test?
 
And only that browser instance launched/authenticated from the external app is logged on, including other tabs launched on the same browser?

Greetings,
Nelson
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Vincent]

Thank you for your responses Nelson.

After you log in to the external application, the user launches another browser with our application in it.

Is your suggestion to launch the browser using WebUI, then manually put in our login credentials? That would be problematic since we then have to launch another browser. It would also make maintenance of scripts extremely hard.

[Missing User]

Hello again Vincent,

It seems from the order of login operations that a manual login or an automated login via some other test script into the external app, then starting a test in WebUI that would launch a browser could possibly work.

We are still looking to incorporate the ability to connect to an existing browser. But it looks like logging in to the external application via some other means, then having WebUI launch a browser maybe the only work around at this point and it's quite understandable that this may not be ideal for you.

Regards,
Nelson
the Telerik team

Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.

[Vincent]

Hello all,
Does WebUI Test Studio have the ability to write and execute tests on existing webpages yet?

Thanks,
Vin

[Missing User]

Hello again Vin,

Unfortunately, the current release does not have this feature, but we are still looking to support this in the future.

So does manually logging in with the external authentication app, then executing WebAii tests in WebUI against your web app not working?

Are the browser instances being launched by WebUI not being recognized as authenticated even with the manual external app login?

Greetings,
Nelson
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.

[Vincent]

Hi Nelson,

Thanks for the response. We would be able to start from the manual log in each time, however it seems like an unrealistic way to write/run/maintain scripts for our application. There's no quick starting point in our application, a lot of steps are dependant on eachother.

Thanks,
Vin

[Missing User]

Hello again Vincent,

I understand that manually logging in is not ideal, but since there currently is no option to attach to existing browser in WebUI, this may be the only option available.

If possible, though, you can add custom code in WebUI that executes the external authentication application before WebUI launches a browser. WebUI can then continue to use the authenticatted browser.

The following is the template for a custom coded step in a WebAii Test:

[CodedStep("MyCustom Step Description")]
public void MyCustomStep()
{
// Login authentication code here
}

If you are able to add code to automate the browser authentication process, then it would be easier to execute and maintain WebAii tests.

Regards,
Nelson
the Telerik team

Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.