test.guide 2024 Q3

Multi-value fields

The IssueTracker templates for Jira now support multi-value fields, such as keywords and labels, that can be separated by the delimiter string |||. When you create a Jira issue during the review, these fields are automatically filled in correctly based on the predefined sizes in the templates.

Definition of artifact placeholders

In the IssueTracker template, the syntax "{artifact:<file name>}" can be used to specify which files should linked directly to the artifact management in the issue. Wildcards are supported. Artifact shares are created for all files that match the specified expression <file name> and are stored in the depository (artifact management).

Jira ticket linking

Jira tickets created during a test case review via test.guide can be linked manually or automatically to existing Jira issues.

• Manually: by specifying the link type and the respective issue keys of the issues


• Automatically: if their issue keys are available as attribute or constant values in the test case execution being reviewed
  
  The automatic link can be configured in the Project settings under Issue Tracker.

Insertion of Jira asset keys

When creating new tickets in the review process, the Jira integration now also supports the insertion of Jira asset keys.

• Saving options in the playbook editor:

Save as
The new name and destination folder of the playbook can be specified.

Save
The playbook is always saved directly under the existing name and folder in the next revision.

The complexity of automotive software testing is increasing with increasing automation and integration in CI/CT platforms. Trying to manage and execute all aspects of testing and test automation, such as test cases, pipelines or test executions, directly in an ALM system like Codebeamer often leads to significant challenges. While ALM systems are excellent at ensuring product quality by managing requirements, defects, and test results, they are not optimized to be used as test platform for highly automated CI/CT processes. They do not achieve the necessary conditions for the increasing level of automation in automotive software testing.

For this reason, it is more efficient to execute the test process separately on specialized test platforms and then export the results back to the ALM system. The flexible mapping between metadata from the CI/CT environment and metadata in the ALM system enables continuous testing, e.g. commit-triggered. The relevant results can then be exported back to the ALM system.

This workflow is now available for the connection between test.guide and Codebeamer. Using templates, test.guide results can be transferred to a Codebeamer test run and are available there for further processing.