Skip to content

qTrace – How can it be of help for a tester?

Before few days I got to know about qTrace by QASymphony. You must know them even through BugDeBug as they are platinum sponsors. Let me talk more about qTrace tool which could be used by testers. Here are my thoughts on it,

 

  • This tool could be used in context where steps to reproduce is more complex and there are many steps in it to be written along with more screenshots. qTrace has capability to capture keystrokes and screenshots for every click done. Later, once you record the steps you can view the steps one by one and also the exact position of click is displayed.
  • I liked “System Information” fetching at one place. You have flexibility in including system information. If the bug you are reporting is based on the specific system requirements then you could use this feature to just fetch it in a second by a mouse click. Isn’t that cool enough?
  • Save As options – I see that this report could be saved as MS-Word document, PDF document and other options. These export options are cool too.
  • You can choose what you want to record – By saying this I mean to say that, it gives you list of windows to be recorded which are already in open state. You could choose “Skype” from the list and only any action performed on “Skype” would be recorded and not any other. I found this interesting as other things will not be recorded if any interruption comes in.
  • Screenshot editing feature – This is a MUST and glad to see this feature in qTrace. You can add annotations, crop which is editing feature.

 

 

What am I looking forward from qTrace?

  • More features to make it powerful one.
  • My wish-list of features include;
    • Customizable “System Information” elements. Tester should be able to choose what all information he needs rather than things which might not be required for the context.
    • Exclude “screenshots” option while exporting it as DOC or PDF format. Not all bug reports would require screenshot. This could be disabled before recording the steps itself rather than saying “Exclude” after recording the steps.
    • Make it available for other Operating System platforms like Macintosh and Linux.

 

What is it priced for?

Yearly license costs you 199838 USD. Err, I am just kidding. It is just 49 USD and could be installed on 3 machines under one license. This is damn affordable for the value that you will be getting out of it. I recommend it.

 

Happy qTracing!

Follow Me

SanthoshTuppad

Software Tester, Product Innovator, Security Enthusiast at Test Insane Software Testing Services
I have been as a software tester for over 5 years. I am a hands-on tester and I've been winning bug battles & testing competitions across the world. I am a testing enthusiast, who conducts free workshops on security testing across India (Covered locations: Bengaluru, Pune, Hyderabad & Chennai. Invite him to come to your location), and monthly meets for testers in Bengaluru. I am also an avid testing blogger.

My interests include traveling, driving my SUV, health & fitness and many others. I mentor budding entrepreneurs, testers, teams in any profession.
Follow Me

Latest posts by SanthoshTuppad (see all)

Share/Bookmark

5 Comments

  1. Jari Laakso wrote:

    Hi Santhosh,

    Thanks for the post! The tool seems really interesting for tracking down what happened after a bug/issue was noticed.

    I have a few questions of the tool:
    1) Is it something you want to keep running on the background all the time you test?
    2) Is it time consuming (generally) to go through the recordings or they are easily browsed?
    3) Have you found this valuable mostly on desktop applications or it’s good also for example on web apps?

    Thanks and have a good day!

    Best regards,
    Jari

    Thursday, February 9, 2012 at 7:23 am | Permalink
  2. Jari, Thanks for your comment. Below are my comments on your questions,

    >> 1) Is it something you want to keep running on the background all the time you test? < <
    No. This could be used when we see a bug and we could use when steps to reproduce requires a lot of steps and recording steps to reproduce with screenshots would give a better clarity for the reader.

    >> 2) Is it time consuming (generally) to go through the recordings or they are easily browsed? < <
    As mentioned in the blog post, this should be used in specific context. In such specific contexts; I would not feel it time consuming and you could go through the details of the recorded steps smoothly.

    >> 3) Have you found this valuable mostly on desktop applications or it’s good also for example on web apps? <<
    Again depends on the type of bug found. I have not used it much to comment on whether more value in desktop or web applications. However; my answer still remains the same, it is based on the context of what bug is found and does it require to be captured using qTrace because steps to reproduce is huge and might be better communicated along with screenshots too.

    – Santhosh Tuppad

    Thursday, February 9, 2012 at 11:53 am | Permalink
  3. Rabby wrote:

    Can I download a copy and a free month’s trial? Site is down as of this post btw.

    Tuesday, February 14, 2012 at 12:25 am | Permalink
  4. Hi Rabby, It is working now. I hope you have downloaded the trial version.

    Tuesday, February 14, 2012 at 3:12 am | Permalink
  5. Prasanna wrote:

    Cool, I think it can prevent lots ‘Not Reproducible’ defects and consequent delay in fixing them.
    $49 yearly is dirt cheap.
    I want another point in the wish list:
    If it can be integrated with other test management tools like QC

    Wednesday, March 21, 2012 at 11:36 am | Permalink

Post a Comment

Your email is never published nor shared. Required fields are marked *
*
*