-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re-run failures only #43
Comments
@gap777 I use I expect that passing the extra options to RSpec will be enough to support this feature (#14 (comment)). |
I work with @gap777. I realized that
We already use a shell script to invoke
So for now, we can at least run (non-parallel) |
@douglasshuang Thanks to your feedback! Please note that combining multiple # Concatenate multiple files with the same header
# https://unix.stackexchange.com/a/170692/33308
$ (head -2 spec/examples1.txt && tail -n +3 -q spec/examples?*.txt) > spec/examples.txt
# Checking it worked
$ wc -l spec/examples*.txt
73015 spec/examples.txt
46467 spec/examples1.txt
26550 spec/examples2.txt
146032 total
# Header is present only once
$ grep example_id spec/examples*.txt
spec/examples.txt:example_id | status | run_time |
spec/examples1.txt:example_id | status | run_time |
spec/examples2.txt:example_id | status | run_time | |
@ilyazub Thank you very much for the refinement! |
@douglasshuang Hey, what was your final solution to run the failed specs in nonparallel? I would like to talk to you about your parallel process suit. We can do it via email, discord, or whatever you find best Really appreciate, thanks |
@santigolucass Hi, here is the complete solution: First, we configure RSpec to use a different status persistence file per test runner.
This produces files named as follows when running
Then, after we run
Since
|
Is it possible to re-run the tests limited to those that failed on the last execution?
The text was updated successfully, but these errors were encountered: