Jason Pritchard
Top achievements
Rank 1
Rank 1
Jason Pritchard
asked on 21 Jun 2010, 12:38 PM
Hello
This weekend I have looked into what this product (QA) can do and how it can be used by our company. I am very impressed with the robustness of the application and how it is able to test client facing(front end) business logic. However I am confused at why there are multiple browsers being used and targeted. From what I can tell it checks the controls ID when verifying data and content and not the layout. So,.. Across all browsers, all controls will be rendered etc. Thus all test will pass across all browsers or fail for all browsers, but the look and feel across all browsers may be different, which is one of the big issues when doing web development. My understanding is that this is a great tool for testing business logic etc but can it be used to verify look and feel across browsers. Can page load time be measured and tracked overtime to ensure that our site does not lag as a result of new data loads or upgrades to controls. Is there a place where we can get exising sample tests demostrating all the features this product can do across a sample site. I use the samples on the Demos.Telerik.com all the time for our ASP.NET examples as a great resource.
I am triing to buid a case for purchasing this product and know that these are the types of questions I will be facing. Also Besides ease of use and not Requireing a VS License, is there any main advantages over QA / Dev versions. I have seen the comparision slides and they seem to do the same thing in both just one is not targeting developers. Is there any advantage to geting dev version. We currently have 3-4 Licenses (Not sure exact number or if other departments have licenses).
I have watched a majority of the videos and went through the FAQ and some of the blogs but still have questions.
Thank you for your time.
PS: Also.... When you goto tv.Telerik.com and click browse and choose automated testing tools.... the Page fails....
Here is the link that fails. http://tv.telerik.com/error?aspxerrorpath=/products/automated-testing-tools/browse
Jason
This weekend I have looked into what this product (QA) can do and how it can be used by our company. I am very impressed with the robustness of the application and how it is able to test client facing(front end) business logic. However I am confused at why there are multiple browsers being used and targeted. From what I can tell it checks the controls ID when verifying data and content and not the layout. So,.. Across all browsers, all controls will be rendered etc. Thus all test will pass across all browsers or fail for all browsers, but the look and feel across all browsers may be different, which is one of the big issues when doing web development. My understanding is that this is a great tool for testing business logic etc but can it be used to verify look and feel across browsers. Can page load time be measured and tracked overtime to ensure that our site does not lag as a result of new data loads or upgrades to controls. Is there a place where we can get exising sample tests demostrating all the features this product can do across a sample site. I use the samples on the Demos.Telerik.com all the time for our ASP.NET examples as a great resource.
I am triing to buid a case for purchasing this product and know that these are the types of questions I will be facing. Also Besides ease of use and not Requireing a VS License, is there any main advantages over QA / Dev versions. I have seen the comparision slides and they seem to do the same thing in both just one is not targeting developers. Is there any advantage to geting dev version. We currently have 3-4 Licenses (Not sure exact number or if other departments have licenses).
I have watched a majority of the videos and went through the FAQ and some of the blogs but still have questions.
Thank you for your time.
PS: Also.... When you goto tv.Telerik.com and click browse and choose automated testing tools.... the Page fails....
Here is the link that fails. http://tv.telerik.com/error?aspxerrorpath=/products/automated-testing-tools/browse
Jason
2 Answers, 1 is accepted
0
Hi Jason,
You are correct in that WebUI Test Studio was designed for functional WebUI testing. You are however able to verify element styles using the ‘Build Verification’ option from the ‘Element Menu’. The ‘Element Menu’ appears when you click on the Blue Nub while hovering over an element. Testing across multiple browsers is always a good practice – for example – You may have a situation where a certain action taken on a page triggers an element to be visible. This element may become visible in one browser, but not in another.
Page load time is not captured by default, however you do have the flexibility to customize a step or even the entire test in C# or VB.NET. With some coding of your own, you could create the ability to capture and log page load times.
We do not currently have test samples that are available to download, however I do like the idea and plan on speaking with the rest of the WebUI team about possibly adding this in the future. In the mean time, I’d be happy to help you out with any questions you have creating tests against your application. Let me know how I can be of assistance!
The difference between the two editions is mostly the interface. The QA edition is designed with QA’s in mind, however it does have the ability to create test lists with a specified order and a calendar display that nicely displays passed and failed tests. The developer edition will keep developers in a tool (Visual Studio) that they are already familiar with, however will rely on the VS Test View for creating test lists. Usually we suggest the developer edition if you already working in Visual Studio and you already have a level of comfort with the IDE.
Thanks for passing along the page failure. I sent a note to our web team to ensure this is updated.
Please let me know if you have any further questions.
Regards,
You are correct in that WebUI Test Studio was designed for functional WebUI testing. You are however able to verify element styles using the ‘Build Verification’ option from the ‘Element Menu’. The ‘Element Menu’ appears when you click on the Blue Nub while hovering over an element. Testing across multiple browsers is always a good practice – for example – You may have a situation where a certain action taken on a page triggers an element to be visible. This element may become visible in one browser, but not in another.
Page load time is not captured by default, however you do have the flexibility to customize a step or even the entire test in C# or VB.NET. With some coding of your own, you could create the ability to capture and log page load times.
We do not currently have test samples that are available to download, however I do like the idea and plan on speaking with the rest of the WebUI team about possibly adding this in the future. In the mean time, I’d be happy to help you out with any questions you have creating tests against your application. Let me know how I can be of assistance!
The difference between the two editions is mostly the interface. The QA edition is designed with QA’s in mind, however it does have the ability to create test lists with a specified order and a calendar display that nicely displays passed and failed tests. The developer edition will keep developers in a tool (Visual Studio) that they are already familiar with, however will rely on the VS Test View for creating test lists. Usually we suggest the developer edition if you already working in Visual Studio and you already have a level of comfort with the IDE.
Thanks for passing along the page failure. I sent a note to our web team to ensure this is updated.
Please let me know if you have any further questions.
Regards,
Daniel Levy
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
0
Hello Jason,
I wanted to followup with you regarding the sample tests inquiry. We actually do have a some samples projects for you to look through. The samples are installed along with the trial. The samples are located in the directory below:
C:\Program Files\Telerik\WebUI Test Studio 2010.1\Samples
Hope this helps!
All the best,
I wanted to followup with you regarding the sample tests inquiry. We actually do have a some samples projects for you to look through. The samples are installed along with the trial. The samples are located in the directory below:
C:\Program Files\Telerik\WebUI Test Studio 2010.1\Samples
Hope this helps!
All the best,
Daniel Levy
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