From 617578bfde312dbed408453c1b0157a07f289706 Mon Sep 17 00:00:00 2001 From: ByteBlast Date: Sun, 18 Jan 2015 00:47:43 +0000 Subject: [PATCH 1/2] Bumped version --- NextVersion.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NextVersion.txt b/NextVersion.txt index 276cbf9..4a36342 100644 --- a/NextVersion.txt +++ b/NextVersion.txt @@ -1 +1 @@ -2.3.0 +3.0.0 From c332c90de2305d009674b70251987136f8ed83f9 Mon Sep 17 00:00:00 2001 From: ByteBlast Date: Sun, 18 Jan 2015 00:51:27 +0000 Subject: [PATCH 2/2] Documented breaking change --- BREAKING_CHANGES.md | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/BREAKING_CHANGES.md b/BREAKING_CHANGES.md index cbe1a76..ae32784 100644 --- a/BREAKING_CHANGES.md +++ b/BREAKING_CHANGES.md @@ -1,3 +1,28 @@ +# Version 3.0.0 + +## ShouldRedirectTo Method + +It used to be the case that when you invoked `ShouldRedirectTo` where `TController` is the same type as the `Controller` under test like this: + + var sut = new HomeController(); + sut.WithCallTo(c => c.Index()) + .ShouldRedirectTo(c => c.Index()); + + an `ActionResultAssertionException` would be thrown. + +An exception is no longer thrown. + +### Reason + +There is no reason why a test like this one should fail. + +You can read the original problem specification and discussion [here](https://github.com/TestStack/TestStack.FluentMVCTesting/issues/47). + + +### Fix + +If your project has been impacted by this particular breaking change, you might consider reevaluate the correctness of the affected tests. + # Version 2.0.0 ## ShouldRenderFileStream Method