#phpunit

> However, if we mandate that every set of arguments is keyed by a meaningful string then this is super useful.

That is super useful, but it's code, not documentation. Out of scope for this issue?

> If we follow the core standards of documenting @return and @param tests will have a lot of boilerplate that does not add much.

Documenting both the @return of the provider and the @params of the tests is writing the same thing twice, and redundant, but *one* of them should be documented!

This seems to duplicate part of #2057905: [policy, no patch] Discuss the standards for phpunit based tests → . Is it meant to be getting split off from that?

-1 from me anyway for the @group tags as described -- they just duplicate the folder structure, so they don't add anything.

PHPUnit annotations are now attributes -- IS needs an update for this.

> Use @group Drupal to allow filtered testing.
> Use @group Namespace or similar for further filtering. e.g: @group Entity

What is the point of this? If all the Drupal core tests are in core/tests, then you pass that as a parameter to PHPUnit instead of a @group.
If all the tests for core/lib/Core/Foo are in core/tests/Foo, then you pass that.

Given how much people are complaining about writing docblocks for test methods in 📌 [policy] Remove the requirement for doxygen for test methods Needs work , why are we adding superfluous @group tags?