Delivery Squash 11.0, a better sprint reporting

The delivery of Squash contains the following features:

• Multi-campaign and iteration report

• Consistency of sprints with the other objects in the Executions Workspace

  • New dashboards in sprints

  • New column "Sprint" in the search for test plan items

  • Chain execution in sprints

• GitLab token renewal

• Monitoring the progress of tests from GitLab: adding a label on GitLab issues

• More efficient integration of GitLab webhooks

• Permission customization of the Automation Workspace

• Help in selecting test cases for automation

• Securing and optimizing the deletion

  • Request for confirmation before deletion

  • Location of residual objects when deleting a project

• Renaming a user group

  
  

• Feature removals

• Deprecated features

  
  

The full list of new features and bug fixes is available on Squash TM 11.0.

Multi-campaign and iteration report

Requires the Squash Premium offer.

As part of the validation of several components and/or when the recipe is carried out by several teams, from the Reporting Workspace, it is now possible to create reports that include multiple campaigns or multiple iterations. Users can select the campaigns and iterations of their choice to generate a customized report.

The report structure has been completely redesigned to accommodate the presence of one or several campaigns or iterations within a single report.

This new type of report provides users with a detailed overview of each iteration, as was already the case with single reports (one campaign or iteration). It also allows users to obtain a global summary of key indicators:

• Number of test cases executed;

• Test results;

• Functional requirements coverage;

• Defect summary.

New dashboards in sprints

The sprints evolve and are enriched. In the Execution Workspace, a new “Dashboard” anchor has been implemented for each sprint. This provides access to a set of statistics related to the sprint, as well as an inventory of tests associated with each sprint requirement.

The dashboard displays the following key indicators and charts:

• Requirement validation status: Tracking the validation status of sprint requirements.

• Criticality of not validated requirements: Analysis of requirements remaining to be validated, categorized by criticality level.

• Coverage by test cases: Visualization of the coverage rate of requirements by test cases.

• Test case status: Progress status of tests (to be executed, in progress, passed, etc.).

• Success/failure rate: Proportion of tests that passed and failed.

• Weight of the TC not executed: Identification, by criticality, of tests that have never been run.

The addition of this dashboard gives users improved visibility into the key elements of sprint progress.

New column "Sprint" in the search for test plan items

In the Execution Workspace, a new “Sprint” column has been added to the search section, allowing users to identify the originating sprint for each test plan item displayed in the search results. This column complements the existing columns, ensuring the traceability of each test plan item’s origin, whether it comes from a campaign/iteration or a sprint.

Chain execution in sprints

In the Execution Workspace, it is now possible to chain executions from both the overall sprint execution plan and the test plan of a sprint requirement. This functionality, already available for campaigns and iterations, has now been extended to sprints.

Management of the renewal of GitLab tokens (evolution delivered in Squash version TM 10.2.0)

Squash ensures the continuity of synchronization comments in case of renewal of GitLab tokens (Project Access Token or other) involving a change of rights and/or user.

Monitoring the progress of tests from GitLab: adding a label on GitLab issues

It is now possible to quickly view the testing status of each issue in GitLab using a dedicated label. The testing status, already available in the test progression note, is now reflected as a GitLab label on the corresponding issue.

In the Xsquash4GitLab configuration, it is possible to specify the GitLab label dedicated to this information for each synchronization scope. This optional configuration is done at the Squash project level, in the “TM acceptance data reporting” section.

Once configured, the label reflecting the testing status is updated on GitLab with each synchronization cycle.

GitLab Webhooks : more efficient integration 

GitLab Webhooks are more reactive on Squash instances having a lot of GitLab synchronizations.

Permission customization of the Automation Workspace

Requires the Squash Ultimate offer.

We have finished updating the configuration of permissions for all Workspaces. In this version, it is now possible to configure the Automation Workspace, just like all the other Workspaces.

Help in selecting test cases for automation

The choice of tests to be automated is at the heart of the automation process.  A new "help" entry has been added to the automation Workspace. This new entry allows users to analyze the test cases according to predefined criteria (see documentation), in order to suggest the best candidates for automation. These suggestions can then be validated or rejected to get a consolidated, prioritized list of tests to be scripted. In addition to saving time on the analysis part, this allows to harmonize the selection of test cases to be automated based on fixed criteria.

Securing of object deletion

The handling of deletion in Squash has been optimized to enhance security and minimize handling errors. From now on, before any deletion operation, a pop-up displays the number of impacted elements, requiring an explicit numerical validation by the user to confirm the action.

This evolution concerns the objects of the libraries of the following Workspaces:

• Requirements

• Test cases

• Executions

• Reporting

• Action words

The feature is configurable at the instance level: it can be enabled or disabled. In addition, a configurable threshold allows to define the minimum number of elements to be deleted from which this confirmation procedure is triggered.

Improvement of the management of residual objects when deleting a project

When deleting a project, identifying which Workspace(s) in which elements were not deleted is simplified. The project deletion pop-up explicitly lists the Workspaces that contain active objects, effectively blocking the project deletion operation. This optimization facilitates conflict resolution.

Change of user group name

The “Test automation server” user group has been renamed to “Technical account” in order to better reflect its broader purpose: these technical users can be used for any scripts/bots accessing Squash through the REST API, not just the ones related to automated tests. With this widening, we brought back their clearance overview on the user administration screen.