vLog for QA technicians

vLog improves the communication between the QA team and the Developers team.

The developers can create "reports" to describe scenarios for testing.

The QA technician run his tests while vLog runs in the background and is configured to record the applications that they need to test. When the technician encounters a problem that he wants to report, all he needs to do is to click on the Ctrl-Ins. vLog creates a comprehensive report that describes the last 10 (a configurable parameter) actions and contains all the "extra-information" that are preconfigured in vLog. vLog also copies the path to the report into the clipboard. If the destination is set to "AttachToBugReport", than vLog opens the preconfigured "reporting tool". The QA technician opens a new "Bug Report" and opens the "Attach" dialog. He then selects the "File Name" edit-box and clicks Ctrl-V. The technician does not need to write a lot because every thing is described in "pictures" in the vLog report.

When the developer reads the bug report (in the reporting tool) he can double-click on the report (vLog needs to be installed on his computer). vLog will be opened displaying the report's main page.
The vLog report is "Comprehensive", "Accurate", and "Understandable".

If the developer wants to comment on the report, he can "draw" on the report's pictures or add voice-messages (comments) on the report.

In some cases, the technician doesn't want the "last" 10 actions. In these cases he can open vLog, select the "first" and "last" lines in the recording pages, and then click on the '+' button to create a report.

vLog also enable QA technicians to create a full "test" report. To do that just use the "Test" button in the "toolbar" (read the Help to understand how to use it).

vLog reports can also be created from another application, such as an "automatic regression tool" using its COM interface (read the "COM Interface" chapter in the Help).