TypedDevs
A test with no assertions should fail?
Add a configuration that allow the user to say if a test has no assertions should fail.
What about not fail but raise a note saying "no assertions found in this test"?
Actually, for the first iteration, we can simply go with the failing option, and revisit/improve if needed later.
To me it should be a configuration, while doing TDD I would never want a test that does not assert anything, and we are nor offering any code coverage metric, so for me a test with no assertion should be by default a test that fails, unless you can tell me a case in which this could be a problem
What about not fail but raise a note saying "no assertions found in this test"?
Actually, for the first iteration, we can simply go with the failing option, and revisit/improve if needed later.
I found this reading phpunit docs:
https://docs.phpunit.de/en/10.3/writing-tests-for-phpunit.html#incomplete-tests