Re: Dynamically Defining Tests from Config File

"Brandon Payton" <[email protected]>
Newsgroups gmane.comp.windows.dotnet.nunit.user
Message-ID <[email protected]>
On Nov 30, 2007 9:03 AM, Brad Stiles <[email protected]> wrote:
> Brandon Payton <[email protected]> wrote:
>
> > If there is an approach to this that would stay in the spirit of the
> > NUnit architecture while allowing me to define separate tests for each
> > parameter/output set, could you please point me in the right
> > direction.  (It can be a very general pointing...)
>
> Your description sounds like you are doing acceptance or integration
> testing, rather than developer testing.

The purpose of the tests is to establish a baseline of behavior before
some heavy refactoring.  The component being tested is an ActiveX
control that takes a number of parameters before loading, and I am
trying to verify that particular features are enabled/disabled based
on those parameters.  This would then allow me to refactor while
comparing behavior to the original design.  Ideally, this would have
little if anything to do with the UI, but that's why it should be
refactored.

Would this be considered "acceptance testing", and if so, what would
you consider "developer testing"?

I suppose it doesn't really matter as long as it's _automated_ testing.

Thanks for your response.

> That's not to say you can't do
> it in NUnit; I've done that sort of thing using an XML "table" for
> holding the data I want to pass to the test.  The actual test method
> simply loops over that data, supplying it to whatever methods are being
> tested, and reporting the results out through the GUI or the log.

-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell.  From the desktop to the data center, Linux is going
mainstream.  Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.