Identify the Media You Are Trying to Test
This is frequently confused with the web page or media player location on your website. The target of a streaming media task will not be the URL of a player or web page that contains the player, but the actual media resource path that is used by a player to play the file.
Once you have identified the location, check the media file type. What protocol does it use? (make sure to specify the protocol in the file path (such as rtmp:// or https://, for example).
Creating a task
Enter the address of the actual media file you wish to monitor. Note that the URL must link directly to the media resource and not a web page that contains a media player. For example, “http://streammedia.com/stream.asf”.
Enter the number of seconds the task should wait for a response from the web page before ending the task and returning an error. If this is left blank the default timeout for a task is 120 seconds.
Duration (in seconds)
By default, LoadView connects to the media server, performs buffering, and plays the stream for 30 seconds. You can customize the option to specify the duration of media content you want to play for the test. The maximum available value is 30 min.
For example, if you specified 90 sec in the duration field the system will try to play 90 sec of the media stream. If the completion timeout period has elapsed prior to completion of playing a 90-sec track of the media stream, the test session will be considered as failed.
If the Auto Select option is specified, the engine will be selected automatically based on the analysis of the media source URL.
You can choose ReportDetails by adding into the Prepare Script field:
(Tasks as Media).ReportDetails = “FULL”;
Tasks[<sequential number of the task>] – specifies the sequential number of the task in the device. Note that the numbering of tasks in the device starts from zero. So to refer to the first task in the device you should provide Tasks.
ReportDetails = (“STANDART”, “FULL”, “SHORT”)
(Tasks as Media).ReportDetails = "Full";