The Protocol Data view displays HTML details that were generated during a schedule run. This view can help you to verify that a test is behaving as you intend.
The amount of detail that you can see in the Protocol Data view depends on the Execution history log level setting in the schedule: see Setting the execution history collected during a run. The setting All is recommended if you plan to use the Protocol Data view. Be aware, however, that the All setting is not recommended for large schedule runs because of the time required to transfer large amounts of log detail to your computer after a run finishes. A sensible compromise is to use a special schedule for Protocol Data view runs with the log level set to All, and to limit this schedule to a single test (or a small number of tests) and to a small number of user groups or loop iterations. Once you are satisfied that a test is performing as you intended, you can move it to a schedule that emulates a realistic workload.
User groups, virtual users, and some HTTP requests are executed in parallel, and the execution history is more reflective of the execution order than the recording order or the order of user groups in schedules. As a consequence, the ordering of page requests in the test and in the execution history might be different, and user groups might be ordered differently in the execution history than in the schedule. However, the order of pages in a test and of tests inside a user group will be the same in the execution history as in the corresponding test and schedule.
If you cannot locate the Protocol Data tab, you can start the view by selecting Window > Show View > Protocol Data.
Parent topic: Evaluating results