From 1282e842febf418ca27df13fa4b32f7e5021b470 Mon Sep 17 00:00:00 2001 From: Rick Waldron Date: Tue, 17 Oct 2017 16:45:37 -0400 Subject: [PATCH] CONTRIBUTING.md: Link #handling-errors-and-negative-test-cases (#1295) --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 55e428abd9..70b5a1798b 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -105,7 +105,7 @@ This means the test is expected to throw an error of the given type. If no erro - **type**- If an error is thrown, it is implicitly converted to a string. In order for the test to pass, this value must match the name of the error constructor. - **phase** - Negative tests whose **phase** value is "early" must produce the specified error prior to executing code. The value "runtime" dictates that the error is expected to be produced as a result of executing the test code. -For best practices on how to use the negative tag please see Handling Errors and Negative Test Cases, below. +For best practices on how to use the negative tag please see [Handling Errors and Negative Test Cases](#handling-errors-and-negative-test-cases), below. For example: