Running a test on an already opened browser

[Raj]

Hi Everyone,

I'm new to WebUI and I've couple of questions

1 - How I can make the WebUI to run a test on an existing browser instead of opening a new browser every time a test is executed
2 - How can I stop WebUI from closing the browser window after completing execution of the test.

Thanks

[Cody]

Hi Raj,

Our software can do the following:

1. You can use the "Run to Here" command (available if you right-click a step within a test) to run the test to a specific spot, then launch the recorder within the browser
2. You can use the Recycle Browser option to re-use the browser in test lists

   NOTE: This feature is only available within test lists

3. You can launch the recorder within an open browser window (see screen shot)

Currently, our software cannot do the two items you requested. Was there a specific reason you need to do the two following items:

• Run a test on an existing browser

  You can create similar feedback to this when using test lists

• Stop WebUI from closing the browser instance after test completes

  You can create similar feedback to this using the "Run to Here" option listed above

Please let us know what you want these two features to accomplish. It is always possible that what you want to do can already be done within WebUI, I'll just need a little more data on what you want the test project(s) to accomplish.

Best wishes,
Cody
the Telerik team

[Veera]

Hi Cody,
I also looking for this feature. This feature will be really help for us in automating only certain features or in other want to automate the app partially. Like using automated test for creating test data in some parts of the application.

Also this feature will be helpful for us in debugging our test more quickly. Every time when we execute the test it always starts from the scratch which often increases our debugging time. instead i can execute only the script which we feel is bugg or error prone.

hope i answered for Raj as well :)

Cheers,
Veera

[Cody]

Hi Veeraraghavan,

Thank you for the additional feedback. It sounds like you're looking for a faster way of debugging test scripts. What if we added a "Run test FROM here" option that would execute the test in the already opened recording window. Would that fit your needs?

All the best,
Cody

the Telerik team

[Veera]

Hi Cody,
I think that should solve the purpose... I am really happy to hear that

Thanks again for your quick response on this!!!

Cheers,
Veera

[Cody]

Hi Veeraraghavan,

This has been entered into our system as Feature Request 76243. I don't have an ETA when we'll implement this feature. Maybe it will be in our Q1 release next year, but I cannot promise right now. You may at any time ask for status on this feature request by this number.

Regards,
Cody

the Telerik team

[Raj]

Hi Cody,

We would like to have these features so that we can create multiple tests and run them as a batch. Running a test on an already opened browser would eliminate the prerequisite steps that need to be run before testing the actual test case. It sounds like we can achieve this with test lists, is there any documentation for creating test lists and running them.

Also, I can't understand the functionality of Recycle Browser option. How does it work?

Please let me know.

Thanks,
Raj

[Cody]

Hello Raj,

We have a general training video on tests list for our QA edition, but it looks like you're using the Dev edition is that correct?. You will need to create a Visual Studio test list instead. The bad thing about VS test lists is that Microsoft doesn't guarantee the order in which the tests will run. VS will run them in whatever order it feels like running them in. If you use the QA edition instead our test lists are run in the order you specify and QA edition also supports the Recycle Browser feature.

Unfortunately we don't have good documentation on the RecycleBrowser feature though it's pretty simple. When enabled a new browser will be launched for the first test in the test list and then stay open and reused for all subsequent tests in that test run. The browser window will then be closed after the last test in the test list executes. The setting is stored in the .testsettings file for VS 2010 and in the .testrunconfig file for VS 2008. I have attached a screenshot showing where this setting is kept.

All the best,
Cody

the Telerik team

[Avraham]

Cody,

I am constantly bumping up against these limitation as well - especially when debugging a script.
Scripters spend a great part of their time debugging scripts.
They cannot afford to keep restarting the application all the time and navigating back to the point of failure.

When a script fails the default behavior should be to stay where as is WITH the application at the failure point.
Telerik does the first part well (failed step is pointed at) but not the second as the browser closes.
The way one is forced to work with Telerik is extremely inefficient and all the time one gains on a great checkpoint creation model is lost in this phase.

Of course when Test Lists are executed the story is different - there, especially in unattended mode, closing the application is required.
So, there seem to be a need for the tool to work in two modes, Design (attended) mode (stop where failure occured) and unattended mode.

The natural way for automation engineed to work is:
  Script
  Try it
  Failure encountered (happens 95% of the times on non-trivial scripts or when users - like myself - are not experts)
  Debug the failed step
  Fix it
  Continue from fixed step *** This is where Telerik is missing the point entirely and miserably

Continue should come in the following flavors:
  Run from selected step (most of your competitors have that) in the usual scenario, selected step will the one you just fixed.
  Execute selected step only - allows you to check the state of the script & app (some of your competitors have that)

This would be a great addition to the tool (MUST FIX YESTERDAY in my opinion.)

Thanks

[Cody]

Hi Avraham,

I find this to be a very interesting case! I did discover that if you change the find expression for the "Plus de critères" link to what is shown in the attached screenshot then it works in all browsers. This actually is not correct but you can use it as a workaround until we fix it properly.

I have filed bug 101743 for this issue. Be aware that if you use the find expression in the screenshot, it may no longer work once we fix this bug. You should be able to simply re-record that step when you upgrade to a build containing this fix.

I have given you 1000 Telerik Points for this bug report.

Regards,
Cody

the Telerik team

[Cody]

Hello Avraham,

Please disregard my last post. It was meant for a different forum thread. My apologies.

I passed along your comments to our development team. They have been getting very similar comments from multiple customers lately. They have decided to make this feature request a very high priority for development. We will probably have something implemented in our Q1 release early next year.

Thank you again for your valuable feedback! We really do listen to our customers testing needs.

Greetings,
Cody

the Telerik team

[Avraham]

I vote for:
Run to Here (exists already)
Run Highlighted Step (this 'almost' exists and can be used when the execution options are displayed)
Run From Here (allow us to do it one step at a time)
This will improve usability of Web UI Tester a great deal

Bey

[Cody]

Hi Avraham,

Thank you for the feedback! I've logged your votes in our feature request lists that our product managers keep track of.

All the best,
Cody

the Telerik team

[Andrew]

Hi

Seems like this topic went to sleep for a while - time to wake it up.
I would like to see this feature available - particularly for debugging purposes.

If I'm in a 'test' and on a particular page in a browser I 'should' be able to simply execute the steps
I wish to without the tool starting a new browser instance - debugging as I go.

Regards

Andrew

[Ivaylo]

Hello Andrew, 

What version of Test Studio you are using? This is currently an available feature in newer versions of Test Studio. While recording a test you have the option to run selected steps. I have managed to record a short web test and while having the recorder launched I decided to execute step 2 only. You can see it here. If you can download the latest internal release by logging into your account (refer to the screenshot). 

If you feel uncomfortable using internal builds please note that our current official release has this feature as well, and our 2012 R1 is coming out next week. 

Greetings,
Ivaylo
the Telerik team

[dan]

Hi Cody,

A question about 'run to here'..

If my test script consists of several 'test as steps', how do I do a 'run to here' if 'here' is a step within one of the 'test as steps'?

Is it possible to have the 'run to here' start its execution from step 1 of the parent test and not step 1 of the 'test as step'?

 

thanks,

dan

[Konstantin Petkov]

Hi,

No, there is no such functionality available in the product. Basically the child test doesn't "know" anything about the parent one. Also the child test can be used as test as step from multiple other tests.

Regards,
Konstantin Petkov
Telerik by Progress