in reply to Handling config-files in Tests (SOLVED)

You have an answer that works for now, however you might want to consider that hard-coding the configfile's location relative to the module location is poor. Much better would be to have that as a default location and provide a mechanism, probably through an import() function, that allows for that location to be overridden. Then, you can use that mechanism within your tests.

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

Replies are listed 'Best First'.
Re^2: Handling config-files in Tests
by CountZero (Bishop) on Feb 17, 2007 at 10:55 UTC
    That would make it more flexible indeed and I might consider that for a next version. Thanks!

    CountZero

    "If you have four groups working on a compiler, you'll get a 4-pass compiler." - Conway's Law