Hello Yuriy,
The actual behavior depends on your client-side player's implementation.
I have experimented with YouTube, and I have discovered that its player actually downloads the FLV video file from the server via HTTP, and hence this activity is recorded in the task. The problem with YouTube is the dynamic video links - the recorded link will not work during the test playback without scripting modifications.
So, if your application uses dynamic links to video files, you will need to handle them in a special way in your script.
Here are the answers to your questions:
| 1. How to make sure that my script is recorded correctly |
Clear browser cache and cookies before the recording.
| 2. How to determine that Script execution does what it needs to do |
There should be no errors or warnings in the test execution results.
| 3. How to correctly read the Logs (Please note that i did some reasearch on that for a few days and have a bit of an idea). |
This depends on the type of the information you want to get from there. The logs show some performance parameters. So, the general task is to decide whether the timings are appropriate.
4. What details do i need to present to Network Team to point out if the server is capable in accepting X amount of connections and that all connections should not have issues while streaming the video on their PCs.
|
I would recommend that you read the
Real-World Load Testing Tips to Avoid Bottlenecks When Your Web App Goes Live MSDN article - it should help you understand how to interpret Load Testing results.
