On 10/22/26 11:39 AM, Giannis Christodoulou wrote:
Hi all,
I'd like to pick up some previous discussions about the test suites
[perl-to-python <https://lists.apache.org/thread.html/
v44xvtggwpqv1jcgz9v1d697jf0qc1zc> , status-of-httpd-test-suites
<https://lists.apache.org/thread.html/b8t0dkb74ddc5r736ltgfzz46pt4xqjo>].
We currently have 3 ways of doing integration testing in httpd ( httpd-
tests <https://github.com/apache/httpd-tests>, pyhttpd <https://
github.com/apache/httpd/tree/trunk/test/pyhttpd> and pytest_suite
<https://github.com/apache/httpd/tree/trunk/test/pytest_suite>).
Going through the README files, I only found a statement which describes
pyhttpd and pytest_suite as
complementary but nothing says where new tests should go.
1. Should we agree on one framework that new tests go to and gradually
consolidate into it?
My view is that pyhttpd would be a good base since each test loads
only the modules it needs
and its own config, provides per-test isolation and the MPM can be
chosen at runtime.
2. If we go with pyhttpd, we'd migrate the tests from pytest_suite
since that port looks mostly complete
and keep the Perl .t files as a reference for a final check.
I think Jim had mentioned the other way around, pulling the pyhttpd
tests into pytest_suite ( perl-to-python <https://lists.apache.org/
thread.html/v44xvtggwpqv1jcgz9v1d697jf0qc1zc> ), so that's an option too.
Of course, I'm not talking about dropping anything but more about
gradually moving in one direction
and making it obvious to the community how to contribute tests.
Please share your thoughts.
I have tried both:
I tend to prefer the pyhttpd, one configuration for a bunch of tests
more easy to debug something crashing instead one configuration of the
whole test suite. But I am probably biased as I struggled in the past
with the perl framework.
Best regards,
Giannis
--
Cheers
Jean-Frederic
