[src/04_solution-strategy/index.md] Naming conventions: Test method names

[jmewes]

References

• https://medium.com/@stefanovskyi/unit-test-naming-conventions-dd9208eadbea
• https://dzone.com/articles/7-popular-unit-test-naming
• https://stackoverflow.com/questions/155436/unit-test-naming-best-practices
• https://github.com/experimental-software/LessonsLearned/blob/master/SoftwareEngineering/Architecture/Architecture.md

[jmewes]

All tests should have a @DisplayName annotation which explains the test case, starting with the expected behavior and ending with the given condition. The test method name should start with the prefix test_ and then some keyword in snake case.

    @Test
    @DisplayName("Should do $X$, if $CONDITION_Y$")
    void test_$METHOD_UNDER_TEST$_$KEYWORDS$() {
        assertThat(true).isTrue();
    }

Example:

TBD

[jmewes]

There should be an arch unit rule that validates the test method names

https://github.com/TNG/ArchUnit/issues/1019#issuecomment-1338953322