Load Test
In the real life
Workflows
Index
- Creation Load Test
- Preparing Data
- Executing Load Test
- Analyzing Results
-
Measure the performance of the application to know which is performance for each version of the Application and see if the performance goes better or worst iteration by iteration
-
This test plan should have a test battery collection for the main important test cases simulating a number of user using the application and simulate the the work load of the server configuring the Load test
- Another benefits of this is to detect possible issue with a number of concurrent of test running simulating the use of the application
Performance counters and logging trace
Add performance counters into the application to be used in the load test plan.
IN order to measure properly the performance application we need to improve our audit information so it will required to add some performance counter and added some more trace information in the different place of the application which we want to test it
Try to Remove dependency on data
Look for a solution to avoid create load test dependent of the database id
Ideally the best approach will be to get the policyid , reportid or enquiryid in the test from database and not dependent of the template database .
If we do this task them will don't need to have always the same template database and we could swap between database .
We'll Add a data source to a web performance test like it said in this: https://msdn.microsoft.com/en-us/library/ms243142.aspx
Preparing Data
Frozen information
Creation template database
It will have configured all what the test data with all the information necessary to run all the scenarios
Executing Load Test
Rig or not Rig?
Create Load Test Rig
set up a group of computers that generates simulated load for testing. The group consists of a single controller and one or more agents. Collectively, this group is called a rig. An agent is the part of the rig that is used to run tests and generate simulated load.
Title Text
Title Text
-
links for more info
http://southworks.com/blog/2013/01/17/visual-studio-load-tests-creating-a-test-rig/
https://msdn.microsoft.com/en-us/library/dd728093(v=vs.110).aspx
https://www.benday.com/2012/01/16/debugging-visual-studio-load-test-rig-problems-2/
https://msdn.microsoft.com/en-us/library/ms253092(v=vs.90).aspx
Scheduling execution
Integrate the load test with tfs services
Ideally the load test should be executed automatically when the package will be built by the tfs building machine.
It will help to identify daily the performance regression
Analyzing Results
Analysis the load test results in order to determinate which was the result to see if the performance went down
In order to see if how was the run load test will be required see how we'll don an analysis of the results to decided how was the performance
For each release will be great run the load test and see the results before create the release package and be aware how it's going the application performance.
Acceptance Criteria
Define an acceptance criteria for those existent automated test once we have an stable database data
Once we'll have an stable database data when the following pbi Create template database and load performance
Could be started to define an acceptance criteria depending of the running results