0.59.0

This feature relates to the Add MDM test cases to project window in  Project. Now when users hover their mouse cursor over an icon in the column State or In project, they see a tooltip that gives the meaning of the icon. The following tooltips are displayed:

State:

 : Active
 : Inactive

In project:

 : In project
 : Not in project

This feature relates to the following grids:

• The requirements grid in  Project
• The MDM requirements grid under   > Configuration > MDM > Requirements
• The MDM test cases grid under   > Configuration > MDM > Test cases

Now when users hover their mouse cursor over a cell in the column Comment or Description, they see a tooltip that provides the full text. This is useful for longer texts that are cut off at the end of the cell and thus not fully readable.

This feature relates to product variants in  Project. Specifically, it relates to the window where users can assign product variants to test cases.

Checkboxes are now displayed next to the column headers in this window. The checkboxes allow users to select/deselect all of the test cases at once. This is useful e.g. for variants that should be assigned to a large number of test cases. Users save time because they no longer need to select each test case individually.

This feature relates to the requirements grid in  Project. When users group the requirements by test case and then select a single test case, detailed information about the test case is now displayed in the side panel.

This feature relates to the requirements grid in  Project. Specifically, users now see a button called  Edit mode in the lower left corner of the grid. When users click on this button, they are able to edit the columns of the requirements grid as they would an Excel spreadsheet. That means, they can enter values directly into the requirements grid, e.g. when reporting a status.

This feature relates to product variants in  Project. Specifically, it relates to the window where users can assign product variants to test cases. In the past, when selecting a group of test cases, it was only possible to assign variants to the entire group. That means, the Assign product variants window listed the entire group as one entry (see screenshot).

This has been changed. Now if a user selects a group of test cases, then each test case is listed separately in the Assign product variants window. That means, the user can assign each test case to the appropriate variants.

This feature relates to the requirements grid in  Project. When users group the requirements by test case and then select a single test case, the side panel now includes an area called Documents. Here, users can upload/download documents for the project test case.

This feature relates to the requirements grid in  Project. Specifically, it relates to the Status area of the side panel, where users can report the status of a requirement. In the past, users could report the status of both active ( ) and inactive ( ) requirements. This has been changed. The Report status button is now disabled for inactive project requirements. This is useful because inactive requirements are outdated or obsolete, so no status entries should be saved for them.

This feature relates to product variants in  Project. Specifically, it relates to the window where users can assign product variants to test cases.

• If the user has not yet selected any variants, then they see a button called  Skip. The user can click on this button to continue without selecting any variants.
• As soon as the user selects a variant, the button name changes to  Confirm.

This feature relates to the column filters in  Result. Now when users apply column filters, the column filter icon (A) is displayed in red, just like the global filter icon (B). This red highlighting helps users more easily recognize any columns that are currently filtered.

This feature relates to the calculation rules, which are found under   > Configuration > MDM > Calculation rules. This menu now includes a  New button, which allows users to manually create new calculation rules. In the past, calculation rules could only be migrated into the menu from other systems.

This feature relates to the functions for adding or editing a MDM requirement. The MDM requirement edit page now includes a field called State. This field allows users to specify whether the MDM requirement is active or inactive.

This feature relates to user permissions. Sometimes it is necessary to remove all user object permissions for tests in a specific bes project. This is now possible by sending an empty permissions matrix.

Models are separated into multiple parts on the server side. This sometimes creates inconsistencies. For example, when a user reports a value for a requirement or updates its thresholds, the requirement itself should also be updated. In the past, this was not always the case. That means, e.g. the requirement’s ‘updated_at’ time was not always correct. This behavior has been fixed.

This improvement relates to the requirement grid in  Project. The following column headers were renamed for clarity:

• Created by was changed to Modified by
• Created at was changed to Modified at
• Status > User was changed to Status > Changed by
• Status > Created at was changed to Status > Changed at

This improvement relates to the requirements grid in  Project. Specifically, it relates to situations where the user has grouped the requirements by test case and then selected multiple test cases (ctrl. + click). Now when the user right-clicks, the context menu includes the option Remove # test cases. This option deletes all of the selected test cases.

This improvement relates to the requirements grid in  Project. Specifically, it relates to situations where the user has grouped the requirements by test case and then selected multiple test cases (ctrl. + click). Now when the user right-clicks, the context menu includes the option Toggle active for # test cases. This option toggles the state of all selected test cases (active and inactive).

This improvement relates to the Create new test page in  Result. Specifically, it relates to the Add metadata templates area. In the past, if a user entered a value into the Value column, then he needed to confirm this value (by pressing Enter or clicking on a different cell) before saving. This has been improved. Now users can enter values and directly press the save button. Users no longer need to confirm the values first.

This feature relates to product variants in  Project. Specifically, it relates to the window where users can assign product variants to test cases.

• The window now has an expand icon ( ) in the upper right corner. Users can click on this icon to maximize the window.
• The window can now be resized as needed. Users can click and drag the lower right corner to resize the window.

