Developer’s Description
Test Evidence Suite enhances developer-tester-user communication. Like a software black box, the Test Evidence Suite sits in the background recording a continuous loop of user actions. Everything gets tucked away in an archive for later review. In UAT: Test Evidence allows your users to work as normal, confident that, should anything go wrong, there’s an exact history of what they did, along with screen shots to backup each action. Test Evidence turns your users into expert bug reporters. In formal testing: Test Evidence Suite’s archive can be filed away as proof of the execution and result of a test. In compliance: the Test Evidence archive is a permanent record that activities were carried out. Test Evidence Suite saves time and increases productivity by enhancing the communication between developers and testers / end users. There are no grounds for doubt when the developer sees exactly what the user did.
The recording is saved to a single file that can be sent to your dev team for analysis and review – find out what a user did to trigger a bug.
The recording may also be exported to a PDF or Word file and archived as part of your QA validation process.
Test Evidence has proved particularly popular in the medical field to prove the provisioning and configuration of devices prior to them being supplied to users.
Record user actions such as keystrokes and mouse clicks, along with screenshots, using this handy application that can help you track down software bugs
Test Evidence Suite
Review by Corneliu Paval on February 26, 2015
What’s new in Test Evidence Suite 1.26.0:
- New Features:
- Supports fixed term license codes.
- Bug Fixes:
READ THE FULL CHANGELOG
Hunting software bugs and testing applications is a difficult, labor-intensive and time consuming process. People working to debug a program can appreciate the value of knowing the context in which a bug manifests itself. The Test Evidence Suite can help them obtain detailed accounts of the user’s actions for the purpose of debugging by logging the user’s keystrokes, mouse actions and attaching relevant screenshots.
The software solution is comprised of two independent applications. One (named Test Recorder) is run by the tester and generates detailed logs regarding their activity, and the other (named Test Reviewer) can be run by the person trying to track down or fix the bug in question. This second application can read and display the logs generated by the first and can also export them as PDFs.
An easy to use logger and recorder
Test Recorder can capture mouse and keyboard activity while taking screenshots of one of the user’s displays. Those who make use of multiple displays can select which one to capture sceenshots from, or to capture images from all of them.
Since this application was not designed with spying on users in mind, its main window needs to be open while recording, and recording sessions cannot be started remotely or scheduled. Users also have the option of selecting which actions will be captured and can configure custom hotkeys to start, stop or pause the application.
View detailed logs of mouse and keyboard activity
Test Reviewer can display detailed, timestamped records of user activity by opening log-files created by Test Recorder. These include, apart from the mentioned timestamp, which mouse button or key was pressed and the coordinates of the pointer. The pointer’s position is also highlighted in the attached screenshot.
Information regarding the computer on which the log was taken, such as operating system, machine name, user name, CPU and .Net Framework version is also included.
Conclusion
This is a handy and reliable application that can be used to analyze the context in which certain bugs occur. It can also have other uses, such as creating tutorials, help files or presentations, for example.
More about Test Evidence Suite
The installation package of Test Evidence Suite v1.26 takes up 21.19 MB. Belonging to the Productivity category, namely Office Software, makes it popular among such programs. The most popular installation package for downloading this program is the TestRecorder.exe file. The direct download link has been checked by our antiviruses and has been found safe.
Every day I keep on getting several requests for a Test Case Template. I’m surprised that many testers are still documenting test cases with Word docs or Excel files.
Most of them prefer excel spreadsheets because they can easily group test cases by test types and most importantly they can easily get test metrics with Excel formulas. But I’m sure that as the volume of your tests goes on increasing, you will find it extremely difficult to manage.
If you are not using any Test case management tool, then I would strongly recommend you to use an open-source tool to manage and execute your test cases.
Test case formats may vary from one organization to another. However, using a standard test case format for writing test cases is one step closer to setting up a testing process for your project.
It also minimizes Ad-hoc testing that is done without proper test case documentation. But even if you use standard templates, you need to set up test cases writing, review & approve, test execution and most importantly test report preparation process, etc. by using manual methods.
Several documents and reports are being prepared as part of Testing. Some are Test Strategy doc, Test Plan doc, Risk management Plan, Configuration management plan, etc. Among these Test Summary Report is one such report which is prepared after the Testing is completed.
Many testers, particularly when working off detailed test instructions, have a tendency to minimize the information they record when testing. This can vary from noting what variables or values they start with and what they end with, to simply noting the test “passed.” The challenge comes when problems are found later, possibly after the software is in production. How do we remember what we did, and when? What records do we have to refer to? How do we, as testers, answer the question “How was this tested?”
How Was This Tested?
That is one question every tester will get asked at some point in his or her career. Sometimes it is asked in a manner of “Wow! That is fantastic!” But sometimes, it is asked in a manner of “Why did you not find this problem?”
Of course, the difference between a tester feeling complimented and a tester getting defensive comes down to the tone of voice. Asking, “How was this tested?” can lead to an informative discussion where everyone learns something, or it can set off a confrontation—particularly when the tester already feels frustrated that a bug was missed and got through to production.
Test Evidence Suite is software for monitoring and recording user actions, such as keystrokes or mouse clicks. It can also create screenshots.
Because developers do not want the program to monitor other users’ activities, it requires an application window to run while logging actions, and the process cannot be started remotely and cannot be scheduled. Configurable keyboard shortcuts are available for easy use.