Hi, On Fri, Jun 24, 2016 at 06:04:14PM +0200, David Sommerseth wrote: > > Perl has the advantage of being available on all platforms (or at least > > "you can install it", I know it's not there out of the box everywhere) > > so maybe we can do a common test driver implementation that runs on > > windows and unix, so less maintenance... > > That argument can be said about Python as well. And there's a lot of > different testing resources for Python, a lot of them are unittest > oriented (so not so directly interesting for us) but there are others > which also "drives" external test cases. Beaker [1] is the one I've > worked most with, but that is overkill in this scenario. But there are > most likely lots of stuff we can extract and reuse too. And there are > several others which I don't recall right now.
The point is not so much "running arbitrary tests" but "controlling
OpenVPN in a scripted way" - what t_client does as a shell script today.
> We might also consider if there are possibilities for us to integrate
> such tests with Travis or similar stuff for platforms where that is
> possible. Often these solutions have Python or Ruby modules available too.
While totally interesting, how is this going to help with *Windows*
testing (which is what this thread is about)?
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
signature.asc
Description: PGP signature
