Roadmap Squash AUTOM /

Roadmap Squash DEVOPS

 

Next release

New Squash AUTOM components released

Status: under development

Release date: 01/31/2021

  • Squash Orchestrator
    Automated test orchestration service capable of receiving an Execution Plan as Code (EPaC) in Json or YAML format describing in a simple but precise way the actions to be performed for the execution of automated tests. The orchestrator then takes care of transcribing the content of the EPaC into commands understandable by the targeted execution environment and transmitting them to it via SSH.
    The Squash orchestrator is made up of a set of micro-services to ensure its basic operation, brought together in a single Docker image.
     

  • Action Provider type micro-services for the Squash orchestrator
    These micro-services aim to provide verbs that can be used within a EPaC in order to simply describe the triggering of specific actions such as the execution of a test of a given technology or the test retrieval.
    The following services are added by this release:

    • Action Provider Robot Framework v1: set of actions linked to Robot Framework (running a test, creating a file of datasets that can be used by a Robot Framework test)

    • Action Provider Cypress v1: set of actions linked to Cypress (running a test)

    • Action Provider JUnit v1: set of actions linked to JUnit (running a test, creating a file of data sets that can be used within a JUnit test)

    • Action Provider SoapUI v1: set of actions linked to SoapUI (running a test)

    • Action Provider Cucumber v1: set of actions linked to Cucumber(running a test)

    • Action Provider Git v1: set of actions linked to Git (cloning of a remote repository)

    • Action Provider Files v1: set of actions related to file management (creation, recovery)
       

  • Squash TM Publisher micro-service for the Squash orchestrator
    Micro-service integrating with the Squash orchestrator to publish to Squash TM information on the results of automated test cases when these have been launched from Squash TM using the Squash AUTOM plugin or via the Generator Squash micro-service TM (available in Squash DEVOPS)
     

  • Result Publisher plugin for Squash TM:
    This Squash TM plugin compatible with version 1.22 allows to process the information received from the Squash TM orchestrator to update the information of a Squash TM automated suite or a Squash TM test plan item.
    This plugin exists in two versions:

    • Community: The status of the ITPI and the associated automated suite is updated according to the result of the automated test. There is no run created for ITPI. Reports are attached as an attachment to the automated suite.

    • Premium: the status of the automated suite associated with the ITPI is updated according to the result of the automated test. An execution is created for the ITPI. The reports are attached as an attachment to the new run.

 

New Squash DEVOPS components released

Status: under development

Release date: 01/31/2021

  • DEVOPS Squash plugin for Jenkins
    Plugin for Jenkins server to facilitate the call to the Squash AUTOM orchestrator within a Jenkins pipeline thanks to the following features:

    • Declaration of Squash orchestrators in a dedicated Jenkins configuration space.

    • Dedicated pipeline step for sending an execution plan to a Squash orchestrator.

  • Micro-service Generator Squash TM
    Micro-service integrating with the Squash orchestrator allowing within a EPaC to request the execution of a set of predefined tests in a Squash TM instance.
    This micro-service exists in two versions:

    • Premium: allows you to target an iteration or a Squash TM test suite and filter it according to the value of a custom field of type tag on the test cases

    • Community: allows you to target an iteration or a Squash TM test suite

  • Test Plan Retriever plugin for Squash TM
    This Squash TM plugin works in conjunction with the Generator Squash TM micro-service and is used to transmit the list of tests requested by the latter.
    This plugin exists in two versions:

    • Community: only the custom fields of the test case and the ITPI dataset are transmitted to the Squash orchestrator for use within the automated script.

    • Premium: In addition to the previously mentioned fields, the custom fields of the test suite, the iteration and the campaign linked to the ITPI concerned are transmitted to the Squash orchestrator for use within the automated script.

 

New Squash AUTOM components released

Status: future development

