Menu

qTest Manager 8.7 OnDemand Release Notes - August 28th, 2017

New Features

Site-level Field Settings

This feature allows standardized fields which will be shared across your qTest Manager projects.

Managing Site Fields

Site fields are defined and configured in Administration panel. To manage site fields, site administrators must have Manage Site-Level Field Settings permission.

The Manage Site Fields page is the same as Field Settings page under a project. You will be able to:

  • Browse through the fields of different qTest Manager’s Artifact types
  • Modify system fields
  • Create and modify custom fields
  • Define values for picklist typed fields

Managing Field Templates

  • A Field Template includes some or all of site fields. Once you apply a Field Template to projects, these projects will use the same set of site fields included in the Field Template. Any update on the site fields will flow down into the projects
  • A Field Template can be applied to multiple Projects, but one Project can only be associated with on Field Template

Applying a Field Template

You are able to apply a Field Template to your existing projects with their own Field Settings. The system will merge the site fields and values with the project fields and values. You will have a chance to preview the mapping between site fields and project fields before proceeding

  • System fields are merged using the original names
  • Custom fields are merged using field names and field types
    • Custom site fields which do not match with any project custom fields will be created as new custom fields in the applied projects
    • Custom project fields which do not match with any site custom fields will remain as internal project fields
  • For picklist typed fields, values from the site fields and projects fields are merged using their display name
    • Project values which do not match with any site values are added to the site fields
    • Site values which do not match with any project values will remain in the site fields

Updating site fields

  • Once a template is applied to projects, any updates on the site fields will flow down into the project field settings
  • Site fields which are removed from a Field Template will become inactive in the associated projects, but you are still able to reactivate them
  • Site fields which are added to a Template will be merged with project internal fields using the same rules as for applying Field Template

Managing Project-level Field Settings

  • In Field Settings page of a project which has been associated with a Field Template, the project admin will be able to view which fields are site fields and which ones are internal project fields
  • Site fields cannot be modified or deactivated within a project
    • You are able to mark a site field Searchable within a project
    • You are able to reorder all fields
    • For picklist field types, you are able to select which values are inactive within your project and select other default values than the selected on the Site-level Field Settings

Please refer to this article for more details of how to use the Site-level Field Settings

Test Automation Scheduling Updates

New Shell Agent

  • We are introducing a new plugin, the Shell Agent plugin, which is capable of kicking off shell scripts (Linux and MacOS) or batch scripts (Windows)
  • The Shell Agent is the newest option in the Test Automation Scheduler that offers a high level of flexibility including:
    • Ability to schedule automated test execution (for tests in any framework and language, including custom frameworks)
    • Automation scripts can be stored in a file that is located in the local machine or in a shared network directory
    • Ability to kick off commands, shell / batch scripts, or executable files that are executable from your console or terminal.
    • Ability to define which test runs get executed and how the results will be passed into Test Execution (by using APIs)

Using information passed from qTest Manager in your scripts

  • When Test Runs are scheduled from qTest Manager UI, extra data of these Test Runs and their Test Suite are passed along with the schedule to the agent
  • You can pass those data using command arguments to your kick-off scripts

Filters on Test Run grid

  • You can filter Test Run grid in Release, Test Cycle and Test Suite pages using any Test Run fields, except for multiple picklist typed fields
  • The applied filters will not be retained after you logged out or close your browsers

API Updates

The following updates are applied to these 2 APIs Submit Test Log and Submit Automated Test Log:

  • The enhancement allows you to update Test Run system and custom fields, except for the read-only fields, before submitting results to the Test Runs
  • The submitted Test Log will inherit the latest field values from its associated Test Run
  • There is a difference between updating Test Runs using qTest Manager UI and using this API
    • In qTest Manager UI: once a Test Run is executed, its Environment field becomes read-only
    • Using API: Environment field is editable even when the Test Run has been executed

Bug Fix

  • 9914 - Closing Defect Submission screen without saving the new Defect will not send out an notification email

Known Issues - Limitations

  • Currently you will not be able to enter multiple commands into the Shell Agent
  • You are able to select no default values for Defect Status field in Site-level Field Settings. When applying this site field in a project with Defect Workflow enabled, your users will not be able to submit new defects. Workaround: project admins please access to the project Field Settings and select a default value for Defect Status field
Subscribe To Our Blog
Powered by Zendesk