I have done a load test to my wcf was hosted service using visual studio 2010 load testing tool.after the test i got below result.
can u any one help me to interpret above result.I have search on the internet and i could not be found any helpful description.
If you opem the Tests Table in the Tables View there is a column Test Time:
Test Time: The average time to execute the test during the load test
run. The units are seconds.
So, the Avg. Test Time is the average execution time of all tests.
Related
Have just started using Visual Studio to load test a web application. I have set up a number of load tests successfully but I am having an issue with one particular test. It happens to be the first time I am including a File Upload, so possibly that has something to do with it.
The LoadTest includes one WebTest that performs the File Upload. After completion the Test Details table shows most of the WebTest's taking ~100-120 seconds to complete. When drilling into the Test Log for each WebTest execution and adding up the Request Time components the result is the expected ~1-3 seconds.
Running the WebTest by itself also gets the expected ~1-3 seconds.
Think times are turned off.
I expect there is a parameter/config value that I have overlooked. It would be greatly appreciated if someone could shed any light on this.
Finally found it. In the properties for the load test scenario there is a "Think Profile" option. It was set to "Normal Distribution". For what I am trying to achieve it needed to set it to "Off".
We have an automated testing framework which using CodedUI, links Ranorex (5.4.2), VSO 2013 (TFS) and VS 2013 on a dedicated automation server. It runs the tests in a sequence determined by a query in MTM which orders them in ascending test case ID order and has been running fine until recently:
An MTM Test Run Log shows them being scheduled in the correct ascending test case ID order. In this image you can see the test case ID sequence going from test case ID 607 on line 9 to test case ID 624 on line 10:
In the last week we've noticed that although the order of the tests in the query hasn't changed, the tests are being reordered when the test run is being prepared in MTM:
In this second image, you can see the sequence change to test case ID 607 on line 9 to test case ID 25285 on line 10. The sequence continues to jump back and forth in a very disorganised way. This is causing us issues because some of the later tests rely on test data generated in earlier tests and therefore fail when this data isn't available because the test is running earlier than it should do.
Nothing has changed in the sequence of the tests in the query and we haven't added any new tests, but our devs have recently installed Visual Studio 2013 Update 5 around the time this started happening.
Has anyone come across this issue before or know whether it could be due to this recent VS update? I have hunted and hunted but have not been able to find anything similar on any other site.
UPDATE
I have investigated this further by doing a run of a smaller number of tests:
Again they go out of sequence during the test run at line 10 of the log. Line 13 contains the test that should have come at line 10:
I have run out of ideas on how to take this issue forwards, so any help would be hugely appreciated.
All -- I am using Visual studio 2013 ultimate edition to run my load tests. I have more than one scenario configured on my load test. Each of the scenario run a different set of unit tests. Is is there a way to selectively run the scenarios ? In other words if there are more than one scenario configured, can I just run one of them and not run the rest ?
If the answer is 'NO', any ideas/suggestions would be very helpful.
Thanks in advance.
Two ways I have found:
One way is to set the user load to a constant zero in the unwanted scenarios.
Another way is to set the "Delay start time" of the unwanted scenarios to longer that the total test duration. This option only makes sense when "User test iterations" is false.
I need to generate some delays to make a load test more realistic. In Visual Studio I have found 2 methods that delay execution of a transaction in a loadtest:
Convert to code
or
Set "Think Time" to first request in the transaction
What would be the best practice here. I am not completely sure that Visual Studio executes these test in sequencional manner, so 2nd option might return false results.
On the other hand, I would loose the ability to change settings from Visual Studios UI, if I generate code from a recorded test. And that increases time spent editing the test quite a bit.
Is there a better way than any of my methods?
I believe that the second way is more safier.
Just have in mind that the Think Time is aplied to each Test Run not to each contained Test. So, if you have a Load Test which contains more than one Tests in the Test Mix the Think Time will apllied at the end of the test run (when all included tests were completed).
Also, if you have more than one virtual user, since it's a load test, Think Time is applied to each user seperately. If, for example, you have 100 user then they will concurently start the tests but they may not finish them at the same time. Each user will wait according to the Think Time before starting the second test without waiting for the others to complete their first test.
I have an ordered test that contains 4 web tests. The problem is that Visual Studio seems to have a problem loading the test results for an individual test.
I included a screenshot to supplement for the 1000 words. :)
As you may see the 3rd test, called intuitively Webservice03, failed. The screenshot above was taken after I double-clicked on the corresponding line to open the detailed information about that test run. The panels with requests and other useful information are empty.
The issue is quite annoying, because the test is part of a bigger test suite that runs periodically, so when it fails, I have to manually disable the setup and cleanup scripts from the test configuration, run them manually, then run each of the tests manually, instead of just comfortably opening the test results.
Did anyone experienced this problem?
Thanks.
Version details:
Microsoft Visual Studio 2010 Ultimate
Version 10.0.40219.1 SP1Rel
Microsoft .NET Framework
Version 4.0.30319 SP1Rel
I had the same problem and tryed to clarify it via Microsoft forum:
Web test details are not displayed when ran from an ordered test
According to the answer you can not have detailed test result for a web test run as a part of an ordered test.
Here is an alternative to Ordered Tests:
Add the web tests to a load test
In the test mix choose 'Test mix based on sequential test order'. This will achieve the same thing as an Ordered Test.
In the load test run settings, make sure 'Save Log on Test Failure' is set to True:
Set a Constant Load Pattern of 1 user
At the end of the "load" test you will be able to see the number of failures and on the Tables view you can click on the error count which takes you to a dialog that lets you browse the individual web test failures.