From e96e840ede2a7400f3acc73ab819ff91de068a1d Mon Sep 17 00:00:00 2001 From: Jonas Baumann Date: Wed, 16 Jul 2014 12:00:58 +0200 Subject: link minitest assertions documentation. --- guides/source/testing.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) (limited to 'guides/source/testing.md') diff --git a/guides/source/testing.md b/guides/source/testing.md index e780ad2c89..b2da25b19f 100644 --- a/guides/source/testing.md +++ b/guides/source/testing.md @@ -364,8 +364,13 @@ Ideally, you would like to include a test for everything which could possibly br By now you've caught a glimpse of some of the assertions that are available. Assertions are the worker bees of testing. They are the ones that actually perform the checks to ensure that things are going as planned. -There are a bunch of different types of assertions you can use. -Here's an extract of the assertions you can use with `minitest`, the default testing library used by Rails. The `[msg]` parameter is an optional string message you can specify to make your test failure messages clearer. It's not required. +There are a bunch of different types of assertions you can use. Here's an +extract of the +[assertions](http://docs.seattlerb.org/minitest/Minitest/Assertions.html) you +can use with [minitest](https://github.com/seattlerb/minitest), the default +testing library used by Rails. The `[msg]` parameter is an optional string +message you can specify to make your test failure messages clearer. It's not +required. | Assertion | Purpose | | ---------------------------------------------------------------- | ------- | -- cgit v1.2.3