Hybrid Execution Model adds an additional layer of dexterity as compared to Cloud Execution Models as we can get custom Device/OS/Browser/Version Combo as available for Test Execution. Also, we have access to the log files for debugging the errors in case one occurs. We will discuss how to get those log files from your local machine for debugging. Providing these files to the Testsigma Technical Support Team will ease the process of finding the root cause of an Execution issue and help with quicker issue resolution.
Locating the Log files
Testsigma Agent is essentially a client Application for the Testsigma App and it is deployed on the local machine using Apache Tomcat. Since the deployment is done using Apache Tomcat, we can get the Log files from the location where Apache Tomcat logs are created.
1. Testsigma Agent logs
Find the Apache Tomcat working directory in your Machine and then locate the logs directory in the same directory where Apache Tomcat working directory is. Inside the Logs directory, you can find a number of files such as agent.log, Testenginelog.log e.t.c.
2. Apache Tomcat logs
Now, inside the Apache tomcat folder named apache-tomcat-<version>, you can find the logs folder for Apache Tomcat. Inside the Logs directory, you can find a number of files such as catalina.log, localhost.log, localhost_access.log, host-manager.log, manager.log e.t.c.
Please zip the above logs folders and attach them in a mail to firstname.lastname@example.org describing the issue.
For a technically sound user, the logs will serve as a great tool for debugging the issues themselves. However, if you need an extra hand, we are always there for you. Just drop in a mail to email@example.com describing the issue and with the above-mentioned log files attached. Remember, adding as much detail as possible will help us resolve the issue in shortest time.
Please mention the following details in the mail:
- Execution Type: Hybrid Web/ Hybrid Mobile. If it is Hybrid Mobile Execution, attaching the Appium Logs too will help.
- Project Name, Application Name, Test Case name, and Execution Name.