Upcoming

This feature relates to the Documents area in  Project. Specifically, it relates to those project documents that are PDF files. In the past, users could only view PDF documents by downloading them and then opening them with an external PDF viewer. This workflow has been improved. Now users can right-click on a PDF file and select  Preview PDF from the context menu. This opens the document directly in an integrated PDF viewer.

This feature relates to the presets, which can be accessed by navigating to   > Configuration > Result > Presets. The preset grid now includes a Discipline column, where you can see which disciplines apply to each preset. You can also filter or group the presets in the grid by their discipline.

Use-case: Disciplines are essentially a way to control which presets are available to which users. When a user selects a preset in  Result, they only see the presets for their own disciplines. Presets that do not match their discipline are filtered out.

This feature relates to the MDM requirements, which can be found by navigating to   > Configuration > MDM > Requirements. Specifically, it relates to the new workflow for editing multiple MDM requirements. The pop-up window now includes a Context area, where users can edit the context of multiple MDM requirements at once.

This improvement relates to the requirements grid in  Project. In the past, users were not able to delete a requirement or test case that had previously been duplicated. That means, if a copy was made of the requirement or test case, then it was not possible to delete the parent at a later time. This has been improved. Project requirements/test cases can now be deleted regardless whether they were previously copied.

This improvement relates to edit mode in  Project. In the past, users could enter status values for both active ( ) and inactive ( ) requirements. This has been changed. In edit mode, it is no longer possible to enter status values for inactive project requirements. This is useful because inactive requirements are outdated or obsolete, so no status entries should be saved for them.

This improvement relates to the preset bricks, which can be accessed by navigating to   > Configuration > Result > Preset bricks. Now users can click on a preset brick in the overview and then click on   to expand a side panel. The side panel displays detailed information about the preset brick. This information is read-only.

This improvement relates to the function for comparing videos in  Result. In the past, the preview image was not updated until the user had dragged and released the timeline. This often led to trial and error because the user could not see the preview image until it was too late. This workflow has been improved. Now users see a preview video frame while dragging the timeline.

This improvement relates to the presets in  Result. Specifically, it relates to the inline editor, where users can enter XML for a preset or preset brick. In the past, the editor did not utilize the entire screen height. That means, there was unnecessary white space underneath the editor. This has been improved.

The attachment panels in the  Result dashboard have been completely re-written such that the loading performance is increased. It uses the server-side row model, which makes it possible to partly load only the data that is currently visible. Previously, all attachments of the selected tests were loaded in multiple requests, which made the application feel unresponsive.

Due to the re-write, the following changes have been made:

• In the grid view, it is possible to group by columns, change the sort order and set column filters. This will also affect the thumbnail view. In the thumbnail view itself, it is not possible to change the grouping, filtering, or sorting.
• The quick filter is available in both views and can be set in either of them.
• The buttons next to the quick filter (left-to-right) have the following effect:
  • Reset filter: Reset all column filters and the quick filter. This has the same effect in both views.
  • Autosize: In the thumbnail view, the number of items shown in one row is adjusted to use the full width. In the list view, the columns in the grid are adjusted to fit its content.
  • Reset to default: Reset the filtering, sorting, and grouping to the default values. In the list view, it also resets the column order.
• In the thumbnail view, a double click opens the carousel instead of a single click. This change is necessary to be able to select multiple items in the thumbnail view similar to the list view. However, this feature is still under development and not yet implemented.
• Due to the use of the new grid view component, the thumbnail view has now a context menu which is similar to the context menu in the list view.

This improvement relates to the following grids:

•   > Configuration > Result > Presets
•   > Configuration > Result > Preset bricks
•   > Configuration > Result > Templates
•   > Configuration > User management > Groups
•   > Configuration > User management > Access tokens
•   > Configuration > User management > Global roles
•   > Configuration > User management > Project roles

The grid layout has been made more compact. That means, the grids no longer use the AG grid theme comfortable. Instead, they use the theme dense.

