Read-only mirrors. Development, issues and pull requests are on GitHub.

summaryrefslogtreecommitdiffhomepage
path: root/docs
diff options
context:
space:
mode:
authorSam Cunliffe2022-10-12 10:17:50 +0100
committerMartin Hořeňovský2022-10-15 16:59:52 +0200
commitd1394a70649d5a0f8ff42c3a90701a557a9b85fe (patch)
treea6dd96475d3ca7cc116797c2877b76439204c420 /docs
parente94976ec9ccff85e71c568d8c84729a38d071bfc (diff)
downloadcatch3-d1394a70649d5a0f8ff42c3a90701a557a9b85fe.tar.gz
Link to SECTIONS doc at top of test fixtures page.
I came here looking for a way to use a fixture. But what I really wanted was better done in the SECTION macro. Feels like a link right at the top would've made it clearer faster.
Diffstat (limited to 'docs')
-rw-r--r--docs/test-fixtures.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/test-fixtures.md b/docs/test-fixtures.md
index e4747c26..21e4ea31 100644
--- a/docs/test-fixtures.md
+++ b/docs/test-fixtures.md
@@ -3,7 +3,7 @@
## Defining test fixtures
-Although Catch allows you to group tests together as sections within a test case, it can still be convenient, sometimes, to group them using a more traditional test fixture. Catch fully supports this too. You define the test fixture as a simple structure:
+Although Catch allows you to group tests together as [sections within a test case](test-cases-and-sections.md), it can still be convenient, sometimes, to group them using a more traditional test fixture. Catch fully supports this too. You define the test fixture as a simple structure:
```c++
class UniqueTestsFixture {