On Jul 17, 2014, at 7:28 AM, Ron Frederick <[email protected]> wrote:
> One other challenge is that I wanted my key import/export tests to test > interoperability with other tools like openssl and ssh-keygen. However, that > meant the script had dependencies on those external tools being installed on > the system. That's no problem when I run the tests here, but I'll probably > need to find a way to conditionalize these tests for running on systems > without the tools installed. This may also hurt the portability of the code. > Again, any suggestions or pointers to examples of good ways to deal with this > would be appreciated! Conch's test suite might be a resource to you, since it solves exactly all of these problems and has quite comprehensive unit test coverage. Twisted's 'trial' testing tool, which Conch uses, is both quite similar to and interoperable with standard library unit testing (and the extra features it has are mostly related to letting you do more 'real' I/O in your tests, which are a bad idea for unit tests). -glyph