This improvement relates to the User content page, which can be accessed by navigating to   > Configuration > User content. By default, the Tag column is no longer visible in the grid. Since the grid is already grouped by tag, this column is redundant for most use-cases. If you want to see the Tag column again, you can display it by clicking on   on the far right and then selecting the column ( ).

This improvement relates to the MDM requirements, which can be found by navigating to   > Configuration > MDM > Requirements. The workflow for editing multiple MDM requirements has been improved:

1. Select multiple MDM requirements (ctrl. + click) in the overview and then right-click. A context menu will open.
2. Click on  Multi edit. A pop-up window will open.
3. Select an operation from the drop-down list and enter your text into the text field(s).
4. Click on  Change all to apply the changes to all of the selected MDM requirements at once.

Users can now be linked to specific features, and their license status can be tracked. The necessary models and API endpoints have been added to support this functionality, including the ability to view and update feature access for users.

The old-style command-line arguments and the meta.json configuration file are no longer supported. See the respective deprecation notices on how to migrate.

This fix relates to product variants in  Project. Specifically, it relates to the window where users can assign product variants to test cases. In the past, an additional checkbox was displayed in the window. The checkbox was removed since it was unnecessary and should not have been displayed.

This fix relates to the documents that can be uploaded while reporting the status in  Project. In the past, after saving the project requirement status, the document did not appear in the side panel. This behavior has been fixed. Uploaded documents are now saved and displayed correctly.

This feature relates to the status report templates in  Project. In the past, when creating a new status report, the timestamp was not displayed in the Date column. This behavior has been fixed. The creation date is now displayed in the Date column and the column can be used for filtering.

This fix relates to the Documents area in  Project. In some cases, the file upload can fail, e.g. if a user tries to upload two documents with the same name. In the past, no error message was provided to users, and the grid became unresponsive. This behavior has been fixed. Users are now notified of the error and they can continue uploading other documents.

This fix relates to edit mode in  Project. In the past, if a user entered the value ‘0’ into a cell and pressed ‘Enter’, then the cell was displayed as being empty. This behavior has been changed. Zero values are now correctly displayed.

Previously, some tests could not be deleted due to incorrect attribute references in the column-to-test cache. Since aggregated entries represent combined data from multiple attributes, there should not be any reference. This is now done correctly.

This fix relates to the Set as project status function in  Result. Specifically, it relates to situations when users manually assign test cases. In the past, inactive test cases were displayed in the Project test cases drop-down list. This did not make sense because it is not possible to have active requirements belonging to an inactive test case.

This fix relates to the scenarios in  Result. Specifically, it relates to scenario nodes that include further, subordinate nodes. That means, the scenario nodes that can be expanded ( ) to reveal additional nodes within. In the past, if a user selected such a node ( ), the check mark was immediately removed again. This behavior has been fixed.

This fix relates to the collections in  Result. Specifically, it relates to situations when users add tests to a collection that already holds a large number of tests (~100 or more). In the past, while adding new tests to the collection, some of the existing tests were removed. This behavior has been fixed.

This fix relates to the function for manually creating a new test in  Result. Specifically, it relates to situations when the test is created with a template. In the past, it was not possible to select and save attribute values from the value list. This behavior has been fixed.

This fix relates to add-ons with configuration keys. Specifically, it relates to confidential keys, e.g. access keys or api keys, which are displayed as a string of bullet points. Confidential keys can contain text with new lines. In the past, this text was all rendered in one line and the new line characters were omitted in transmission to the server. This behavior has been fixed. New lines are now preserved.

This fix relates to the following pages:

•   > Configuration > User management > Users
•   > Configuration > User management > Groups

Specifically, it relates to the chip that indicates the number of Additional permissions that were assigned. In the past, the chip sometimes showed the wrong number of permissions. This was because the internal tree nodes were also being counted as permissions. This behavior has been fixed.