0

My office has a suite of web reporting engines written in VB. All in all there's about 300 reports with varying displays depending on the data being input into them. I'm trying to establish an efficient way to deal with such a major diversity, but am struggling with creating a system that won't be a nightmare to code/maintain.

What I've considered doing is:

  1. On program launch, read the steps required for each test page. This may have multiple tests for the same page with varying inputs.
  2. Write each iteration of the test in XML file under $env:temp/testname
  3. Use the TestCaseSource attribute of Nunit to funnel every related xml file as a source.

My major stumbling block has been how to get that data to the Nunit framework. Is Nunit really appropriate for what I'm trying to do, or is it too static?

Improve this question
2
  • Did you combine TestCaseSource with a test data factory producing TestCaseData objects, like shown in the NUnit docs here nunit.org/index.php?p=testCaseSource&r=2.5.9 ? This seems to allow dynamic test data generation at run time.
    – Doc Brown
    CommentedNov 12, 2013 at 17:22
  • @DocBrown: I hadn't seen something in quite that direction. I think yielding an instruction step would actually bypass the need of an XML file. Mind C&P'ing that into an answer?
    – Jacobm001
    CommentedNov 13, 2013 at 16:52

1 Answer 1

Reset to default
1

You can combine TestCaseSource with a test data factory producing TestCaseData objects, like shown in the NUnit docs here http://www.nunit.org/index.php?p=testCaseSource&r=2.5.9

This will allow dynamic test data generation at run time. Maybe that is what you are looking for.

Improve this answer

    Start asking to get answers

    Find the answer to your question by asking.

    Ask question

    Explore related questions

    See similar questions with these tags.