Configuring Tested Application

Configuring the tested application for LogDigger tells the LogDigger browser extension how and where you want to receive feedback and usage tracking information.

The application can be configured by:

• providing a logdigger.xml configuration file (simple and does not interfere with the application in any way), or
• enabling a LogDigger Connector component in your application (programming language dependant).

Note

It is not necessary to configure the tested application for LogDigger. By specifying LogDigger settings manually in the browser extension, the user can attach any web site to a project in the LogDigger Server. However, if the tested web site is under your control, it is highly recommended to configure it to automatically point the LogDigger browser extension to the appropriate LogDigger Server project.

Configure using logdigger.xml

The application configuration file for LogDigger is a simple XML file that points the LogDigger browser extension to a project on the LogDigger Server:

<?xml version="1.0" encoding="UTF-8"?>
<logdigger>
  <server>http://your.logdigger.server:8080/logdigger</server>
  <logging-key>your_project_key</logging-key>
</logdigger>

The configuration file must be named logdigger.xml and accessible from the root of the website. After installing the configuration file, ensure that it is accessible by opening http://testedsite/logdigger.xml in your browser.

Note

Make sure to verify server URL and logging key for your project. On the project page you can find a sample of logdigger.xml already containing parameters for your environment and project.

Configure using the LogDigger Connector (Java only)

If your application is in Java and you use Log4j for logging, you can have the additional benefit of collecting your application logs as a part of the test tracking data. See the section LogDigger Connector for Java for details.

You do not need logdigger.xml if you are using the connector.

Note

Configuring the tested application does not mean that the application usage session will be recorded automatically. The tester has to:

• enable tracking using the LogDigger button menu, and
• accept the sending of usage data to the specified LogDigger Server instance.

LogDigger will stay enabled for the site even after a browser restart, until disabled by the user.