Release date: 02/26/2021

  • Squash AUTOM plugin for triggering Squash TM automated tests:
    This Squash TM plugin compatible with version 1.22 allows you to declare Squash Orchestrator type automation servers within Squash TM and to trigger the execution of automated tests by a Squash orchestrator from Squash TM.
    This plugin exists in two versions:

    • Community: only the custom fields of the test case and the ITPI dataset are transmitted to the Squash orchestrator for use within the automated script.

    • Premium: In addition to the previously mentioned fields, the custom fields of the test suite, the iteration and the campaign linked to the ITPI concerned are sent to the Squash orchestrator for use within the automated script
       

  • Action Provider type micro-services for the Squash orchestrator
    These micro-services aim to provide verbs that can be used within a EPaC in order to simply describe the triggering of specific actions such as the execution of a test of a given technology or the test retrieval.
    The following services are added by this release:

    • Action Provider UFT v1: set of actions related to UFT (running a test, creating a file of data sets that can be used within a UFT test)

    • Action Provider Agilitest v1: set of actions linked to Agilitest (execution of a test)
       

  • Micro-service Allure / Squash TM Publisher for the Squash orchestrator
    Micro-service integrating with the Squash orchestrator to generate an Allure report summarizing the results of all the tests of a Squash TM automated suite and send it to Squash TM.

 

New Squash AUTOM components released

Status: future development

Release date: 03/31/2021

  • Action Provider type micro-services for the Squash orchestrator
    These micro-services aim to provide verbs that can be used within a EPaC in order to simply describe the triggering of specific actions such as the execution of a test of a given technology or the test retrieval.
    The following services are added by this release:​

    • Action Provider Ranorex v1: set of actions related to Ranorex (running a test)

 

Latest release

Version 1.22 Squash

Status: released version (latest stable version)
Release date: 12/31/2020

Release note 1.22.0

Release note 1.22.1

  • Management of test cases in BDD format and library of actions
    This new test case format is based on Gherkin syntax and allows you to write your BDD scenarios using a simple and intuitive interface.
    The actions contained in the test steps can be varied and reused in test cases from different projects.
    During their transmission to the automation engineer, the scripts associated with the BDD test cases are converted into a format corresponding to the target implementation technology (Cucumber or Robot Framework). The choice of technology has no impact for the user when writing test cases.

  • Action library plugin
    This Squash TM plugin compatible with version 1.22 allows you to manage the actions contained in the test cases in BDD format in a new space. From this space, it is in particular possible to consult the test cases using an action and the information relating to its implementation.
    This plugin also facilitates the writing of test cases in BDD format by offering the user by auto-completion the actions already present in the library and corresponding to his entry.

  • Consultation of automated suites
    In terms of iterations and test suites, a new tab allows you to view the history of automated suites (set of automated tests launched at the same time).
    For each automated suite, the user can consult the overall execution status, the details of the tests executed and access the execution report for all the tests.

 

Release history

(versions of Squash TF)

12/24/2019 release

Components:

 

Status: released versions (stable versions)

  • Squash TF Execution Server 2.3.0:

    • Jenkins version upgrade to version 2.190.1. Jenkins plugins have been upgraded as well.

    • New project template for Robot Framework Runner.

    • Bug fixes.
       

  • Robot Framework Runner 1.0.0:

    • Robot Framework Runner enables python test execution within our set of tools.
       

  • Squash TF Java Junit Runner 1.2.0:

    • TestList.json parameters can be retrieved for java JUnit tests.​

  • Squash Keyword Framework 1.14.0:

  • Squash TF IntelliJ plugin 1.0.0:

    • ​The autocomplete feature with macros have been enhanced.

    • Bug fixes.

  • squash-tf-services Python library 1.0.0:

    • Squash TM parameters are accessible within a Robot Framework test, during execution, thanks to a Python library.

    • Libraries are available on PyPI (Python Package Index)

09/30/2019 release

 

Components:


Status: released versions (obsolete)

  • Squash TF Execution Server 2.2.0:

  • Squash Keyword Framework 1.13.0:

    • Metadata functionality has been added. It enables auto link between a SKF script and a Squash TM test case.

    • SoapUI library included in the corresponding SKF plugin has been updated to 5.5.0

    • Selenium library included in the corresponding SKF plugin has been updated to 3.141.59

      • Selenium plugin uses now Selenium 3 (still compatible with Selenium 2)

      • Selenium Plugin Legacy has been created. This plugin is compatible with Selenium 1 scripts

    • Documentation migration: https://squash-tf.readthedocs.io/projects/skf/en/doc-stable/

  • Runner Squash TF Cucumber Java 1.2.0:

    • tf.feature and ta .feature parameters can use now a relative path to project root

    • Therefore, systematic use of absolute path is no longer necessary

  • Runner Squash TF Java Junit 1.0.3:

    • Metadata functionality has been added. It enables auto link between a Junit test and a Squash TM test case.

  • Plugin Squash TF IntelliJ IDEA 0.0.2:

    • The autocomplete feature with macros have been enhanced

    • New syntactic rules has been added to syntax check feature

