Articles Tagged 'logging'

Sometimes to diagnose issues with SpiraTest, SpiraPlan, SpiraTeam or KronoDesk it is helpful to increase the logging level to log all trace activity in the system. This KB article describes how to enable this feature.

Sometimes when you are using Rapise, you see an error on the screen, or something doesn't work as expected. In that case, our support team will need a copy of the log file that is likely to contain the error message. This article explains how to get that log file.

A customer had a question - is there a way to suppress the DoSetText or DoSendkeys methods from sending their text to the logs. They didn't want users to see this text in the Rapise (and SpiraTest) logs because they contained sensitive information (e.g.  passwords).

When using Rapise, it is often useful to see how Rapise is identifying objects in the Application Under Test (AUT) and if necessary find out why Rapise is not able to locate a specific object. This article outlines how to increase the logging level in Rapise.

This article is obsolete. There is no ribbon in Rapise since version 6. If you have Rapise 6.0+ then follow these steps to change the verbose level.

This article describes how to export server Event Logs when requested by support.

Sometimes when using RemoteLaunch with a specific plugin (e.g. Selenium), you may get an error such as:

Could not load file or assembly 'WebDriver, Version=2.44.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The system cannot find the file specified.

The way to debug this kind of error message is to enable Microsoft .NET Fusion Logging to get more information as to which dependency could not be loaded. This article explains how to turn this on.