In the template MVC 4 project there is no longer a MyApplication.RegisterRoutes method, rather routes are registered in RouteConfig.RegisterRoutes.
The RouteTester constructor looks for the presence of the RegisterRoutes method and calls it to initialise the registrations. When the method is not found all the tests fail. There is a workaround which is of course to add the RegisterRoutes method
back in for MVC 4 projects, but this is not ideal.
Really the constructor should now also check for RouteConfig.RegisterRoutes and call that if found, otherwise unfortunately this package won't get much take up with MVC4.