Highlights of Squore 2021

More Modern and Elegant Look & Feel

Optimized spacing between elements to improve readability.

Modern graphical elements for a better understandability (e.g., use of breakdown bars instead of pies).

Introduction of a unified detailed view as a side bar

  • Many popups replaced by the detailed view
  • Detailed view available for Artefacts, Findings, Action Items and Forms edition
  • All data edition and comments are now grouped in the detailed view
さらに表示

Squore Project Management: Branches are Now Supported

​To adapt to industrial projects reality, it is now possible to branch a Squore project.

​Relaxation can be reported from one branch to another using one of the following mode:

  • All branches
  • Only selected branches
  • No propagation

​Same propagation principle available for metric/status override.

さらに表示

New Finding View Design for Clearer Visualization

The finding view (same for action items view) has been fully redesigned for a better understandability

  • New summary replacing pies
  • New filter panel on the left

    • For direct access to multiple filters
    • To avoid multiple clicks

​Finding view can be the starting point for the detailed view context. Different review modes are available, based on where the user clicks:

​The review mode expands into a fully detailed view:

さらに表示

New Squore Configuration Capabilities Available

  • Computed rules : Findings can now be generated from the (Squore) model

    • This can for instance be used for generation of findings on Ticket artifacts
    • Once defined those findings are shown the same way than any finding imported from external tool

  • Findings on rules absent from the ruleset are now also imported
  • Stored with a special flag and can be viewed in the findings view

  • New possibility to hide specific dashboards / highlights / reports / exports on a condition
  • Possibility to use computations in chart description

    • Values in chart description are always up to date

  • Same possibility to use computations in mail notification templates (plain text or HTML)
さらに表示

Squore delivered with a Groovy toolkit for customization

Main advantages of the new Groovy toolkit:

  • Well documented toolkit (JavaDoc like documentation) for writing

    • New data providers / Repository connectors
    • New external tools (Launched by the Squore Tools menu) with preset token for using the API
    • New export

  • Same language than Jenkins customization language
  • Less dependencies to Perl modules

Squore 21.0 comes with:

  • 26 Data providers written in groovy
  • 1 Repository connector written in groovy

This provides good samples for developing new Squore Data Providers or Repository connectors

さらに表示

New Squore Agent for better integration in CI

  • New Squore Agent downloadable from Squore server

    • Squore Agent is in charge of downloading and updating the CLI and its environment
    • No specific installation, everything is automatic
    • Easy integration in Continuous Integration process

Example of simple pipeline:

Example of pipeline with multi-level Quality Gates (Process, Product, Reliability):

さらに表示

Squore for CANoe (vTESTstudio, DIVA): Turn your test results into relevant KPI

Highlights of the Solution

Squore for Tests & Requirements could be presented as a dynamic report for CANoe and vTESTstudio data.

​The solution mainly contributes to track the project progression by reviewing/overloading test verdicts and assessing the impact on their associated requirements.

​Data is imported from CANoe, vTESTstudio and vTraceItem (ie, a generic data import based on the Vector "vti-tso" format). 

Important KPI:

  • Requirement Test Coverage (Requirement is covered when all associated tests are passed)
  • Test Effectiveness (ratio of passed tests)
  • Variant Matrix (Synthetic view of test effectiveness per variant in the project)
  • Review progression
  • Overloading tracking
さらに表示

Squore for VectorCAST improved: Ensure Tests guideline compliance

Assess quality during tests and requirements development

  • By creating quality rules to respect.

    • Rules example:

      • Check if test has an expected result
      • Evaluate the test name
      • Look for requirement linkage

  • By computing compliance ratio
さらに表示