...
Scenario testing replicates a number of standard user actions so we may confirm how your player behaves in each case, and importantly, how our library acts accordingly, i.e. that it is correctly cap-turing all possible user interactions.
You can find a detailed list of these scenarios here.
Step 3
This last stage involves a Kantar Media Spring sense check to confirm the content of the streams is as expected.
...
The live results of this test will be displayed on the main Output screen (see below).
Illustration 2: Example main output screen
In the Events section of this page you will see:
...
Below we demonstrate use of the tool by providing a UK example.
Setting up the test tool
We left the first field (app name) blank because it is optional.
...
After clicking “Start test!” and a stream has been running
After starting the test tool and then starting the player, you will see the event counter counting through the number of requests as they are processed.
...
When clicking the “Viewrequests”
Part 1
In the above screen shot, we scrolled down through the list of all the heartbeats sent during the test.
...
- The number of the heartbeat sent: 34,
- The time when the server received the heartbeat,
- The app name: 4oD. (This value is obtained from the library app installed in the player and is populated if you have not entered this value in the first screen)
- The Apple Advertising ID after the Kantar Spring library hashed and truncated it and sent it to the measurement systems
- Then follows either a list of the errors and warnings, or as in this case: an “OK” message.
Part 2
In next part of the test the heartbeat data is broken down and parsed into a readable format.
...