Hi,
The two applications you mentioned, NUnitForms and NUnitASP are targeted towards NUnit. We don't maintain a MbUnit port here as it would mean branching code off these two projects and that quickly becomes unmangeable.
MbUnit can be easily ported to these projects however as MbUnit supports the NUnit Fixture and Assert list so more often than not you can adapt any NUnit code used by replacing the imports to MbUnit.Framework; and adding a referance to
MbUnit.Framework.dll. Sometimes you may need to adapt some of the fixtures but in general we have a greater range of Assert's that you can use to adapt the NUnit code. If you do change the code to support MbUnit then be sure to share back with the NUnitForms\NUnitASP communites.
Thanks
Andy
On 12/31/05, Chak <[EMAIL PROTECTED]> wrote:
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
