Introduction to Application Center test
Developers Concentrate on new features to make their job simple. Of course, the aim of the New Versions of a Visual studio is to make Developer job easy by reducing code more than half of the previous versions. Designers search for Code to meet their Client requirement.Most of them minimum make a fuss over the inward preparing of Web server (IIS).This article is to influence them developers to check their Application’s Performance utilizing the Microsoft Application Center Test Tool (ACT).
Description of application Center test
As a developer, It is important to think about Microsoft’s Stress testing tool for Visual Studio 2003, Application Center Test (ACT) stretch tests web servers and examination performance and versatility issues with web applications. By this tool, we can quantify performance through a few parameters like Requests per Second (RPS), Iterations, HTTP errors, DNS errors, Socket errors, Average Time to the first byte, Average Time to last byte and so forth. This parameters list Displayed on Output window after fruition of a test. This test additionally helpful to check the conduct of the application under a few synchronous end clients (stack) of the web applications.
Requests per Second: Indicates the rate at which the Web server is reacting to HTTP requests from the ACT. Qualities are ascertained in view of a second testing period.
Note: It should be high.
Iterations: Indicates the number of times the test has been iterated (looped) since the start of the test run. This is shown for all tests, paying little respect to whether the test length was determined to utilize emphasis or a runtime.
Note: It should be high.
HTTP errors: Indicates response codes in the 400-499 and 500-599 range are being received. These errors can be caused by many different problems with either the requests or the Web application.Analyze the answer to discover the solicitations in charge of the blunders, and the correct reaction codes returned by the Web server.
DNS errors: Indicates errors occurred resolving the server’s address. It could be caused by a request that uses an invalid server name, or it could be due to network configuration problems.
Socket errors: Indicates the Web server is unable to maintain some or all connections. During exceptional load conditions utilizing different concurrent associations, the Web server will ordinarily start dismissing associations after its most extreme limit is surpassed.
Performance is an afterthought. Obviously after the correctness of the application. But we can not ignore the Performance. Using ACT we can assess the Application performance, Not the suggestions to improve application performance.