You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: jekyll/_cci2/rerun-failed-tests.adoc
+7-3Lines changed: 7 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -96,7 +96,7 @@ NOTE: You can specify the timing type similar to `circleci tests split --split-b
96
96
97
97
After updating your configuration, run the job that runs tests again and make sure that the same number of tests are being executed as before the config.yml change.
98
98
99
-
Then, the next time you encounter a test failure on that job, click the "Rerun failed tests" button. If the `--verbose` setting is enabled, you should see output similar to the following the next time you click btn:[Rerun failed tests] with this job on CircleCI:
99
+
Then, the next time you encounter a test failure on that job, select btn:[Rerun failed tests]. If the `--verbose` setting is enabled, you should see output similar to the following the next time you select btn:[Rerun failed tests] with this job on CircleCI:
100
100
101
101
```sh
102
102
Installing circleci-tests-plugin-cli plugin.
@@ -633,7 +633,7 @@ On a rerun, if the parallel run is running tests, `no_files_here` will be popula
633
633
[#approval-jobs]
634
634
=== Approval jobs
635
635
636
-
If your workflow has an approval job, and a failed job containing failed tests that you wish to rerun, you will not be able to click btn:[Rerun failed tests] until the workflow has terminated. This means that you must cancel the approval job before you can click btn:[Rerun failed tests].
636
+
If your workflow has an approval job, and a failed job containing failed tests that you wish to rerun, you will not be able to select btn:[Rerun failed tests] until the workflow has terminated. This means that you must cancel the approval job before you can select btn:[Rerun failed tests].
**Answer:** In order to use `timings-type=testname`, the test runner/framework must be able to take in as *input* a list of *test names* (as opposed to *classnames* or *file names*). Most test frameworks (including RSpec) do not accept as input a list of test names. If the test framework accepts as input a list of test names, pipe the test names into `circleci tests run` instead of piping in test file/class names via `circleci tests glob`. This will enable CircleCI to find the historical test data for individual test names and split the test names into logical groups.
0 commit comments