Hi,
First of all, I want to say the Web UI test studio is great product. However I think I can’t find a few features that will make it feasible to be used to in our test environment. I am using Web UI Test studio Q2 2009 trial.
I have been trying to write the tests using the test canvas. The tests should be able to recorded and maintained by testers. They do not have programming skills, so I only try to do things relying solely on the GUI provided by the test studio.
Test explorer:
· I am missing the ability to copy and paste a step in test explorer. This is a huge productivity killer. Open in xml, copy and paste xml step can do the trick, but it’s very prone to error and maybe too much to ask for non technical folks.
· If I accidently delete a step there is no way to undo it.
· It’s not possible to insert steps in the Test explorer directly. If I know I can use certain element in the Elements explorer. The only way to do it with recording surface and repeating the steps to get there in that state to have the element you want will a lot of time. Maybe it’s possible to make a snapshot of the DOM for use later?
· For reusability of the steps I thought I might just work around it to break it into separate test. However the add “Test as step” pull down show everything unsorted. Pretty hard to find things in there. Maybe it should be possible just to drag a test in it, and then it will know you wan to call the test step.
· Sometimes you want to be able to replay the tests in the recording surface, so you can modify the test steps at that state. This is not possible.
· There should be a feature to extract test steps in test explorer as a separate Web UI test.
· When “Enable annotation for quick execution” is set. It loops and annotates every parent element when I want to test the visibility of 1 child element. It should only show the annotation of the steps.
· If I use relative URL, “Quick execute test against selected browser” and “Re-capture test browser states to enhance test maintenance” don’t work. It only works in test view.
· There is no event indicating to continue after a page finish loading. For example when testing for existence of an element on other page after navigate to there. It sometimes either wait for nothing or sometimes just doesn’t wait long enough for the page finish loading. I know you can set the wait time very long. However when someone deletes a button on a page, it just pointless to wait even after it finished loading. It should fail immediately instead. I know there are cases that this is not applicable with and timer. So it should have different wait model. Wait after page loaded and check immediately or wait an amount of time after page loaded or wait absolute amount of time after an action.
· It’s not possible to add something like a wait that is not dependant on anything at all. Sleep timer or something.
I am hoping all this is possible and I am just missing something. Looking forward to use this product.
1 Answer, 1 is accepted
Thank you for your compliments towards WebUI Test Studio, we also appreciate your feedback on the product and hope you find the tool useful for your testing purposes.
Your suggestions are great ideas which we'll add as feature requests and look to implement in future versions of the product. Some of them have been brought up in the past, but we'll re-log them for reference.
The “Enable annotation for quick execution” parent annotation behavior you describe does sound odd, so we'll definitely look into that.
For extracting test steps to create a new test, as a possible work around, you can copy/paste the test and delete the steps you don't want, as you can hold Ctrl and select groups of steps for deletion.
Thanks again for your feedback, please let us know if you have any other suggestions or run into any other issues.
Regards,
Nelson Sin
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.