From 6f65aebe8a01f916ea755b887e1487693cc26af9 Mon Sep 17 00:00:00 2001 From: GiuseppePiscopo Date: Mon, 6 Feb 2017 12:52:14 +0100 Subject: [PATCH] chore(index): add Shouldly, fix couple typos --- index.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/index.md b/index.md index 32901aa9..251751e4 100644 --- a/index.md +++ b/index.md @@ -120,8 +120,9 @@ Lets take a look at some features of NSpec.
NSpec has some simple assertions, but you should really just use -[FluentAssertions](http://www.fluentassertions.com/). You can build -your own assertions by using extention +[FluentAssertions](http://www.fluentassertions.com/), or +[Shouldly](https://github.com/shouldly/shouldly), or another assertion +framework. You can build your own assertions by using extension methods. For example: @@ -171,7 +172,7 @@ context will execute `act` before assertions are run. ### Inheritance ###
-Being able to nest tests is awesome. But you'll can always use +Being able to nest tests is awesome. But you can always use inheritance to "flatten" tests if needed. @@ -187,7 +188,7 @@ you'd write a `before`, `act`, and `it/specify` at the class level. ### Debugger Support ###
-If you want to hook into the debugger quickly. Just place the +If you want to hook into the debugger quickly, just place the following line inside of your tests. When you run `NSpecRunner.exe`, the debugger will pop right up: @@ -203,7 +204,7 @@ Nuget. So you can use TDD.NET/ReSharper to run your tests. Or you can do something even fancier, and build your own console app! Instead of creating a Class Library for the test project, -create a Console Project. Add the following code in `Program.cs`: +create a Console Application. Add the following code in `Program.cs`: