From e33f87ac0fabaab468ce4b457996cc0f1b1bb648 Mon Sep 17 00:00:00 2001 From: GitLab Bot Date: Tue, 21 Apr 2020 15:21:10 +0000 Subject: Add latest changes from gitlab-org/gitlab@master --- doc/development/testing_guide/flaky_tests.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'doc/development/testing_guide/flaky_tests.md') diff --git a/doc/development/testing_guide/flaky_tests.md b/doc/development/testing_guide/flaky_tests.md index 1e53e92fad5..6c1b06ce59a 100644 --- a/doc/development/testing_guide/flaky_tests.md +++ b/doc/development/testing_guide/flaky_tests.md @@ -40,7 +40,7 @@ Quarantined tests are run on the CI in dedicated jobs that are allowed to fail: ## Automatic retries and flaky tests detection -On our CI, we use [rspec-retry](https://github.com/NoRedInk/rspec-retry) to automatically retry a failing example a few +On our CI, we use [RSpec::Retry](https://github.com/NoRedInk/rspec-retry) to automatically retry a failing example a few times (see [`spec/spec_helper.rb`](https://gitlab.com/gitlab-org/gitlab/blob/master/spec/spec_helper.rb) for the precise retries count). We also use a home-made `RspecFlaky::Listener` listener which records flaky -- cgit v1.2.1