LogDigger Track Page

The track page shows a list of all data collected during the application usage tracking session.

Track layout

At the top of the track page you can find basic information about the usage session, such as:

• The project to which this track belongs;
• The testing date and the username of the person conducting the test;
• The web browser used;
• An overview of the issues reported in this track;

Data in the track is organized by actions, such as HTTP requests to the application, or issue reports. Actions are sorted in reverse chronological order (the most recent action is at the top of the track).

Typically, HTTP request related actions include:

• the URL of the HTTP request;
• the HTTP GET and POST data;
• the thumbnail and/or screenshot of the loaded web page;
• browser details;
• server logs and other data, when available.

An example track page:

Reporting an issue

You can report a new issue related to an HTTP action while you’re reviewing the track page. To create a new issue, move the mouse pointer to the action header and click Report issue.

Clicking on the link will open the LogDigger issue report form. The screenshot related to the issue will be the one attached to the action.

Reviewing server logs

If server logs are available, they will be associated with the related actions and linked from the action header. If the log contains error messages, the first message will also be displayed in the action header: