Skip to content

Commit 5206640

Browse files
yaningoYann Domingorosieyohannan
authored
Adding info about downloading previous test results (#9028)
* Adding information about timing data retrieval when splitting tests by timing * Add job type to config reference (#9021) * att job type to config ref * Update jekyll/_cci2/configuration-reference.adoc * Removing word that Vale flags as weasel --------- Co-authored-by: Yann Domingo <[email protected]> Co-authored-by: Rosie Yohannan <[email protected]>
1 parent de9feeb commit 5206640

File tree

2 files changed

+7
-0
lines changed

2 files changed

+7
-0
lines changed

jekyll/_cci2/test-splitting-tutorial.adoc

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -333,6 +333,13 @@ Requested weighting by historical based timing, but they are not present. Fallin
333333
+
334334
CircleCI defaults to splitting tests by name. As this is the first time you are storing test data from the pipeline, CircleCI does not yet have timing data to work with.
335335
// Check if this applies to GitLab
336+
337+
On subsequent runs, you'll see an additional step labelled **Downloading previous test results**:
338+
+
339+
image::downloading-previous-test-results-step.png[Downloading previous test results step]
340+
+
341+
The presence of this step confirms that, during this run, the test results stored by a previous run (with the `store_test_results` step) were successfully retrieved. Provided that the data is xref:parallelism-faster-jobs/#junit-xml-reports[properly formatted], the test suite will be split as evenly as possible over the specified number of test environments.
342+
336343
. Open the **Timing** tab in the job. This tab provides a visualization of how each parallel run did relative to each other.
337344
+
338345
image::test-splitting-timing-tab.png[Parallel runs visualization in Timings tab]
60.1 KB
Loading

0 commit comments

Comments
 (0)