I am setting up our tests with building blocks, I could have:
1. login scenario
2. menu navigate scenario
3. fill in a form scenario
In order to get to 3, 1 and 2 must be run. So what would seem more natural while developing the tests (not for regular runs for which the run and drop session makes sense) is to be able to run 1, keep browser session open, run 2, stay open, and now work on recording 3. But now what happens is that in order to record 3 I need to manually do the actions of 1 and 2 from the recording surface to get to the right starting point.
I suspect I am missing something in the paradigm here and recognize the possibility that I'm asking the wrong question to solve my problem. :)
(We're evaluating WebUI which looked really promising for what we want to be doing.)
Steve
6 Answers, 1 is accepted
I suspect what you really need is learn about and use our "Connect to open browser" feature as shown in the attached screen shot. The idea here is that you can manually launch IE, manually perform your login and navigate to your starting point, then attach our recording to this already open browser window and record your test 3 as you have described (filling in a form). Will this fit your needs?
Kind regards,Cody
the Telerik team
Rank 1
If I'm understanding WebUI paradigm correctly, what I want is to be able to both RUN (any file) and RECORD (any file) from the same browser session.
Steve
p.s. Apologies for late response, I was on vacation.
The manual you are referring to is over a year old now. The Connect to Existing Browser feature was added after that manual was published. Here's a training video on it. We have lots of training video's here, KB articles here, and a brand new Users Guide about to go live here.
Greetings,Cody
the Telerik team
Register Today!
Rank 1
That is, I want to run test 1 (ex. login to application) and build test 2 upon the status after 1 was run. But what happens is that 1 runs and then closes the browser upon completion. A lot of test development is blocks that build upon a given browser-application status.
Steve
Back from vacation. :)
My recommendation is to follow these steps:
1) Open your Login test
2) Using the Run To Here feature to execute all the steps of your Login test. Say that test has 14 steps, right click and step 14 and select Run To Here.
That will launch the browser, execute the steps 1-14, then switch into Record mode. From there leave the recorder browser open and create as many new tests as you need.
Will that work for you?
Cody
the Telerik team
Register Today!
Rank 1
Hi Steve,
Here is another way which may accomplish what (I think) you want to do. This is the way I have resolved this issue for our application.
Login test
All steps to login.
Menu navigation test
If (not logged in)
{
Call login test
}
Execute Menu navigation steps.
Fill in a form test
if (not logged in)
{
Call login test
}
if (not on correct page)
{
call menu navigation test
}
Execute steps to invoke form and fill it in.
This allows you to run each of the tests independently and it also allows you to chain them together. Each test executes only those steps that it needs to depending on the scenario. You do need to implement the "not logged in" and "not on correct page" based on your application. Both will have to be a single verification check as WebUI does not support custom verification tests).
Another advantage of the above is that it also allows you to debug failures in child tests when running the parent tests (as you know, WebUI does not currently allow you to debug into a child test from a parent test).
Hope that helps,
Shashi