On 10/05/06, Joost van der Sluis <[EMAIL PROTECTED]> wrote:
Or else I've to add wrappers for all the properties I want to change.
for example 10 tests, running with 20 different settings writing =
20*10=200 procedures...
I haven't had a look at you code, but I would imagine the Setup and
TearDown does the bulk of the work. Each test procedure would then
consist out of two or three lines of code. One line to set the
property. One line to execute the DB Read (or whatever you do). One
line to test the result.
As Dean said, you could also read values from a INI file or something.
In one of my projects I prompt the user for answers the first time
the tests are run. I then store those values in a INI file. After
that the tests check to see if a answer exists in the INI file, if so,
it uses it, otherwise prompts the user again.
Thats just one example of using INI files with tests. Other ways are possible.
Regards,
- Graeme -
--
There's no place like 127.0.0.1
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
