DrinaW wrote:Good morning.
Can you please tell me more about how eValid creates its logfiles?
We can certainly help you understand more about logfile in eValid DrinaW.
As eValid plays back a script it writes certain information about what it is doing to four different logfiles: the event log, the performance log, the timing log and the message/error log.
As an eValid user you have several options in processing these files.
Every file can be purged before playback, or can be appended to after each playback (if you have multiple playbacks).
How does these logfiles compare with each other?
Here's a summary of differences:
* Event Log. This has a single time-stamped line for every event that happens during playback.
At the end of the file it has a Download Summary that gives statistics about the download details from the playback.
The other three logs (see below) are subsets of the event log.
All four logs have the same Download Summary at the end.
* Performance Log. This log contains no messages from any Validate, Timer/Alarm, and Wait commands which are executed in the script during playback.
Messages for Absolute Events are not recorded into the performance log as well.
This log should only contain the download timings and the "Command Completed" message.
* Message/Error Log. This log contains ONLY those lines of the Event Log that do NOT say "OK" as a result status.
So, this is a good place to look for any error messages your playback generated.
* Timing Log. This log contains only the summary of the downloaded page.
It should only show the Number of Cached bytes, Total number of bytes downloaded, the total download time, and the rate of the download.
Note: LoadTest runs write results in a slightly different way, so this explanation does not apply to LoadTest runs.
When viewing eValid Logs:
All eValid logfiles can be viewed in a variety of ways -- with simple click-on buttons:
* View data in Text Editor (using your default Text Editor)
* View data as HTML Table
* View ALL test data in an eValid chart
* View last test run data in a eValid chart
* View as a spreadsheet (using your default spreadsheet processor)