o_19mgorv9t13a3ko71fev19l81mqa.pdf

TestRouteMatch and TestRouteFail contain calls to the Assert method, which throws an exception if the
assertion fails. Because C# exceptions are propagated up the call stack, I can create simple test methods that test a set of
URLs and get the test behavior I require. Here is a test method that tests the route I defined in Listing 15-8:
...
[TestMethod]
public void TestIncomingRoutes() {
// check for the URL that is hoped for
TestRouteMatch("∼/Admin/Index", "Admin", "Index");
// check that the values are being obtained from the segments
TestRouteMatch("∼/One/Two", "One", "Two");
// ensure that too many or too few segments fails to match
TestRouteFail("∼/Admin/Index/Segment");
TestRouteFail("∼/Admin");
}
...
This test uses the TestRouteMatch method to check the URL I am expecting and also checks a URL in the same
format to make sure that the controller and action values are being obtained properly using the URL segments. I
use the TestRouteFail method to make sure that the application won’t accept URLs that have a different number of
segments. When testing, I must prefix the URL with the tilde (∼) character, because this is how the ASP.NET Framework
presents the URL to the routing system.
Notice that I didn’t need to define the routes in the test methods. This is because I am loading them directly using the
RegisterRoutes method in the RouteConfig class.
Defining Default Values
The reason that I got an error when I requested the default URL for the application is that it didn’t match the route I had defined.
The default URL is expressed as ∼/ to the routing system and there are no segments in this string that can be matched to the
controller and action variables defined by the simple route pattern.
I explained earlier that URL patterns are conservative, in that they will match only URLs with the specified number of segments.
I also said that this was the default behavior and one way to change this behavior is to use default values. A default value is
applied when the URL doesn’t contain a segment that can be matched to the value. Listing 15-9 provides an example of a route
that contains a default value.
Listing 15-9. Providing a Default Value in the RouteConfig.cs File
using System;
using System.Collections.Generic;
using System.Linq;
using System.Web;
using System.Web.Mvc;
using System.Web.Routing;
namespace UrlsAndRoutes {
public class RouteConfig {
public static void RegisterRoutes(RouteCollection routes) {
routes.MapRoute("MyRoute", "{controller}/{action}",
new { action = "Index" });
}
}
370