Desktop Editor UI Revamped
The Desktop Editor UI has been changed to better display information of a recorded session as well to accomodate new functionalities.
The Screens tab allow user to edit the captured screenshot with the built-in annotation tools.
The Properties tab shows basic information of a session: the Project field shows name of the project this session belongs to, the Planned and Actual field shows the planned and actual duration of the session, the Executor show the user name who recorded that session, etc.
The Linked Objects tab provides functionalities to link objects to the recorded session which are either qTest's requirements, test cases, test runs, internal or external defect, or attach more resources to the session.
New feature: Automatically object linking:
- When a recording session is linked to a defect, if that defect was linked to a test run, the session will also be linked to that test run
- When a recording session is linked to a test run, it will also automatically be linked to the test case associated with that test run. In addition, if the test case was linked to a requirement, the session will also be linked to that requirement.
The Environment tab show the environment information and the applications under recording and the time break down.
- When update an existing test case, Precondition and Description of the existing test case are not populated
- When submitting a new defect, although you can assign owner accounts that do not have proper permissions for the selected project, these owners will not be able to view the created defect later
- Cannot retrieve custom fields from FogBugz
- Cannot set a value for the field “Notify More Users” and this field is excluded from defect submission to FogBugz
HP Quality Center (HPQC)
- Cannot submit defect with dependent fields that need to be verified
- In Explorer Editor, Primary and Secondary Fields may not be displayed in order
- In Manage Dependency Rule setting, Explorer only supports creating dependency rules among Dropdown List fields
- If dependency settings in qTest Explorer are different than the settings in HPQC, the defect can be submitted to HPQC but the values in dependent fields will not be the same as the HPQC settings
- Special characters are not supported
- Dependent fields are not supported
- When the field control type is “TreePath”, a textbox is displayed instead of the TreePath control
- Cannot add custom field if JIRA’s version is earlier than v4.4.x.
- On Windows 10, if Chrome is the default browser then URLs from Explorer will not be redirected correctly. This is a bug from Chrome (https://code.google.com/p/chromium/issues/detail?id=514162)
- When launching multiple Chrome instances with the same titles, the Always On feature will not be triggered
- Chrome / Firefox / IE: Cannot capture characters typed into a Rich Text Editor control
- Chrome: when capturing user action on <select> element, qTest Explorer only captures the default selected value, not the value that user picks up
- Terminal Screen: qTest Explorer sometimes cannot record typed characters after pressing the Tab key
- The context menu of qTest Explorer in the taskbar of the Dependent mode (when qTest eXplorer is launched from qTest) only supports Record mode (it does not support Snapshot)
- jQuery: Will not recognize any control on IE8 – Windows Vista
- Cannot capture characters typed into a RichText box
- MFC: Cannot capture the tab name of a Tab control
- WinForm: Captures the Picture Box control as “Click here”.
- Captures the ExpandBar control as “Click here”
- Captures the Slider control as “Click here”
- Captures the SplitPane control as “Click here”
- Cannot capture content of the Jtable control
- Extended monitor
- Incorrect image captured when the taskbar has two rows, a part of the taskbar is included in the images
- Capture console: Cannot capture context menus & dialogs on XP and Vista.
- Captures entire text on notepad or text area
- Un-recognized UI controls will be captured with generic descriptions such as ‘‘Click here’’ or ‘‘Type here’’
- Cannot define hotkeys with the following combinations:
- Only number (e.g.1, 2…) or only letter (e.g. a, b…)
- Alt + <key> (e.g. Alt + R)
- Alt + Shift + <key> (e.g. Alt + Shift + C)