You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,15 +1,15 @@
1
-
Fluent MVC Testing
1
+
TestStack.FluentMVCTesting
2
2
====================================
3
3
4
-
This library provides a fluent interface for creating terse and expressive tests against ASP.NET MVC controllers.
4
+
This library provides a fluent interface for creating terse and expressive tests against ASP.NET MVC controllers. This library is part of [TestStack](http://teststack.github.com/).
5
5
6
6
This library is testing framework agnostic, so you can combine it with the testing library of your choice (e.g. NUnit, xUnit, etc.).
7
7
8
8
The library is compatible with the AAA testing methodology, although it combines the Act and Assert parts together (but you can also have other assertions after the Fluent assertion). See the code examples below for more information.
9
9
10
-
The motivation behind this library is to provide a way to test MVC actions quickly, tersely and maintainably. Most examples I find on MVC controller testing are incredibly verbose, repetitive and time-consuming to write and maintain. Given how quickly you can write controller actions and how simple they are (assuming you are following best practices and keeping them lean) the time to test them generally isn't worth it given you can glance at most of your controller actions and know they are right or wrong instantly. This library aims to make the time to implement the tests inconsequential and then the value your tests are providing is worth it. The other problem that I've noticed with most examples of controller testing is that there are a lot of magic strings being used to test view and action names; this library also aims to (where possible) utilise the type system to resolve a lot of those magic strings, thus ensuring your tests are more maintainable and require less re-work when you perform major refactoring of your code.
10
+
The motivation behind this library is to provide a way to test MVC actions quickly, tersely and maintainably. Most examples we find on MVC controller testing are incredibly verbose, repetitive and time-consuming to write and maintain. Given how quickly you can write controller actions and how simple they are (assuming you are following best practices and keeping them lean) the time to test them generally isn't worth it given you can glance at most of your controller actions and know they are right or wrong instantly. This library aims to make the time to implement the tests inconsequential and then the value your tests are providing is worth it. The other problem that we've noticed with most examples of controller testing is that there are a lot of magic strings being used to test view and action names; this library also aims to (where possible) utilise the type system to resolve a lot of those magic strings, thus ensuring your tests are more maintainable and require less re-work when you perform major refactoring of your code.
11
11
12
-
I came up with this library after using the [MVCContrib.TestHelper](http://mvccontrib.codeplex.com/wikipage?title=TestHelper) library for quite a while, but becoming frustrated with it; the library was initially created during an [experiment I conducted](http://robdmoore.id.au/blog/2011/03/14/terse-controller-testing-with-asp-net-mvc/) to try and create terse controller tests. I (and my team) have been using the library for over a year on a number of projects for the company that I work for.
12
+
This library was inspired by the [MVCContrib.TestHelper](http://mvccontrib.codeplex.com/wikipage?title=TestHelper) library.
13
13
14
14
Installation
15
15
------------
@@ -18,11 +18,11 @@ You can install this library using NuGet into your Test Library; it will automat
18
18
19
19
If you are using ASP.NET MVC 4 then:
20
20
21
-
Install-Package FluentMVCTesting
21
+
Install-Package TestStack.FluentMVCTesting
22
22
23
23
If you are using ASP.NET MVC 3 then:
24
24
25
-
Install-Package FluentMVCTesting.Mvc3
25
+
Install-Package TestStack.FluentMVCTesting.Mvc3
26
26
27
27
Known Issues
28
28
------------
@@ -162,7 +162,7 @@ If you are redirecting to an action in another controller, then there are two sy
Unfortunately, I couldn't think of a way to get rid of the magic strings here so where possible use the default ones above.
165
+
Unfortunately, we couldn't think of a way to get rid of the magic strings here so where possible use the default ones above.
166
166
167
167
See below for model testing.
168
168
@@ -264,4 +264,4 @@ You can chain the error property checks after any of these checks (you can only
264
264
Any questions, comments or additions?
265
265
--------------------------
266
266
267
-
Leave an issue on the GitHub project or a comment on my [blog](http://robdmoore.id.au/blog/2012/05/29/fluentmvctesting-fluent-terse-and-maintainable-asp-net-mvc-controller-testing/). Also, feel free to send through a pull request.
267
+
Leave an issue on the [GitHub project](https://github.com/TestStack/TestStack.FluentMVCTesting/issues) or send a [pull request](https://github.com/TestStack/TestStack.FluentMVCTesting/pulls).
0 commit comments