How to name tests for Laravel? Annotation or prefix "test"?

Question

PHPUnit

Actually, what is the correct name for functions for tests, or how do you call them in your company?

according to PSR, I have to call functions in camelCase, but at the same time, Laravel itself (just like Symfony) generates snake_case through make

public function test_example()
    {
        $response = $this->get('/');

        $response->assertStatus(200);
    }

Well, as for the "test",
What do you think is more correct?

/**
     * @test
     */
    public function some_example()
    {
        $response = $this->get('/');

        $response->assertStatus(200);
    }

or

public function test_some_example()
    {
        $response = $this->get('/');

        $response->assertStatus(200);
    }

As I was told, not all versions of UnitTest can correctly support the @test annotation in dockblocks, but to be honest, I have never seen this, in some legacy code, if only or am I looking in the wrong place?

Answer 1

I prefer prefix. Simply because it does not require a separate line in the docblock, which is already growing due to argument descriptions, data providers, and a human-readable test name.
Names in snake_case are preferable because long method names in camelCase are much harder to read.