Why doesn NUnitAsp support frames / Javascript / pop-up windows / more HTML controls?
NUnitAsp’s purpose is to enable test-driven development of ASP.NET code-behind methods. If you use NUnitAsp to do so, you’ll find that the lack of Javascript, etc. is much less of an issue. When you write an NUnitAsp test, focus on testing the behavior of a specific page or even a specific user control. We expect you to ignore frames, Javascript, and other client-side issues and focus on testing code-behind logic. We would like to provide more robust client-side support, but given our limited manpower, we have decided to focus on the code-behind unit-testing aspect of NUnitAsp instead.
