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

As we have discussed in the Hybrid Execution Model Setup Article, Testsigma Agent is the tool that creates a communication channel between the local machine where the Execution is performed and the Testsigma App on the cloud. 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.


Once you have found the Apache Tomcat working directory, locate the Logs directory in the same parent directory where Apache Tomcat working directory is. Inside the Logs directory, you can find a number of files such as applications.log, agent.log, spring.log, Testenginelog.log e.t.c.


Debugging Errors

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 support@testsigma.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.