in reply to Re^2: Interactive tests
in thread Interactive tests

The nice solution is to detect if a test database can be accessed, and if not print a warning and skip the tests.

Replies are listed 'Best First'.
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]
      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]
        Good point, it certainly can, dunno why i didn't think of that to start with. :o) Thanks for the help, I'll tweak the test scripts somewhat.
[reply]

In Section Seekers of Perl Wisdom