This improvement relates to the views that can be used e.g. in the requirements grid in  Project and in the test grid in  Result. Now when users click on   to access additional options in a context menu, they will see that the option Save as new has been renamed to Duplicate. The option was renamed to provide a more accurate description of its function.

• This improvement relates to the wording used in the front end. For example, the browser tab CAViT has changed to Result.
• This improvement relates to the URLs of sub-pages within the application. For example:
  • https://example.eu/cavit/dashboard changed to https://example.eu/result/dashboard
  • https://example.eu/statuse/projects changed to https://example.eu/project/projects

Existing bookmarks pointing to sub-pages of the application will no longer work. Please update your bookmarks to ensure continued access to the desired pages.

This fix relates to the requirements grid in  Project. In the past, an error occurred when starting an add-on on a group of requirements. This behavior has been fixed.

This fix relates to the requirements grid in  Project. In the past, when loading a view that includes a filter for a context column, the filter was not applied. This behavior has been fixed.

This fix relates to the product variants in  Project. When creating new product variants, users can save context attributes to specify e.g. whether the variant is related to a specific directive, configuration, type of dummy, etc. These context attributes are now visible to users in the overview of product variants.

The parameter as_of is used, for example, when filtering by status reports. An error was therefore displayed in the application when working with status reports.

This fix relates to the function for reporting the status of a requirement in  Project. While reporting the status, users can upload any relevant documents. In the past, the attached documents were no longer shown after saving. This behavior has been fixed.

This fix relates to the Add MDM test cases to project window in  Project. Specifically, it relates to situations where the test cases are grouped, e.g. by region or directive. In the past, if a user selected ( ) a group of test cases and then changed their mind and deselected the group again ( ), the deselected group was added to the project upon saving. This behavior has been fixed. Deselected groups are no longer added to the project.

This fix relates to the MDM requirements, which are found under   > Configuration > MDM > Requirements. Specifically, it relates to the History area within the side panel. In the past, this area displayed entries relating to the corresponding project requirements. This behavior has been fixed. The area now only displays those entries relating to the MDM requirement.

This fix relates to the requirements area in  Project. In the past, users who had access to a project were able to see and open the menu entry Requirements, even if they did not have permission to see the project requirements. In the past, the page would open and the grid would display ERR. This behavior has been fixed. Now the menu entry is invisible to users who do not have permission to actually access it.

This fix relates to the test grid in  Result. In the past, when sorting and grouping by the same column, the test results were not displayed in the correct order. This behavior has been fixed.

This feature relates to the Edit tests window in  Result. In the past, the functions for maximizing and resizing the window were not working correctly. This behavior has been fixed.

• The window can be maximized again by clicking on the icon ( ) in the upper right corner.
• The window can be resized again by clicking and dragging the lower right corner.

This fix relates to the Set as project status function in  Result. Specifically, it relates to the debug view and the detail view. In the past, these views were empty. This behavior has been fixed. The views now show the correct information.

This fix relates to the test grid in  Result. In the past, if a user maximized the test grid by clicking on the   icon in the upper right corner, then the context menu stopped working. That means, when a user right-clicked on a test, the context menu did not appear. This behavior has been fixed. The context menu now appears regardless whether the test grid is maximized or not.

This fix relates to the videos tab in  Result. In the past, when a video was uploaded, the conversion function sometimes produced a web video derivative that was not playable in the carousel. This behavior has been fixed.

This fix relates to the test grid in  Result. In the past, selecting specific tests caused the Events tab to freeze. This behavior has been fixed.

This fix relates to the Edit tests window in  Result. The window size has been fixed.

This fix relates to the test grid in  Result. Specifically, it relates to attribute values that have line breaks. In the past, if a user grouped the tests by a column with line breaks, then the data in the grid became unreadable. This behavior has been fixed. Line breaks are no longer displayed in group titles.

This fix relates to the Edit tests window in  Result. In the past, users were not able to switch between preset tables in this window because the drop-down list in the upper right corner was not working correctly. This behavior has been fixed.

This fix relates to the test grid in  Result. Specifically, it relates to the views that can be loaded by clicking on the   icon in the upper right corner of the grid, then clicking on  Views and finally clicking on the name of a view. In the past, the view was not correctly loaded and an error occurred. This behavior has been fixed.

This fix relates to the MDM requirements, which are found under   > Configuration > MDM > Requirements. Now if the requirements are grouped, e.g. by test case, a context menu is no longer displayed when right-clicking on the group header. In the past, a context menu was incorrectly displayed, and users received an error when starting an action from the context menu.

This fix relates to the attachment side panel under   > Configuration > MDM > Test cases. In the past, attachments were not correctly displayed when using the browser Firefox. Specifically, when a user uploaded files in the Attachment area, these files were not immediately displayed. The user had to manually reload the menu and re-open the MDM test case in order to see the new files. This behavior has been fixed.