Abstract classes treated as tests, even when they used to not be

[Crell]

Q	A
PHPUnit version	10.3.5
PHP version	8.1
Installation Method	Composer

Summary

I have some abstract classes in my tests, as a test hierarchy. The idea is that several different implementations of a thing all use the same tests in the base class, just providing an alternate implementation. I had the abstract base classes named FooTest, with child classes FooTypeATest, FooTypeBTest, etc. This worked fine in PHPUnit 9.

In 10.3, it still runs but I get a warning that the class is abstract. Which... yes, it is, but why would PHPUnit 9 rightly just ignore it, while PHPUnit 10 is giving me a warning? Is this deliberate?

[ghostwriter]

#5132

[sebastianbergmann]

Yes, this is deliberate.

[borgogelli]

Yes, this is deliberate.

@sebastianbergmann I think that it's counterintuitive and logically incorrect.

The problems generated are an avalanche:

1. phpunit returns the exit code 1 even if the failOnWarning option is set to false
2. So to solve the problem, the user is forced to transform the abstract class into a concrete one
3. I have to create a dummy test method inside it to avoid other errors.

[ghostwriter]

If an abstract class name ends in *Test (*Test.php), rename the class and file.

eg. Abstract*Test to Abstract*Testcase

[borgogelli]

If an abstract class name ends in *Test (*Test.php), rename the class and file.

eg. Abstract*Test to Abstract*Testcase

I know that I can't use the Test suffix, but problem persists with PHPUnit 10.4.2
Could be the cause that I extends the class TestCase ?