ASP.NET OOP and Unit Testing: ASP Alliance

Print Add To Favorites Email To Friend Rate This Article
ASP.NET OOP and Unit Testing

page 1 of 7

Published: 02 Jul 2007

Abstract
This article discusses some of the approaches to business logic in an ASP.NET application, as well as using unit testing for an ASP.NET site. It shows you how a Model-View-Controller approach can be used in a web application.

by Brian Mains
Feedback

Average Rating: This article has not yet been rated.
Views (Total / Last 10 Days): 38382/ 147

Article Contents:

Introduction

ASP.NET is a very functional framework for developing web applications. Creating an object-oriented solution is harder to do so because of the coding effort involved with doing so. This coding effort means creating a custom page or user control class that drives the ASP.NET page.

You may wonder why you would want to do all that work to get around a few complicated problems. The biggest benefit that I have found is that with this extra work, it is possible to unit test ASP.NET pages, which is a huge benefit to ensure that application logic is correct. You can ensure that controls are shown/hidden, that the data displays correctly, and test many of the other visual mechanisms as well. The drawbacks to this approach are the strong coupling between the ASP.NET page and the custom page object and the level of coding effort involved.

There are some challenges when working with ASP.NET objects that I will explain in detail later on. Before we start looking at the problem and the solution, an understanding of some of the capabilities is needed.

View Entire Article

(Page 2) »

User Comments

Title: jjjjjk
Name: gggg
Date: 2012-10-13 3:17:31 PM
Comment:
gggg

Title: RE: Unit Test Bangs
Name: Brian Mains
Date: 2010-04-18 10:49:40 AM
Comment:
Unit testing for simple applications can surely be done; unit tests only help strengthen an application, but unit tests add time, so for a small project, manual unit testing by the user probably is all that is necessary.

The real question is: is the application going to grow? If it will eventually become a big app, unit testing may be favorable to grow with that application.

But IMHO no you don't need unit testing for a small application, unless you want to to strengthen the application.

Title: Unit Test Bangs
Name: Chennaite
Date: 2010-04-13 8:00:19 AM
Comment:
Nice Article. but still need to know whether we need unit testing for simple applications?..

Hats off for brain.

Title: Good Article's
Name: LoveIndonesia
Date: 2009-10-28 5:59:38 AM
Comment:
good articles but sometime i can't understand the mean in article because my english is bad.:D

Title: wow. just what i needed.
Name: d potter
Date: 2009-07-22 1:06:37 PM
Comment:
this article explained just what i needed to know at just the right level of detail. spot on, man.

protip: if you're stubbing both Request and Response, combine them into an IRequestResponseManager so your stub can share the same HttpCookieCollection across simulated redirects/etc.

Title: Timely info
Name: Scheffler
Date: 2008-08-26 6:45:50 PM
Comment:
Nice article Brian. I had a similar need today and this fit the bill quite nicely. I used a pared down version of the ISessionStateManager interface you defined above because I was only barely interacting with the Session state collection. However, this has allowed me to nicely stub out and test locally my persistence logic for some prototyping work before fully fleshing out my NHibernate logic.

Thanks for taking the time to write and share your idea.

Title: Good
Name: venkat
Date: 2008-01-25 2:43:08 AM
Comment:
its Good...! better to provide code for this.

Title: good
Name: max
Date: 2007-10-09 3:07:04 AM
Comment:
this article is very..good...keep it up