Replay results can be consumed using Replay-Result viz, Tabjolt vizes and Logshark vizes
Replayer knows about each session that it executes, the tool writes following information to a Replay.csv file.
- URL of the viz that it loaded
- number of interactions executed
- number of failed interactions
- Status of the page load i.e if it succeed or not
- time taken during page load
- Apache Access ID of original traffic to correlate the replay traffic with original
After a replay test run in the output folder the tool creates the Replay.csv, summary.csv and copy of ReplayResult.twb and Replay-Compare.twb. Use ReplayResult.twb to understand the results of replay run. This can be used for user acceptance testing to understand load and interaction failures.
To compare the results of 2 runs use Replay-compare.twb, which can help in understanding error rates and response time difference between the two runs. To compare the results copy Result.csv from run A and name it Result-A.csv, also copy Results.csv from run B and name it Results-B.csv, opening Replay-compare.twb should connect to the Replay-A.csv and Replay-B.csv which will help in doing AB comparison.
The result of running replay generates traffic to Tableau server with viz loads and interactions, after replay completes if the Tableau server zip log is processed with logshark it generates vizes which can be used for performance comparison. Mainly the Apache.viz gives a overview of page load time and different errors encountered during the run.
The following screenshot shows the bootstart response time in Apache logshark viz, which is similar to tabjolt viz (shown previously) except this information is collected from server logs.