What can you say about test names?

Test names should be informative and understandable so that it is immediately clear what is being tested. A good test name describes the condition and the expected result.

For example, instead of test1(), it is better to use shouldReturnErrorWhenInputIsEmpty().

This helps quickly understand the purpose of the test without having to read its code, making maintenance and problem-solving easier.

It is also recommended to adhere to a consistent naming style in the project and avoid overly long or abstract names.