Static methods called dynamically in documentation

[BenMorel]

In PHPUnit, all assertions are static methods:

public static function assertTrue($condition, $message = '')

But the documentation has always suggested to call them dynamically:

$this->assertTrue(false);

And most of the tests I've seen have been following this convention so far (including mine).

It doesn't seem to be a problem for PHP, which doesn't complain in any error reporting mode; but in addition to being a code smell, this approach triggers the static code analysis tools of my IDE, which keeps complaining about static methods called dynamically.

Is there any reason why the documentation shows dynamic calls to the assertion methods?

The whole documentation could be re-written in the following manner:

self::assertTrue(false);

Is there any reason not to?

[sebastianbergmann]

This is not a discussion or support forum, sorry.

[BenMorel]

This was a preliminary question to offer a contribution to the documentation, but it was seemingly misunderstood.

I wish you well.

[hboomsma]

@BenMorel see #1914

[BenMorel]

@hboomsma Thanks for the pointer!