> > Some things to consider when using extensive Javascript: > * Use a Javascript unit testing framework such as JsUnit > http://www.edwardh.com/jsunit/ > There are some examples of JsUnit tests in our Remote Scripting client > http://www.thycotic.com/dotnet_remotescripting_client.html > * Any browser could turn off Javascript or some paranoid companies have > even been known to filter it at the proxy server! How would your > application handle that? For this reason, you still need to be doing > validation (etc) back at the server anyway.
All good points, but alas, there is still a class of intranet apps that really can not be tested, in any meaningful way, unless the client browser environment is being simulated. I wanted to compare and contrast it with the Humble Dialog (NUnit/MVP) approach, which I'm actually quite committed to, but of course does not touch the UI at all and therefore could use a complementary method. I was looking at NUnitAsp to fill the missing role of top level UI regression tester, or possibly more. Anyway, the two approaches are definitely not mutually exclusive. But great video, I feel I understand the issues now. Thanks, Mike [Non-text portions of this message have been removed] ------------------------ Yahoo! Groups Sponsor --------------------~--> Has someone you know been affected by illness or disease? Network for Good is THE place to support health awareness efforts! http://us.click.yahoo.com/Rcy2bD/UOnJAA/cosFAA/X1EolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetMetroArea/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
