This new module is included in qTest’s Enterprise edition. It is responsible for handling unstructured testing Sessions which do not contain step by step details or pass/fail type of results. qTest is now the only product on the market to explicitly support scripted and unscripted manual testing, as well as automated testing results.
* Note: While this module is a central place to manage Sessions, you will need to install our Integrated eXplorer, Web eXplorer or Mobile eXplorer on your machine to execute them. They can be downloaded from qTest’s Resources page, shown below:
2. Session detail page:
Sessions are centrally stored in qTest. There you can review details of each Session, including its status, a pie chart with specific duration of time types (for completed sessions) and application/system information related to the system it was executed on.
3. Session Editor
Sessions can be reviewed and edited using our Session Editor.
With this feature, you can:
4. Linkage of a Session to Requirements, Test Cases, Test Runs or Defects:
Submitted Defects and Test Cases from eXplorer are displayed in Resources section of Session detail page. A Session can also link to Requirements or Test Runs. Moreover, links from a Session to any existing objects within the project can be manually added or removed.
eXplorer Settings page:
eXplorer settings can now be managed in the cloud for all eXplorer instances, saving time in administration and creating consistency across all eXplorer users.
Test Run Enhancements:
1. Revised Execution Structure:
Currently, the hierarchical structure of Test Execution tree is as: Release > Test Cycle > Test Suite > Test Run. A Test Cycle can only contain Test Suites or Test Runs, which creates a disconnect between the test execution structure and the requirements/test execution structure.
This release features the ability to add an unlimited number of Test Cycles under another Test Cycle. With the enhancement, Test Cycles can be used as a folder structure to group Test Runs, allowing you unlimited levels of depth in your execution structure.
2. Execution with a recorded Session
For Enterprise users, you have an option to create a Session to record your activities when executing Test Runs or Test Suites. The selection can be set at Project level and you can modify your preference freely.
In the Session, there will be links back to the executed Test Runs.
3. Enhanced Execution History table
Columns can be resized and retained for your next login on the same browser and machine.
Rally Integration Enhancements:
1. Requirement Integration enhancement – Ability to retrieve objects by a query
While configuring Requirement retrieval from Rally to qTest, you can input a query to retrieve only the requirements which meet your specific conditions.
2. Test Cases are also created in Rally
When a Test Case is created and linked to a Requirement imported from Rally into qTest, a Test Case is also automatically generated and linked to that User Story in Rally. With this ability, you can utilize Rally reports to do statistics on these objects.
* Note: Test Cases and their associations with User Stories will not be updated or removed in Rally, regardless of any changes in qTest.
3. Project names are fully displayed
Rally support multi-level projects. In the integration configuration page of qTest, the project name and its path are fully displayed.
* Note: This enhancement only affects the object types configured after this release.
1. Defect Import (Beta function)
If you have a list of defects in Excel files you would like to migrate into qTest, you can import them to qTest using our new import wizard, which is currently in beta.
2. New report – Test Run Summary by Assignees
This report provides the statistic of Test Runs assigned to the team members. It can be filtered by Releases, Cycles and Assignees.
3. IE 10/11 support
IE 10 and IE 11 are now in our support list along with our currently supported browsers (Firefox, Chrome, Safari, IE8 and IE9).
On Windows 8, IE 10 is divided into two editions: Metro application and traditional desktop application. Currently, we only support the traditional application.
4. Linkages to Sessions in object detail pages
If an object (Requirement, Test Case, Test Run or Defects) has associated Sessions, the links to these Sessions are displayed in Session List section.
5. JIRA configuration – Enhanced performance to shorten the configuration page’s loading time.