|
1 | 1 | 
|
2 | 2 |
|
| 3 | +[](https://discord.gg/H2G9yWeuRZ) |
3 | 4 | [](https://codeclimate.com/github/avmnu-sng/rspec-tracer/maintainability)
|
4 | 5 | [](https://codeclimate.com/github/avmnu-sng/rspec-tracer/test_coverage)
|
5 | 6 | [](https://badge.fury.io/rb/rspec-tracer)
|
@@ -35,6 +36,7 @@ installed.
|
35 | 36 | * [Demo](#demo)
|
36 | 37 | * [Getting Started](#getting-started)
|
37 | 38 | * [Working with JRuby](#working-with-jruby)
|
| 39 | + * [Working with Parallel Tests](#working-with-parallel-tests) |
38 | 40 | * [Configuring CI Caching](#configuring-ci-caching)
|
39 | 41 | * [Advanced Configuration](#advanced-configuration)
|
40 | 42 | * [Filters](#filters)
|
@@ -146,6 +148,18 @@ debug.fullTrace=true
|
146 | 148 | objectspace.enabled=true
|
147 | 149 | ```
|
148 | 150 |
|
| 151 | +### Working with Parallel Tests |
| 152 | + |
| 153 | +The Rspec tracer, by default, supports working with [parallel_tests](https://github.com/grosser/parallel_tests/) |
| 154 | +gem. It maintains a lock file `/tmp/parallel_tests.lock` to identify the last |
| 155 | +running process. Usually, you are not required to do anything special unless you |
| 156 | +interrupt the execution in between and the process did not complete correctly. |
| 157 | +In such a case, you must delete the lock file before the next run. |
| 158 | + |
| 159 | +```sh |
| 160 | +rm -f /tmp/parallel_tests.lock && bundle exec parallel_rspec |
| 161 | +``` |
| 162 | + |
149 | 163 | ## Configuring CI Caching
|
150 | 164 |
|
151 | 165 | To enable RSpec Tracer to share cache between different builds on CI, update the
|
|
0 commit comments