Skip to content

Squash TM 4.X Release Notes

Squash TM 4.0.0

Released on July 28 2022

Evolutions

  • Requirements:

    • High-level requirements taken into account in default and custom dashboards
    • Import/Export of high-level requirements
    • Convert a high-level requirement into a standard requirement
    • Add a "Last execution" column in the "Test cases verifyng this requirement" table
    • Add a "Coverage" indicator in the "Coverage indicators" block
  • Test cases:

    • Keep the previously selected keyword when adding a new BDD step
    • Add the "No test step/Has test steps" information in a BDD test case tooltip
    • Copy/Paste a BDD test step
    • Filter by project BDD actions suggestions
    • Choose between creating a new action and linking it to an existing one when adding or modifying a BDD test step
    • Add a case-insensitive action in the Action Words Workspace
    • Bulk modification of "Automated test technology" and "URL of the source code repository" test case fields from test cases search page
    • Add a "None" value in the automated test technology list for a test case
    • Test setup/teardown support in the .robot files generated from BDD test cases
  • Campaigns:

    • Only the filtered ITPI are taken into account when mass running tests
  • Issues:

    • Mantis REST Bugtracker Connector (replaces the existing Mantis SOAP Bugtracker Connector)
    • Export "Known issues" tables
    • Do not display the same issue twice in the "Known issues" tables and in the "Iteration and Campaign report"
    • Display the issue status in the execution steps
  • Reporting:

    • Editable requirement report revamping
    • Editable test case report revamping
    • High-level requirements taken into account in the editable requirement report
    • Add an option to print folder information in the editable requirement and test case reports
    • Add an option to print associated test cases in the editable requirement report
    • Add an option to links between requirements in the editable requirement report
    • "Equal" filter no longer case-sensitive in custom charts
    • Unselect a workspace when displaying a favorite dashboard
    • Export only the last execution for each ITPI in the campaign custom export
    • Display images in editable reports
  • Automation:

    • Define default environments for Squash AUTOM test automation servers and projects
    • Select the execution environment when running automated tests with Squash AUTOM
  • Administration:

    • Configure the BDD action words case-sensitivity
    • Display inactive users in grey in the administration tables
    • Automatically select an element after its creation
    • Export the "Users" table
    • Export the "Projects" table
    • Display the license information
  • Transverse:

    • Save modifications when clicking outside a "dropdown list" field
  • Xsquash4Jira:

    • Limit permissions of Xsquash4Jira synchronizations
    • Add project_id and project_name fields in the API GET synchronization response
    • Reduce the volume of logs about Jira reporting by modifying the logger level from warn to debug
  • Xsquash4GitLab (new plugin):

    • Synchronize GitLab issues as requirements
    • Display coverage and testing indicators in GitLab issues
  • REST API:

    • Add and delete a link between a test case and a requirement
    • Get, add and delete a link between a test step and a requirement
    • Add and modify automated script fields of the test case
    • Get, add and delete user permissions
    • Filter on projects or project templates when getting all projects
    • Add an automated test technology
    • Add and modify a requirement version
    • Harmonize URL to link a test case to a requirement:
      • Former endpoint: /requirements/{ids}/coverages with a "testCaseIds" parameter with the ids of the test cases to associate
      • New endpoint: /requirements/{ids}/coverages/{testCaseIds}, e.g.: /requirements/2/coverages/24,26,27
    • Get requirements, test cases and campaign tree structures
  • Admin REST API:

    • Get, add and delete links between a Squash TM project and bugtracker projects
    • Add a 'squashAUTOM' test automation server
    • Get and configure a server 'token' credentials
    • Choose whether to clone or not a repository when adding it
  • Technical:

    • Install plugins in subdirectories of the install directory

Corrections

  • Requirements:

    • Obsolete requirements are not filtered in the coverage indicators of a high level requirement
    • In milestone mode, the coverage indicators of a high level requirement take into account the requirements not linked to the milestone
    • Impossible to create a new requirement version with import, after created a child requirement with the same import
    • Confict between a requirement and a folder, a requirement can be seen as a folder in some cases
    • When exporting requirements from the search page, only the main tab is filled, other tabs are always empty
    • "Donuts" charts' tooltips are truncated when the dashboard page is not expanded
    • "Milestone" and "High level requirement" attributes are in the wrong place on a standard requirement's print page
    • Incorrect known issues count for a high level requirement
    • Standard requirement path not displayed when hovering the project in the "Standard requirements linked to this high-level requirement" block of a high level requirement
    • Impossible to print a requirement if there are issues attached to it and the user is not connected to the bugtracker
    • Wrong link to redirect to a high level requirement from the search page
    • When a standard requirement is turned into a high level requirement, it is moved out of a project in the library
    • Test cases from other requirements can be displayed in the "Test cases verifying this requirement" block of a high level requirement
  • Test cases:

    • Error when viewing or transmitting a Robot Frameword BDD test case if a dataset is defined, but no parameters are in the steps
    • The "action" field of a BDD step does not save or close automatically when clicking out
    • The online help for the "Automated test reference" field is incorrect
    • Test case name not truncated in "Test case called by"
    • Icon in the library not updated automatically when pasting steps
    • "Automated test technology" field not automatically filled for Cucumber
    • Bad management of string containing only digits in Cucumber BDD test cases
    • Fixed and variable parts of an action are not in the right order when adding a BDD step with a h2 database
    • "Verified requirements" default sorting is incorrect
    • 8617 Wrong parameter values if several parameters have the same name when calling a test case
    • Impossible to view an action details when creating the action from a BDD test case without refreshing the page
    • In milestone mode, with a locked milestone, grey out the "Add a new version" option when the test case is linked to a locked milestone
    • In milestone mode, with a not locked milestone, it should be possible to create a new test case version even if it is linked to a locked milestone
    • The formatting is lost when the steps are displayed in collapse mode
  • Campaigns:

    • The test suites list is not in alphabetical order in the "Modify the attributes" popup
    • 8909 Impossible to delete a campaign linked to a "In progress" or "Finished" milestone
    • An error message is not displayed if we type a campaign/iteration end date anterior to the start date on the keyboard
    • 8826 Impossible for a campaign and an iteration to have the same scheduled/actual start/end date
    • Rich text custom fields are not displayed properly in the execution popup when they have a long text
    • 8840 Impossible to delete a campaign or iteration containing a automated suite
    • The "Status" sorting order is incorrect in the IPTI search page
    • 8847 "Real vs planned progress" misleading depending on the scheduled and actual dates
  • Issues:

    • 8874 Displayed fields incoherent with the ticket type in the "Report an issue" popup with Jira
    • 8929 Issues reported on Redmine are linked to the wrong tracker
    • 8852 Various delays in the "report an issue" form with Jira Server
  • Reporting:

    • In campaign custom export, empty custom fields are not all valued with 'n/a'
    • When a report is generated from a tags selection, I can see all projects, even if I am not authorized
    • Impossible to generate a campaign custom export which has custom fields associated with test cases and test steps
  • Administration:

    • 8851 Impossible to delete a project if it is in a proect filter
    • Error when deleting a source code management server used by test cases
    • 7775 port used to communicate with Squash Orchestrator cannot be configured
    • 8928 Impossible to delete a project if it contains action words
    • Display issues when modifying the bugtracker type with another authentication protocol
  • Transverse:

    • Prefix in the name of the requirement and test case import report is added twice
    • In the requirement and test case import report, the number in the LINE column does not match the line number in the file
    • Wrong icon for a dashboard displayed from a custom selection
    • Issues with English translation
    • Image size not included in the tooltip when hovering a milestone name
    • Rich text custom fields are stripped of their default value when creating an object
    • Problem displaying and refreshing the dashboard page of a milestone
  • Technical:

    • 8845 Some DEBUG log lines appear in INFO
    • When an administrator modifies a user group, the user previous group is still applied on their session if they were logged on when the group change occured

Plugins