On 24/06/16 19:33, Gert Doering wrote: >> > 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)?
Having a standardised testing framework makes it possible to run a similar set of tests (comparable to what t_client.sh does today) in an automated way across multiple platforms, and can report these results to a shared hub. This way we can run automated tests and catch regressions which is not caught by our current buildbots ... such as the Windows platform. These test cases can then be extended too, to test even more of the feature sets. With a good test framework you can for example define that you have 1 server and 10 clients doing various work in parallel. Other scenarios can be performance testing, if performance drops below a predefined limit, we will get alerts ... and so on ... and I did mention cross platform testing? But! Building such a framework takes a lot of time, which is why it is good to build on what others have already done. Of those things I've seen, much of them have been written in Python or Ruby to some degree - but also a lot of things in bash too for Linux based testing. -- kind regards, David Sommerseth
