Re: Direction for test frameworks: Perl TAP vs. Python/pytest

On 16.06.26 17:23, Daniel Gustafsson wrote:
>> That's a fair concern. It seems to me that back-patching TAP tests
>> doesn't happen too often.
> A quick look at REL_14 shows that there have been 450+ commits touching
> src/test in some fashion since 14.0 was stamped. It's not the same as
> backpatching of TAP tests but it's a data point.

git log --oneline REL_14_0..REL_14_STABLE -- **/t/*.pl src/test/perl | wc -l
172

So a bit less than 450.

So basically what you'd sign up for is that about 35 test changes per
year have to be written twice.

I mean, even in the current setup, there are sometimes significant
differences in the Perl test framework between major versions. So the
current number isn't zero.

Personally, I find the idea of doing a wholesale conversion of the tests
in a backbranch to be horrible. I wouldn't trust such a thing. And the
amount of work to actually put that together in the first place would
most likely be much larger than converting test changes on the go as needed.