In some situations, it is beneficial to analyze the runtime events of a test. For example, to analyze concurrency issues, you might want to know in what order requests were sent.
StresStimulus can write test events to system trace during test execution. If no system trace is available, it can also write trace data to a file.
Trace Log Options
To enable writing to trace log, in the Workflow Tree > Advanced Options > set Enable test execution trace log property to Yes.
To set the trace log properties, in Main Menu > Edit > Settings > Trace tab
The following are the events that can be traced:
- General: General test events & system errors. If using scriptable variables or components, all runtime errors will be logged.
- Errors/Warnings: Requests errors and timeouts that happen during the test. Includes VU #, Session #, Iteration #.
- Request/Response: All request and response events. Includes VU #, Session #, Iteration #.
Check the Add timestamp to the external listener checkbox if your listener does not provide its own timestamp.
Log to a file
If you don't have a system trace listener or want to save the output to a file, then check the Log to file checkbox. Then specify the output folder and max log size.
Before every test, a new log file will be created and populated during a test run.
- No labels