i think you'll need a web test framework such as WatiN [http:// watin.sourceforge.net/] or Selenium [http://selenium.openqa.org/] I do know that asp.net is very difficult (if not impossible) to trutly unit/intergration test because of auto-generated control ids, and sealed http classes.
anytime i have read/seen web page testing there are 2 components. 1 unit test to test the MVC/MVP using mocks. 2. web testing framework to test the actual html. these scenarios are not using the asp.net postback model though, they are using monorail, MS MVC or their own framework which mimics the seal http classes. most implementation do not use any code behind or Bind() operations. If they are using aspx its only for the convience of the extension and IIS. there is no viewstate, postbacks or asp server controls. all html elements are manually coded. with my first TDD designed application I used the MVP pattern to minimise my usage of asp.net code behind. I created unit tests and integration tests for all parts up to the view (aspx) I used Rhino.Mocks for my mocking framework. i then manually tested the aspx pages. This worked for me because there were less than 10 pages for the system. On Feb 12, 9:49 am, Randy <[EMAIL PROTECTED]> wrote: > I'm looking into the possibility of using MbUnit but would like to > know what kind of support exists for ASP.NET and compact framework > development. > > I've looked around and can't find anything -- meaning there is no > support for these environments? > > Thanks, > > Randy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MbUnit.User" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/MbUnitUser?hl=en -~----------~----~----~----~------~----~------~--~---
