Table of Contents
Squish Test Center groups test results using Projects, Batches, Reports and Labels.
In Squish Test Center, Projects are meant to help separate test results that are not related, or are part of separate products. Tests for the same product or feature should be uploaded to the same Project (Squish Test Center's analysis features do not work across Project borders, keep that in mind when deciding how to split up your tests by Project).
Batches and Reports are concepts that were developed to help structure and group your test results.
A Batch represents a test execution across one or more test suites and across one or more configurations. If you end up with a single test result file after a test run, e.g. because you execute a single test suite on a single machine, the result file should be uploaded into its own separate Batch. If you end up with multiple test result files after a test run, e.g. because you execute multiple test suites or run your tests on multiple machines and configurations, all result files that belong to the same test run should be uploaded to the same Batch.
When you upload one or more results to a Batch, the results are grouped under a Report.
While a Report can contain test results of one or more test suites it should only contain
test results that were executed on one specific configuration. A Label
can be assigned to a Report to show on which configuration the tests of a
Report have been executed on. If you run your Tests on both Windows
and Linux, you should upload your results to two separate
Reports, by tagging one upload with the Label OS=Windows
and the other upload with the Label OS=Linux.
If there are other attributes that differentiate the configurations your tests run on, like
the version of your AUT or the browser version, you can add a Label for each of them.
You can chose to upload all results of a specific configuration to the same Report, but sometimes its simply more convenient to upload each result by itself and end up with many Reports for one specific configuration. Both setups should work equally well.
If your nightly test runs consisted of 10 test suites executed across two operating systems and three browser versions, all results of the nightly test run should be uploaded to the same Batch. As a Batch name you should pick something that is easy to identify and unique. For nightly test runs including the date makes sense, so you would end up with a Batch name like this Nightly 25.02.2020. Since in our example the nightly test run is executed across 6 different configurations, you should end up with at least 6 Reports, each with a Label for the operating system and another for the browser version.
On the other hand, if you distribute the tests across multiple machines, or decide to upload each suite result individually, you could end up with 60 Reports in the Nightly 25.02.2020 Batch, of which many will share the same sets of Labels.