Agreed
> On Oct 26, 2026, at 5:58 AM, Joe Orton <[email protected]> wrote:
>
> On Thu, Oct 22, 2026 at 06:51:57AM -0400, Eric Covener wrote:
>>> We currently have 3 ways of doing integration testing in httpd (
>>> httpd-tests, pyhttpd and 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.
>>>
>>> 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.
>>>
>>> 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 ), 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.
>>
>> No strong opinion here, and with little experience in either python
>> suite, I would have thought new tests in pyhttpd but don't bother
>> porting pytest_suite stuff into it -- keep them running in-place in
>> the ported suite. Not to completely rule out adding to pytest_suite
>> tests, new permutations of stuff in old tests as needed would make
>> sense.
>
> This is roughly my position as well.
>
> I think it would make some sense to migrate pytest_suite tests into
> pyhttpd gradually / in the long run, particularly if we keep the Perl
> tests running as a regression baseline forever.
>
> Regards, Joe
--
Jim
"This is an outrage!"
Tony Harrison
