[NUnitAsp-devl] NUnitAsp refactoring ideas

[Jim L. <jl...@cu...>]

Brian Knowles wrote:
> We'll wait for your ideas before we do any kind of
> release. There's quite a bit of docs to write before I
> feel we can release anyway.

The main thing that's bothering me about the code right now is that both
Browser and WebFormTestCase are starting feel a little big.  It's
getting hard to find my way around those classes.  I'd like to refactor
them into multiple classes.  My initial thought involves involves
creating classes that can parse and possibly assert on each of the
ASP.NET components.

Another thing I'd like to do is modify Browser so that it no longer
takes a form name argument.  I believe that ASP pages only have one
form... if so, we don't need a form name.  Perhaps we could overload
that method.

In WebFormTestCase, I'd like to modify the asserts so that the
AssertXxxExists and AssertXxxDoesNotExist methods are consolidated into
a single AssertXxxExists(boolean exists).  I'd like to remove assert
methods that we aren't certain to need.

Those are the changes I'd like to make before 1.0.  I feel that we're
somewhat committed to long-term support of an API once we release v1.0,
so I want to make the big changes first.  I also want to make sure that
the API we release is as minimal as possible, since it's easier to add
to an API than to modify or remove from it.

Longer-term ideas that have been percolating to the surface as I've been
using NUnitAsp are XML-based test drivers (for customer-driven
acceptance testing) and an in-process component renderer for testing
ascx's.  I'd also like to see the HTML rendering in NunitGui that Brian
once mentioned.  And, of course, we need to expand our test cases.

> Let us know what your ideas are.

There you have it.  Sorry you asked?  ;)

Jim