Select import strategy

In most cases you should not set an import strategy. In the normal workflow you change a test and at the same time get a new version of the application under test (AUT), so every upload represents a distinct AUT version and you retest everything. Each upload is then kept as its own independent execution.

An import strategy is only useful when this assumption does not hold, for example when tests are re-run against the same application version, when the revision of the tests is not strictly tied to the AUT version, or when only the failing tests are regularly re-executed. In these cases an import strategy lets Test Center identify previously uploaded results and overwrite or annotate them, instead of adding the new results as separate executions.

Setting an import strategy

The import strategy is set per upload as the importStrategy field of the report request. For the full list of upload fields and their semantics, see Report Request Body.

It identifies previously uploaded reports based on tests executed and labels assigned, and then removes or annotates previous results. It can be specified as overwrite:testcase, where testcase can be chosen based on whether you want to overwrite individual test cases, test suites or scenarios. Alternatively it can be specified as annotate-failures:<annotation-name>, so that failures from previous results will be annotated with the chosen annotation type.

For upload mechanisms that do not expose a dedicated importStrategy parameter, the import strategy can always also be set by providing the special label .importStrategy, for example .importStrategy=overwrite:testcase.