Be the first to post a text review of NUnitAsp. Rate and review a project by clicking thumbs up or thumbs down in the right column.

View all reviews

• Tracker artifact added

  kkhaitan created the Support for Multiple Forms in NUnitAsp artifact

  posted by kkhaitan 209 days ago

• Tracker artifact added

  kkhaitan created the Support for Multiple forms artifact

  posted by kkhaitan 212 days ago

• Tracker comment added

  Anonymous commented on the ControlTester update for ASP .Net 2.0 with Validators artifact

  posted by nobody 430 days ago

• Tracker comment added

  kruemelmo commented on the NUnitASp performs web requests when using XHTML artifact

  posted by kruemelmo 478 days ago

• Tracker artifact added

  Anonymous created the ParserException for HTMLAnchorTester artifact

  posted by nobody 698 days ago

• Tracker comment added

  Anonymous commented on the Getting a System.NotSupportedException artifact

  posted by nobody 698 days ago

• Code committed

  jlittle82 committed patchset 317 of module NUnitAsp to the NUnitAsp CVS repository, changing 1 files

  posted by jlittle82 703 days ago

• End of NUnitAsp Development

  Hi all, I'm making it official: I am no longer maintaining or supporting NUnitAsp. I've been neglecting NUnitAsp for several years, so I doubt this is a surprise. I originally wrote NUnitAsp in 2002 (starting with a seed provided by Brian Knowles), before .NET was even out of beta, to solve the problem of unit testing ASP.NET code for a portal application. As the portal grew more complex, so did NUnitAsp. But this approach always led to holes in NUnitAsp--the features of ASP.NET I didn't use didn't get any love. One big example: I always worked strictly in the ASP.NET component model, so my pages never had more than one form and I didn't use HTML or Javascript directly. That project ended years ago, but I kept NUnitAsp alive, even though I haven't written any ASP.NET code for a long time. The NUnitAsp v2.0 release last year was my last attempt to fill in the big holes. Now it supports multiple forms, has a simpler syntax, and it tests HTML as well as ASP.NET server-side components. NUnitAsp still has some dramatic flaws: no support for Javascript, tests running in a different process than ASP.NET, difficulty setting up sessions. Most people ended up using it for acceptance testing, rather than unit testing, and Selenium, Watir, and the like are better for that. Most folks "in the know" are using presentation layers to make ASP.NET so thin that a tool like NUnitAsp isn't helpful. Despite these flaws, I think NUnitAsp is an interesting tool. I'm proud of the code and the API. If nothing else, it's a good example of what a dedicated agilist will do when faced with a brand-new platform: he finds a way to unit test it. If you would like to take over development of NUnitAsp, and you have name recognition in the community, I will be happy to hand it over to you. If I don't recognize you, feel free to fork the code. When your fork is successful, let me know, and I will give you the keys to the "official" project. NUnitAsp still gets between one and two thousand downloads per month, so it's not quite dead yet. Thanks for your interest in NUnitAsp and in sticking with me over the years. I'm not going away, of course--I just have other projects that are occupying my time. I write about them at http://jamesshore.com. Best wishes, Jim

  posted by jlittle82 703 days ago

• Tracker artifact added

  blaqflame created the VS 2005 DOCTYPE xhtml 1.0 Breaks Version 2.0 artifact

  posted by blaqflame 704 days ago

• Tracker comment added

  blaqflame commented on the HTML DocType requirement artifact

  posted by blaqflame 704 days ago