From bb95dd382ecca3df1148c5317d7af52c561cdb0c Mon Sep 17 00:00:00 2001 From: Jon Rowe Date: Mon, 20 Mar 2023 11:45:16 +0000 Subject: [PATCH] Fix a documentation link --- .../aggregating_failures.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/features/expectation_framework_integration/aggregating_failures.feature b/features/expectation_framework_integration/aggregating_failures.feature index d875b7e4f..107eb6552 100644 --- a/features/expectation_framework_integration/aggregating_failures.feature +++ b/features/expectation_framework_integration/aggregating_failures.feature @@ -1,6 +1,6 @@ Feature: Aggregating Failures - RSpec::Expectations provides [`aggregate_failures`](../../rspec-expectations/docs/aggregating-failures), an API that allows you to group a set of expectations and see all the failures at once, rather than it aborting on the first failure. RSpec::Core improves on this feature in a couple of ways: + RSpec::Expectations provides [`aggregate_failures`](../../rspec-expectations/aggregating-failures), an API that allows you to group a set of expectations and see all the failures at once, rather than it aborting on the first failure. RSpec::Core improves on this feature in a couple of ways: * RSpec::Core provides much better failure output, adding code snippets and backtraces to the sub-failures, just like it does for any normal failure. * RSpec::Core provides [metadata](../metadata/user-defined-metadata) integration for this feature. Each example that is tagged with `:aggregate_failures` will be wrapped in an `aggregate_failures` block. You can also use `config.define_derived_metadata` to apply this to every example automatically.