From 3d9fd3dd7ad35763fa35df74c52f85ba32355e6c Mon Sep 17 00:00:00 2001
From: Jaime Perez Crespo <jaime.perez@uninett.no>
Date: Fri, 10 Jun 2016 15:31:14 +0200
Subject: [PATCH] Add a link in CONTRIBUTE pointing to TESTING.

---
 CONTRIBUTE.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTE.md b/CONTRIBUTE.md
index 679aa6ff3..b6eecdc24 100644
--- a/CONTRIBUTE.md
+++ b/CONTRIBUTE.md
@@ -63,7 +63,7 @@ exceptions thrown.
 deploy, and therefore we try to avoid it.
 * Add **unit tests** to verify that your code not only works but also keeps working over time. When adding tests, keep
 the same directory structure used for regular classes. Try to cover **all your code** with tests. The bigger the test
-coverage, the more reliable and better our library is.
+coverage, the more reliable and better our library is. Read our [guidelines](TESTING.md) to learn more about tests.
 * Add proper **documentation** explaining your how to use your new feature or how your code changes things.
 * Submit your code as a **pull request** in github, from a branch with a descriptive name in your own fork of the
 repository. Add a meaningful, short title, and explain in detail what you did and why in the description of the *PR*.
-- 
GitLab