In the past I've tested web interfaces in various ways, including with automated tools.
I'm currently working with ASP.NET sites which rely on jQuery for some AJAX interaction with a Web Service. (This is NOT MS Ajax.) Page content is dynamic. I've tested with my own techniques (mostly manual, I do use automated testing for markup syntax, JScript, links etc.) so far and not entrusted it to a test framework. In the past these tools have caught my attention as maybe being ways to do such testing with MBUnit. Watin (and Watir) Selenium WebAii SWEA There are probably more too. I find it difficult to do a good analysis of this. I usually test on several browsers (IE, FF, Opera, Safari and Chrome). Is there a good evaluation of the merits and troubles of using different ways to link browser testing into MBUnit? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
