Allow users to have shorter flaky report
The rerun command for the flaky tests can be pretty big. This becomes a bigger problem when there are more flaky tests appearing. We allow users to skip the rerun command from the summry report by setting the env variable `RSPECQ_REPORTER_RERUN_COMMAND_SKIP`. The location and worker are still repoted. The sentry payload remains the same.
This commit is contained in:
parent
ff395e1f51
commit
2edcc280e5
|
@ -4,7 +4,10 @@ Breaking changes are prefixed with a "[BREAKING]" label.
|
|||
|
||||
## master (unreleased)
|
||||
|
||||
## 0.7.0 (2021-04-1)
|
||||
- New env variable RSPECQ_REPORTER_RERUN_COMMAND_SKIP. When set, the reporter
|
||||
does not include the flaky test's rerun command.
|
||||
|
||||
## 0.7.0 (2021-04-01)
|
||||
|
||||
- New cli parameter `reproduction`.
|
||||
When passed, primary worker publishes the queue in the same order as passed
|
||||
|
|
|
@ -103,6 +103,7 @@ $ RSPECQ_BUILD=123 RSPECQ_WORKDER=foo1 rspecq spec/
|
|||
| `RSPECQ_QUEUE_WAIT_TIMEOUT` | Queue wait timeout |
|
||||
| `RSPECQ_REDIS_URL` | Redis URL |
|
||||
| `RSPECQ_FAIL_FAST` | Fail fast |
|
||||
| `RSPECQ_REPORTER_RERUN_COMMAND_SKIP` | Do not report flaky test's rerun command |
|
||||
|
||||
### Sentry integration
|
||||
|
||||
|
|
|
@ -113,6 +113,8 @@ module RSpecQ
|
|||
RSpec.configuration.pending_color
|
||||
)
|
||||
|
||||
next if ENV["RSPECQ_REPORTER_RERUN_COMMAND_SKIP"]
|
||||
|
||||
summary << "#{@queue.job_rerun_command(j)}\n\n\n"
|
||||
end
|
||||
end
|
||||
|
|
Loading…
Reference in New Issue