Provide a default constructor for DefaultHttpContext.

[Tratcher]

#91

[davidfowl]

I'm not sure this is enough to declare this testable (it's a start though). Let's try to get some examples of providing a form and query string without having to declare extra types.

I'd like @pranavkm @halter73@rynowak @harshgMSFT to chime in here since they have been writing unit tests agains the new HttpAbstractions. The goal here is the make it easy across the board so that frameworks like Mvc and SignalR can do it as well as end users wanting to test their controllers/hubs etc.

[Tratcher]

Then we should merge this PR and start new ones for the additional feature work.

---

From: David Fowlermailto:[email protected]
Sent: ‎7/‎7/‎2014 10:21 PM
To: aspnet/HttpAbstractionsmailto:[email protected]
Cc: Chris Rmailto:[email protected]
Subject: Re: [HttpAbstractions] Provide a default constructor for DefaultHttpContext. (#98)

I'm not sure this is enough to declare this testable (it's a start though). Let's try to get some examples of providing a form and query string without having to declare extra types.

I'd like @pranavkm @halter73@rynowak @harshgMSFT to chime in here since they have been writing unit tests agains the new HttpAbstractions. The goal here is the make it easy across the board so that frameworks like Mvc and SignalR can do it as well as end users wanting to test their controllers/hubs etc.

---

Reply to this email directly or view it on GitHub:
#98 (comment)

[davidfowl]

@Tratcher Sure, this PR is fine but the bug is about making the context more testable in general. I'll move the discussion to the bug instead of this PR.