Hello,

I typically work in 2 tiered applications where the .NET windows form,
or the .NET web form does everything, except for the data layer to
manage the database. In this scenario, the UI is the 'real' unit i want
to test.

 However, i notice that the focus of MBUnit , (or even NUnit),  is
toward the library class. Am i right in this assumption ? And if so how
do you suggest people like me can step into TDD, given that all our
code is in the UI ?

I notice that NUnitForms and NUnitASP do not have a corresponding
packages in MBUnit.

Regards,

Chakravarthy

Reply via email to