Skip to content

[java] Separate pattern for test classes in ClassNamingConventions rule for Java #2867

@sabi0

Description

@sabi0

Apex has testClassPattern - https://pmd.github.io/latest/pmd_rules_apex_codestyle.html#classnamingconventions

Java doesn't - https://pmd.github.io/latest/pmd_rules_java_codestyle.html#classnamingconventions

Having test classes names consistently end with "Test" is important to make sure they are correctly picked up by Maven Surefire plugin. I would say this is even more important than following other naming conventions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    an:enhancementAn improvement on existing features / rules

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions