0.55.0

Add-ons can specify how they work with a special meta.json within their root folder. The file has been reworked and a new .addon.yaml has been introduced. This opens up more features.

This feature relates to two areas:

• The MDM test cases, which are found under   > Configuration > MDM > Test cases. Now you can add entire groups of requirements to a test case. This saves you time because you do not need to add each requirement individually. Further information.
• The requirements grid in  Project. Now you can add entire groups of test cases to a project. This saves you time because you do not need to add each test case individually. Further information.

This feature relates to the requirements grid in  Project. When you right-click on a requirement, the context menu now includes the following options:

•   Compare test case to MDM
•   Compare single requirement with MDM

Use case: MDM test cases and MDM requirements occasionally need to be updated, for example, if the context has changed. Now project managers can easily compare their project test cases and project requirements with the MDM equivalents, and adopt the changes as needed. This means, project managers now have a tool to easily keep their projects up-to-date. Further information.

Note: It is also possible to select multiple requirements in the grid (ctrl. + click). In this case, the options in the context menu have slightly different names. For example, if you select two requirements, then the options are called   Compare 2 test cases to MDM and   Compare 2 requirements with MDM.

There is now a new area called Status report templates, which is found under   > Configuration > Project > Status report templates. Here, MDM managers can add new status report templates and modify existing templates.

Note: Only users who have the permissions under Others > Status report template are authorized to create or modify status report templates. Please adjust your permissions and roles accordingly.

This feature relates to the requirements grid in  Project. There is a new area that displays status report templates next to the project requirements grid. Here, product managers can:

• add status report templates to the project. This makes them available for reporting by simulation / test engineers.
• view status reports grouped by template.
• filter the requirements in the grid, i.e. only display those requirements that relate to a specific status report template.
• delete status report templates that don’t have public/private status reports attached to them.
• toggle active templates that already contain public/private reports.

This feature relates to the test grid in  Result. Specifically, it relates to the Photos and Videos tabs. If the tab contains a large number of photos/videos, then the user can click on   to display the photos/videos as a list. Now users can select the relevant photos/videos (ctrl. + click) and right-click to open a context menu with the option Open carousel. This option only displays the selected photos/videos in the carousel, rather than all of the photos/videos that are included in the tab.

This feature relates to the MDM test cases, which are found under   > Configuration > MDM > Test cases. Now you can click on a test case in the overview and then click on the   icon to expand a side panel. The side panel displays details about the test case and its context.

This feature relates to the requirements grid in  Project. Here, users can see a requirement’s state, i.e. they can now see whether a requirement is active or inactive. This feature includes the following aspects:

• Individual project requirements now include a State field. When editing a requirement, users can specify whether the requirement is active or inactive.
• The requirements grid now includes a State column. Requirements can be grouped, sorted and filtered by their state.
• If requirements are grouped by test case, then the state of the test case is also displayed.
• The context menu now includes the options Toggle active test case and Toggle active requirement. These options allow users to activate/deactivate test cases and requirements directly in the grid.

This feature relates to the MDM test cases grid, which is found under   > Configuration > MDM > Test cases. This grid now includes a Discipline column, which shows the disciplines that were selected for the test case. It is also possible to group, sort and filter test cases in the grid by their discipline.

This feature relates to the global roles, which can be accessed by navigating to   > Configuration > User management > Global roles. It is now possible to click on a role in the overview and then click on   to expand a side panel. The side panel displays a read-only permission tree, which allows users to see which permissions are set for the role.

Note: The side panel is accessible to users who have the permission Can view role and to users who have the permission Can change role. However, the permission tree in the side panel is always displayed as read-only. That means, users who have editing rights can not edit the permissions in the side panel. They need to navigate to the edit page to do so.

This improvement relates to the function for comparing requirements and test cases with MDM. The following fields are now also included in the comparison screen:

• Active
• Test result identifier
• Attribute key

This improvement relates to all of the grids that use the view feature, e.g. the test grid, MDM requirement grid and project requirement grid. Once a user has configured a view, the view is automatically selected.

This improvement relates to the jobs list, which can be accessed by clicking on   in the tool bar. The jobs list now includes an Updated at column, which specifies when the job was last modified.

This fix relates to those menus that have a sidebar, e.g. the requirements grid in  Project. Here, users can click on   to expand or collapse the sidebar. Furthermore, users can resize the sidebar by dragging its edge. In the past, if a user resized the sidebar, and then resized the entire window, the sidebar’s resize function was suddenly broken. This behavior has been fixed.

This fix relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. Specifically, it relates to the debug view, which can be accessed by clicking on   on the far right. In the past, if a user changed an input attribute and clicked on Calculate again, then all of the input attributes were updated (even the attributes that were not changed). This led to a problem if the unchanged attributes were write-protected. This behavior has been fixed. Now only those input attributes are updated that were actually edited.

In the past, new workspaces were occasionally saved to the backend despite there already being a workspace available for the selected preset. This resulted in the number of workspaces accumulating and the performance decreasing. This behavior has been fixed.

This fix relates to the jobs overview, which can be accessed by navigating to   > Configuration > Jobs. In the past, the job details could not be opened in a new tab. This made it difficult for users to work with jobs efficiently. For example, there was not an easy way for users to compare multiple jobs. This behavior has been fixed. Users can now right-click on a job and open its details in a new tab.

This fix relates to the jobs list, which can be accessed by clicking on   in the tool bar. In the past, the grid was not successfully loaded and an error was thrown. This behavior has been fixed. The grid is now correctly initialized.

This fix relates to the jobs overview, which can be accessed by navigating to   > Configuration > Jobs. In the past, the overview displayed tasks from other users. This behavior has been fixed. Users now only see their own jobs.

This fix relates to the jobs overview, which can be accessed by navigating to   > Configuration > Jobs. In the past, the overview displayed state icons in black and white only. As a result, the icons were difficult to tell apart. This has been fixed. The icons are now displayed in color.

This fix relates to the requirements grid in  Project. Specifically, it relates to the comments that can be entered while reporting the status. In the past, line breaks could be entered into the comment field, but they were lost upon saving. This behavior has been fixed. Line breaks are now correctly displayed in the comments.

This fix relates to the add-ons, which can be accessed by navigating to   > Configuration > Add-ons. Specifically, it relates to those add-ons that are executed periodically ( ). In the past, the add-on’s modification date, i.e. the date displayed in the Modified column, was changed each time the add-on was executed. This behavior has been fixed.

This fix relates to the documents that are saved in  Project. In the past, the Upload column was empty. This has been fixed. The Upload column now displays the date and time when the document was uploaded.

This fix relates to the Apply calculation rule function, which can be accessed by navigating to  Result and right-clicking on a test in the grid. Specifically, it relates to the debug view, which can be accessed by clicking on   on the far right. In the past, when a user right-clicked on a result, the Debug context matching context menu was grayed out. The context menu remained disabled until the attributes had finished loading. This was misleading as it suggested that the debug context matching was not available. This behavior has been fixed. The context menu is now enabled by default.

This fix relates to the documents that are saved in  Project. In the past, when loading many project documents, e.g. over 100, the loading indicator got stuck and was displayed infinitely. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, the grid did not automatically refresh after adding a test case. That means, the newly added test case was not automatically displayed in the grid. This behavior has been fixed.

The package can be downloaded by navigating to   > About. The download link is located at the bottom of the page. Here you will also find a short text, which provides further information about the package.