qTrace is a rich set of tools that adapts to your testing needs, yet it is simple to use and easy to learn.

1. Record

qTrace does not just capture screens or videos, instead it is an intelligent capture technology similar to those found in sophisticated test automation tools. qTrace tracks users’ interactions with an application and uses that information to automatically create detailed defect document. qTrace supports the recording of a wide range of applications and technologies on the browser as well as desktop apps.

When recording, Testers can choose to:

  • Take a single screenshot of the current desktop
  • Record all applications – Any user action on any applications will be screen captured and included in the bug report
  • Record one or more specific application – Only the user action performed on the selected application(s) will be included in the bug report

Testers can have qTrace store all of the actions performed while recording, or choose to store only a limited number of screen captures. With a limited number of screens, testers can run qTrace continuously in the background during testing, while avoiding large recording files.

2. Edit

qTrace Editor is provided when recording is complete. Testers can review the recording, edit by adding notes and highlights, and select important information to include in the final bug report. User can enter a defect title and description and then edit the following recorded information as desired.

Screens:

  • Delete a screen from the recording
  • Select to include or exclude a screenshot from the defect document
  • Edit the screen by cropping, adding highlights or arrows, adding call out note, or blurring sensitive/private areas of a screen
  • Move the location of a trace step on the screen

Trace Steps:

  • Add or Delete trace steps
  • Re-number trace steps
  • Edit the text of a trace step
  • Add/Edit a note
  • Select to include or exclude the trace steps from the bug description

Environment Information:

  • Select which element of the environment information such as OS, ADO version, CPU, RAM, … to include in the bug report

3. Share

After the tester finishes editing the bug report, it can be shared to the team in a number of ways.

  • Submit a new ticket: Direct integration with multiple defect tracking system lets testers simply click Submit to create a new defect ticket
  • Create a Document: Export the defect information into a Word, PDF or as multiple JPEG images. Testers can use/share the exported documents as a bug report
  • Email a Document: Quickly send an email of the bug report

qTrace offers built-in integration with these defect tracking systems.

We will be adding other defect tracking tools in the future. But if you cannot wait, or if you don’t think QASymphony will be supporting your defect tracking tool, you can custom build your own connector using the tracker API. You can learn how here.