Test Case Sharing
This feature is only available in qTest Elite edition. You can create Test Runs from other projects’ that have shared Test Cases and execute these Test Runs in your own project.
1. Activating Test Case Sharing feature for a project
To create Test Runs from shared Test Cases or to share your project Test Cases with others, you will need to activate Test Case Sharing feature and select the options to be able to share or use shared test cases.
2. Sharing Test Cases from within a Module or Test Case
When the Test Case Sharing feature is activated and option Enable users to use Test Cases from other projects is selected, you will see a Shared checkbox as a Test Case/Module property. Simply select the checkbox to share individual Test Cases, or click to share a Modules and automatically share all test cases within it.
3. Creating Test Runs from shared Test Cases
On creating Test Runs, you can select any projects which have shared Test Cases to your project .
qTest now provides the ability to track the time spent executing tests and compare it to the amount of time planned for executing that test. This feature is available in qTest Elite and Enterprise editions.
Based on time tracked for each Test Log, the Rollup of time spent on the Test Run is calculated, including:
- Total Planned Time: sum of Planned Time of all Test Logs of the Test Run
- Total Actual Time: total actual execution time has been spent for all Test Logs of the Test Run
- Average Execution Time: the Total Actual Time divided by the number of Test Logs
You are able to easily see the time which has been logged on each Test Log. The project admin and the Test Log’s tester can edit the amount of time inputted on a test log.
There is a new report for the Rollup of time per Test Executions to a Test Suite/Cycle/Build/Release and the difference between planned and actual time.
1. Copy/Paste Test Steps
To save time when defining Test Cases, qTest features the ability to Copy and Paste Test Steps both within projects and across projects.
NOTE: A called Test Case cannot be copied across projects or onto itself.
2. Re-order multiple Test Steps
You can select multiple Test Steps then drag and drop to re-order them.
3. New system field – Priority
Priority is added as a system field for both Test Case and Test Run artifacts. When you create a Test Run, it will inherit the Test Case’s priority. The value can then be changed if needed.
4. Data query for Test Cases with executed Test Run instances
In Test Design’s Data Query, a new criterion has been added, Has Executed Test Run Instances, to query for Test Cases associated with executed Test Runs.
5. Test Case Traceability Matrix report – add Automation column to the exported Excel file
Bulk assigning users to projects
From Licenses – Users tab of Site Administration panel, the site admin can assign multiple users to multiple projects.
Mail Recipients Management
This feature let the site admin manage which external email addresses or domains qTest is allowed to send emails to. qTest notification emails, user invitation emails and other emails which are sent to qTest users are never blocked.
Mail a report to external users
When viewing a report, you can send the link to download exported file to either your email or any specified emails, including external users who are not qTest users.
NOTE: In case you are sending emails to external users, their emails need to be listed in Mail Recipients Management as described above.
1. Data Query for Session Manager
Now users can create custom data queries for Session Manager or quickly navigate to shared queries as needed.
- System Queries: these built-in queries allow the user to access his assigned sessions; show all Sessions or just the ones currently have assignees.
- My Queries: all previously created queries by the user would be displayed here
- Team Queries: the shared queries by others would be displayed here
2. Support Batch Edit/Delete
User can execute mass update Session Records for these fields: Title, Description, Overall Summary, Assigned User.
3. Introduce new Icon for launching Session Playback. All Action Icons are revised for better user experience
1. Replay Recorded Media
The recorded Audio / Video from eXplorer can be reviewed in Session Editor.
2. Ability to select specific Test Module when creating/updating Test Cases
3. Ability to update existing Test Case
Existing Test Case would be overridden/replaced by new information. Thus, all steps would be replaced by new steps. The Test Case version would be increased as a result.
4. Ability to update existing Defect in JIRA and qTest
Existing Defect information would be overridden/replaced by new information. In case of JIRA, native JIRA Form would show up just like when creating new defects.
5. Screens that are captured from websites would have respective URL Links for easy navigation
6. Save Defects to HTML format
7. Users can review the Session with Session Playback
This feature would replay the Session to illustrate how the original tester conducted the testing.
- Timeline Zoom In/Out: Allow users to magnify or reduce the scale of timeline as needed
- Controls for Playback: Allow users to start, stop, pause Session Playback. We can adjust the speed of playback with Slower/Faster control. The "1x" indicator would represent the current playback speed. The Next/Previous controls could be used to quickly navigate to adjacent Screens.
- Steps within Screen are the actions taken upon each screen.
- Screen Artifacts includes all additional material generated by users such as Recorded Audio, Video, Notes, Test Case and Bug. Each of these would be displayed as a dedicated icon right above the related Screen.
1. New permissions for Automation Scheduling
New permissions for manipulating schedules, including create/update/delete/view permissions:
2. Cancel automation schedules
Schedules which are Running or Not Run can be manually cancelled at any time before they are completed.
3. Data Query – Project admin can removed saved queries
4. Enhancement for requirement integration with Rally
You have an option to retrieve user stories from all child projects, regardless of the child projects’ depth of level.
5. New APIs
- Update a release
- Delete a release
- Get all builds of a release
- Get a build by its ID
- Update a build
- Delete a build
- Get a module by its ID
- Get All Modules Under Root Or A Specific Module
- Search for modules by name
- Update a module
- DELETE a module
- Get a requirement by its ID
- Get all requirements
- Update a requirement or move it to another module
- Delete a requirement
- Get a requirement's comments
- Put a comment to a requirement
Test Case APIs:
- Update a test case
- Get a test case by its ID
- Create a test step
- Update a test step
- Delete a test step
Test Cycle APIs:
- Get a test cycle by its ID
- Create a test cycle
- Update a test cycle or move it to another container
- Delete a test cycle
Test Suite APIs:
- Get all test suite fields
- Get a test suite by its ID
- Create a test suite
- Update a test suite or move it to another container
- Delete a test suite
Test Run APIs:
- Create a manual test run from a test case
- Update a test run or move it to another container
- Delete a test run