I would urge you to rethink that. For run of the mill
basic form driven applications, you can often times
scale down your unit testing.
But, as soon you start working on complex
applications with extremely complex business rules,
unit testing is a must. Being able to rerun your
unit tests in mass during development and prior
to builds is an invaluable way to reduce errors
visible to your ui development team and
your quality assurance testers. If implemented
properly, it can be a time saver over not
unit testing at all.
--
Robbe Morris - 2004-2006 Microsoft MVP C#
Earn money answering .NET questions
http://www.eggheadcafe.com/forums/merit.asp
"Jon Paal" <Jon[ nospam ]Paal @ everywhere dot com> wrote in message
news:%2***************@TK2MSFTNGP11.phx.gbl...
with try catch statements you can see your results or
-- you could just trap the desired information in a output value or
-- javascript alert and then you can see what is happening.
I find this to be much easier than doubling my workload to build nunit
tests and tests to test my tests :)
"Diffident" <Di*******@discussions.microsoft.com> wrote in message
news:09**********************************@microsof t.com... Hello All,
Can anyone please suggest me a good unit testing tool. I have seen NUnit
but
not sure on how I can use it to test my methods which involve session
variables, viewstate variables, textbox values.
I understand that NUnit is more suitable for OO methods which take set of
parameters and return an output parameter. How about tools for testing
methods which use state variables and form values?
Thank you!!