Unit testing ASP.NET Legacy code

Question

I have list of ASP.NET legacy projects. In these projects business logic is tightly bound with the Pages. All the authentication and other stuff is written in load and click events in the code behind. I am using Visual Studio 2012.

What is the best way to unit testing these projects?

Working Effectively with Legacy Code, by Michael Feathers.

Oded
– Oded

2012-10-10 09:51:05 +00:00
Commented Oct 10, 2012 at 9:51 — Oded
– Oded, Commented Oct 10, 2012 at 9:51

Jaimal Chohan · Accepted Answer · 2012-10-10 09:56:32Z

1

When unit testing legacy ASP.NET code, some of the hardest challenges are in mocking out stuff like the Session, HTTP Context and the Page Object. To isolate these you end up having very messy mocking logic, usually involving a lot of reflection and run-time injection of values.

TypeMock is invaluable here as it has everything you need to isolate diificult to mock types like the ones above, and also has a lot of helpers for mocking the the ASP.NET pipeline without having to rely on a web server.

answered Oct 10, 2012 at 9:56

Jaimal Chohan

8,6557 gold badges45 silver badges65 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Unit testing ASP.NET Legacy code

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related