I want to unit test a method that has httpcontext and route , routehandler but the rout value is null and it fails

Question

0.00/5 (No votes)

See more:

Hi,

I am trying to unit test a method that converts a razor (cshtml) view to a string and returns it.
I tried to mock the HttpContext but was not very successful.

here is the method:

C#

public static string RenderViewToString(string viewPath,object model = null)
{
	var context = new ControllerContext(HttpContext.Current.Request.RequestContext, new MyController());
	// first find the ViewEngine for this view
	ViewEngineResult viewEngineResult = ViewEngines.Engines.FindView(context, viewPath, null);
	
	var view = viewEngineResult.View;
	context.Controller.ViewData.Model = model;

	string result = null;

	using (var sw = new StringWriter())
	{
		var ctx = new ViewContext(context, view,
									context.Controller.ViewData,
									context.Controller.TempData,
									sw);
		view.Render(ctx, sw);
		result = sw.ToString();
	}

	return result;
}

What I have tried:

This method works fine when executed but I have trouble to unit test it as the context.Route value comes empty.

Any suggestions?

Posted 24-Mar-21 4:49am

kianoush torkzadeh

Updated 24-Mar-21 5:41am

Richard Deeming

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Answer 1 · 2021-03-24T05:41:00

You won't be able to test that method, since it's using HttpContext.Current.

You should change the method so that you pass in an HttpContextBase instance - or preferably a RequestContext instance - as a parameter.

C#

public static string RenderViewToString(RequestContext requestContext, string viewPath, object model = null)
{
    var context = new ControllerContext(requestContext, new MyController());
    ...

Code that calls it from within a controller can pass in the controller's ControllerContext.RequestContext instance.

Code that calls it from a static method can pass in HttpContext.Current.Request.RequestContext, or be modified to accept the RequestContext as a parameter.

Your unit test code then only needs to mock the RequestContext object.