06/06/2019 release

 

Components:

  • Squash TF Execution Server 2.1.1 ( release note )

  • Squash Keyword Framework 1.12.0 ( release note )

  • Runner Squash TF Cucumber Java 1.1.0 ( release note )

  • Runner Squash TF Java Junit 1.0.3 ( release note )

  • Squash TF IntelliJ IDEA plugin 0.0.1


Status: released versions (obsolete)

  • Squash TF Execution Server 2.1.1:

    • Docker images have been created for the following execution agents:

      • Execution agent​

      • Execution agent + X11 + Firefox + geckodriver

      • Execution agent + X11 + Chrome + chromedriver

    • Jenkins version upgrade to version 2.164.1 (lts). Jenkins plugins have been upgraded as well.

    • Macro libraries.

    • Bug fixes.

  • Squash Keyword Framework 1.12.0:

    • A JUnit connector has been added to execute JUnit Jupiter (JUnit 5) or JUnit Vintage (JUnit 4) tests.

    • Junit 5 “resources” and “engine components” have been added

    • Bug fixes.

  • Squash TF Cucumber Java Runner 1.1.0:

    • There is now a new report dedicated to keyword execution.

    • Bug fixes.
       

  • Squash TF Java Junit Runner 1.0.3:

    • Bug fixes.
       

  • Squash TF IntelliJ IDEA plugin 0.0.1:

    • A new studio, based on IntelliJ IDEA, provides support for Squash Keyword Framework (previously Squash TA Framework) automated testing projects.

    • This plugin provides the following new features:

      • Syntax coloration for .ta or .macro files.

      • Syntax check for .ta or .macro files.

      • Autocomplete feature for .ta or .macro files. (macros developed by a user within a project are also suggested)

01/31/2019 release

 

Components:

Status: released versions (obsolete)

  • Runners :

Squash TF introduces the concept of Runner. Runners aim to:

  • Facilitate the integration of our set of tools in a pre-existing test asset.

  • Facilitate the adoption of our set of tools.

  • Enable a Squash TM execution of your pre-existing test asset, even if it wasn’t written with Squash Keyword Framework.
     

  • Squash TF Java Junit Runner 1.0.0: 

    • It enables the execution of your JUnit5/JUnit4 tests via our set of tools. 

    • This runner goes with a project template (archetype) to help you start a project.
       

  • Squash TF Cucumber Java Runner 1.0.0:

    • Gherkin / Cucumber - Java tests, that have been automated via our set of tools, can be executed thanks to Squash TF Cucumber Java Runner. It is particularly suited to Squash TM Gherkin test cases.

    • This runner goes with a project template (archetype) to help you start a project.

  • Squash TF Execution Server 2.0.0:

Previously Squash TA Server 1.X.

This version has two goals:

  • Make the installation easier thanks to:

    • a docker image for the execution server

    • an execution agent installer

  • Increase our execution capacity, notably with project templates for both our Runners

 

  • Squash Keyword Framework 1.11.0 (ex Squash TA):​

XML-functions has been created: this Plugin allows for XSL transformations on XML resources.

MEN-XML Plugin has been created: integration of MEN-XML plugin, a MEN Orléans contribution

  • Common component Plugin

    • Encoding specification is used for parameters substitution

    • Enhancement of JavaCodeBundle compiler so that it would accept input unique files.

    • Configurable filter to exclude binary files in parameters substitution macro has been added

    • Dump to local filesystem command has been added

    • Exploitation of CSV resources: XML transformation

  • DB Plugin

    • Encoding specification in DB request macro has been added

    • Configurable SQL block delimiter has been added to SQL script execution macro

    • Additional dataset validation rules has been added to converters

    • DB count macro has been added

    • Functional failure context of DB request has been improved: expected and actual data are now attached to the failure report of a comparison assertion.

    • « Database not.contains » assertion has been added

  • SoapUI Plugin

    • SoapUI logs are now displayed when executing a SoapUI script with SoapUI Plugin

  • FTP Plugin

    • FTP plugin’s commands can now target a folder

  • SFTP Plugi

    • SFTP plugin’s commands can now target a folder