After a Login VSI test has completed and investigating is being done in results, if there were either sessions which were slower to perform a workload function or ended up finishing a function, thus hitting a timeout, there might be screenshots in the Login VSI results structure.
These screenshots are programmatically captured by the virtual user running on the target session. This file will get uploaded to the Login VSI share on the Login VSI server host.
- Navigate to the results directory and ErrorShots directory within. The ErrorShots directory won't exist unless at least one screenshot was uploaded to the test results.
The path is: \\<loginvsi_serverhost>\<loginvsi_share>\_VSI_Logfiles\<test_name>\Debug\ErrorShots
- Note some screenshots might have the same filename other that one not having a -e at the end, and the other having it
- Screenshot filenames without -e: These are "warning" screenshots; these are taken when the virtual user is slower to complete a function on the target, usually caused by resource getting close to constraint in the infrastructure
- Screenshot filenames with the -e: These are "error" screenshots; these are taken when the virtual user hits a defined timeout and was unable to complete a function in the workload. This condition will produce a messagebox mentioning what the workload function was attempting to perform, to give a better idea of what to troubleshoot. This is what the screenshot-taking mechanism will capture.
An example of essentially the same screenshot with slightly different filenames and one showing the Login VSI-detected error, in this case, Outlook encountered some error and was unable to successfully load.
Login VSI 4.x