Cantata Team Reporting is an add-on product for the Cantata unit and integration testing tool. For more information about the Cantata base product please see the Cantata page.
Where organisations have large engineering teams, or need to co-ordinate multiple test runs, Cantata Team Reporting adds major benefits to the Cantata desktop product; enabling teams to work more effectively. Test results are centralised using a client-server architecture and are then accessible though a web interface or via REST API.
Cantata accelerates safety standards compliance by automating:
Team Reporting stores test data pushed from Cantata client desktops or build servers onto a centralised Cantata server. Server administration pages of the web interface set up a controlled hierarchy of containers to suit the needs of business units, products and their variants.
The Cantata Eclipse® client interface is used to select the container to which test data (test scripts, source code under test, functional and coverage results) are to be pushed. Within a given container, test data are grouped into coherent Test Data Sets. Environment variables, Java or Cantata properties can be used to control how and when test data sets are created for continuous integration builds, version control revision etc. Test data upload to the Cantata server is either automatic on test execution or via the GUI at user instigation. The test data is accessible over a web interface and REST API.
By aggregating the test results over multiple tests, managers can easily see the complete picture of Cantata test progress across their code base build by build. Aggregation of overall functional tests and achieved levels code coverage over multiple work-spaces is only practical with this centralised reporting approach.
Cantata Team Reporting provides a web interface for distributed teams to share tests assets (test scripts, source files, test reports etc.). Test status and progress can be monitored with filters, ordering and history.
Cantata Team Reporting Global Summary View (for multiple containers distributed on a WAN or LAN)
Cantata project properties with additional data
Where organisations re-use source code across multiple system or product variants, they can test that code with the same Cantata tests in each of these different cases. Controlling such multiple test execution scenarios is made easy with Team Reporting. The additional data stored about each test execution allows for differentiation between variant scenarios. This additional data is highly flexible and can be specified as any of:
environment variables (used to distinguish variants at build time)
Cantata properties (e.g. tool version, target configuration)
Java properties (e.g. user, operating system)
user defined properties (e.g. specific project options)
Where code variants are used, it can be particularly useful to manage and analyse results per:
continuous integration build number (e.g. Jenkins build ID)
Test Data sets can themselves also be named or configured to automatically reference build tags from continuous integration tools for further differentiation.
Where teams of engineers or managers want to collaborate on development or review of Cantata tests, replicating these tests over multiple desktop environments or target configurations brings replication challenges. The centralised availability of Cantata tests in Team Reporting avoids the need to replicate tests over multiple work-spaces from different desktops. The web interface allows distributed teams to collaborate easily and managers to monitor progress through sharing Cantata test assets (test scripts, source code, results files etc.). Summaries drill down to individual functional and code coverage test results, test scripts and source code in the same style as the Cantata desktop Eclipse® GUI.
Cantata Team Reporting Datasheet
Cantata Feature Brief - Team Reporting
Cantata Technical Note - Integration with Jenkins