> -----Ursprüngliche Nachricht----- > Von: Eric Covener <cove...@gmail.com> > Gesendet: Dienstag, 24. April 2018 15:31 > An: Apache HTTP Server Development List <dev@httpd.apache.org> > Betreff: Re: A proposal... > > On Tue, Apr 24, 2018 at 8:50 AM, Jim Jagielski <j...@jagunet.com> wrote: > > One idea is that we setup, using the existing perl test framework, a > sort of "catch all" test, where the framework simply runs all scripts > from a subdir via system() (or whatever), and the reports success or > failure. Those scripts could be written in anything. This would mean > that people could add tests w/o knowing any Perl at all. It would > require, however, some sort of process since those scripts themselves > would need to be universal enough that all testers can run them. > > > > I may give that a whirl... I have some nodejs scripts that test > websockets and I may see how/if I can "wrap" them within the test > framework. > > I fear this would lead to M frameworks and N languages which makes it > harder for maintainers (prereqs, languages, etc) and fragments > whatever potential there is for improvements to the harness/tools.
My concern as well. I think this will lead to a less usable framework overall. It might be more usable for some, but overall it is less usable. I also have my issues understanding the Perl framework, but I think it should be one framework that is platform independent. I would say that leaves us with Perl, Python or something like that as base language. If we switch the framework we need to consider that with all gaps we have, we already have a large amount of tests in the current framework that need to be ported over time. Regards Rüdiger
