Introduction iVision had its third annual Tech Summit meeting on October 14th, 2016 and it was a great success. The Tech Summit is a unique concept whereby all employees can meet for a casual evening together to learn about what’s going on in each practice, learn about some new and emerging technologies, and build closer team […]
There may be times when you want to have different post data on a per-request basis. You could just clone the request and hardcode each one with a different data set, but besides taking up a lot of unnecessary time, the data change again it would be difficult to update it again. Fortunately, Visual Studio has the functionality to populate any values in the test.
In part 2 of this series on Web Performance Testing with Visual Studio 2013, Kevin walks you through creating validation rules, extraction rules and coded web tests for your applications. Part 1 dealt with creating a WebTest using Microsoft Web Test Recorder, which is good for testing the overall process. If you want to setup benchmarking or confirm the application working correctly, then you will need to setup coded web tests, validation rules and extraction rules.
Recently, iVision was contracted by a long-term client to conduct performance testing on an intranet application they had acquired from a third-party. The process involved coordinating and integrating technologies such as Microsoft Visual Studio’s Web Performance Testing and Load Testing, Microsoft SQL Server’s SQL Profiler tool, Performance Monitor, and Microsoft Excel. Our client wanted to ensure that the product would respond well while under expected (and greater-than-expected) loads using existing hardware.