The new standalone WebUI Test Studio 2010 (its official launch was announced in my previous post) includes a couple of built from scratch modules which we’ll describe in this blog. I’ll start with the important features of the Test Lists in the QA Edition.
Record and execute a single test
Recording and execution of a single test case is pretty straight forward thanks to a cool hint on the startup screen:
With the QA edition you can quickly create a new project, add a test in the project and launch the recorder for your first test.
You can also add as many tests as you want in the Project Explorer (Project View) and record your scenarios, then execute them one by one. And if you need to execute a group of tests simultaneously, that’s where the Test Lists section comes into place.
Creation -- Choose between Static and Dynamic test lists
In WebUI Test Studio 2010 QA Edition you can create two types of test lists – “static” and “dynamic”. Once a project is loaded simply switch to the Test List View and choose to add the respective list type (the “Add” commands on the left).
Standard Test Lists
To create a static or simple test list you need to specify its name and then select a set of tests from the current project to add to the new test list. The standard Add Test List dialog looks like this:
So you have the project tree to the left and the list of tests to the right. Type a name for the list, select and add as many tests as needed (multi-selection is enabled), and you are good to go. If you select a folder node to be added, all the tests from this folder (and its sub folders) will be added, as well. As simple as that!
[Note] We currently don’t allow adding one and the same test twice in a test list. If you, however, overcome this feature (take it as a challenge), please file a bug – we’d appreciate it! J
The tests in the test list are executed in the same order you’ve listed them when creating the test list. To be able to update the exact order in the list, we expose the UI to reorder the tests (e.g. move one before or after another). This is possible either upon creating the test list or after the list is created – from the common Test List View section.
You also see an overview of the tests from the selected test list in the right GridView.
Dynamic Test Lists
The dynamic test lists are the advanced way to define your set of tests. This is accomplished by the rules you add to filter all the tests in the project. Since there are a couple of nice features here, let me share details about the dynamic test lists in a separate post.
Editing Selected Test List
The Test List View also provides the following options to configure the test lists:
Edit List – add more tests/rules or rename the object. Double-click the item in the GridView will load it in edit mode, too.
Edit Settings – Each test list has its own settings. One can configure settings such as whether to annotate the execution, set the browser to execute against, set the base URL for all tests and many more.
Clone List –adds a copy of the selected test list. This is useful when you need a single change in the settings for the same set of tests such as execution against a different browser.
Delete – sure, one may not need a certain test list anymore.
Select a test list and click the Execute button to run it. It will run all the included tests as configured by launching the browser and producing the Run Result for you. We persist the result on the disk so whenever you load the project again, it will still be there. The run result management section is another big topic I’d like to dedicate a post about.
The Project Dashboard
When you turn on the Dashboard mode in the Project View screen you get the project test lists and run results on the right.
This is an overview and a shortcut at the same time – double-click will bring you to the respective view (Test List or Run Results) and get your choice selected there.
I hope this helps! Stay tuned for more posts on the WebUI Test Studio new cool features.