Skip to content

Remove RemoveTestPrefix from "best practices" composite recipe #927

@jeffjensen

Description

@jeffjensen

What problem are you trying to solve?

RemoveTestPrefix is invoked by multiple composite "best practice" recipe paths. Yes, test was once a required method prefix and now is not, but removing it isn't a best practice it is more of a test naming preference. In fact, multiple teams I've worked on prefer to keep it so the IDE's method list clearly shows the test methods apart from the supporting methods in the test class (especially with a sorted list).

Have you considered any alternatives or workarounds?

It is large effort of creating multiple custom recipes to disable it (just try the assertj recipe).
Without the "excludeRecipe" feature, avoiding it is not a quick effort.

Any additional context

When a team wants to remove test as a prefix, they can run the single recipe.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions