Performance Testing Using VSTS

Performance Testing Using VSTS

                   Webtest is another mechanism of automating the manual test case execution in Visual Studio Team System . All along we have been gaining insights into the Functional automation of a system under test using the Coded Ui Testing mechanism introduced with the shipping of 2010 version of the VSTS.

In Fact the Webtest can as well be brought to an optimum use to automate an application, however the robustness needs to be analysed for the same. I have put one Coded Ui Test mechanism description in my series of article with lots of images.

Webtest feature of the test project in Visual Studio is used for performance testing alone. It mainly interacts at the http level and only request response of the various transactions is tracked in it. As a result, we cannot have any scenarios having the client side validation tested via this very functionality. Only the business transactions having the client server interaction can be tracked. All set of scripts get recorded in the form of request response parameters.

Some of the very basic terms associated with the Webtest is the context parameters. It is something that we generalize as variable names in our day to day scripting. We parameterise the control id dynamically by making it dependent on some start text and end text and then apply a sort of extraction text rule by which the text coming in between the start and end text get extracted and stored in some variable which is what we discussed as context parameters.

Then once we have done the business scenario recording, we can apply a load on the set of scripts and run the execution suite.This results in the performance testing being realized.

Related Post On Coded Ui Testing :
  I will be doing the same with the Webtest as well, describing how we can use this very feature to an optimum usage to bring a Return On Investment from the business perspective and ease out the manual testing phenomenon to remove the boredom of doing the same repetitive task again and again.
This includes more of parameterizing the control definiton of various objects , based on the recognition mechanism and also the object if at all changes in the future shipping of the product, the same can be handled with ease using the Context Parameters globalisation method. Context parameters may be an input from the user end to data drive a test execution or it may as well be some sort of Rule that has been applied on the System, under Test to fetch some properties of relevant object to make the testing more independent of the Control Ids.

Keep visitng the blog to delve more into the Automating of the Applications.

1 comment: