Re^2: Interactive tests

Yup, see where you're coming from, and it makes perfect sense.

The test file in question relies on some entries in the (test/local) database, so perhaps a nice big warning is enough.

I just don't want future users being a bit baffled as to why tests may fail.

Comment on Re^2: Interactive tests

Replies are listed 'Best First'.
Re^3: Interactive tests by moritz (Cardinal) on Apr 17, 2008 at 21:32 UTC
The nice solution is to detect if a test database can be accessed, and if not print a warning and skip the tests.	[reply]
Re^4: Interactive tests by Cagao (Monk) on Apr 17, 2008 at 21:39 UTC
Aye, but in this instance it's not a case of whether the test db can be accessed, it's whether the user has updated it accordingly.	[reply]
Re^5: Interactive tests by moritz (Cardinal) on Apr 17, 2008 at 21:44 UTC
Why can't the program update the db? Why does the user have to do it? Update: and if it can't be modified programmatically, can the test detect it at least?	[reply]
Re^6: Interactive tests by Cagao (Monk) on Apr 17, 2008 at 22:08 UTC