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 4 of 7

by Brian Mains
Feedback

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

Article Contents:

ViewState Objects

ViewState seems to work well with the unit testing framework; though I thought I remembered seeing problems with this in the past, recent tests show that it does not seem to have the problems that I thought it did. So the view state may be a safe mechanism to work with. You can reference the keys and retrieving values from it as you would in any ASP.NET page. The internal mechanism is a System.Web.UI.StateBag object, and after investigating, I did not come across anything that may hinder unit testing.

« (Page 3)

View Entire Article

(Page 5) »

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