PerformanceTiming has 45 methods (exceeds 20 allowed). Consider refactoring. Open
public interface PerformanceTiming {
/**
* Returns the value that corresponds to the {@code navigationStart} event.
*Name 'io.fluentlenium.core.performance' must match pattern '^org.[a-z]+(.[a-zA-Z_][a-zA-Z0-9_]*)*$'. Open
package io.fluentlenium.core.performance;- Read upRead up
- Exclude checks
Checks that package names conform to a specified pattern.
The default value of format for module PackageName has beenchosen to match the requirements in the JavaLanguage specification and the Sun coding conventions. Howeverboth underscores and uppercase letters are rather uncommon, so mostconfigurations should probably assign value ^[a-z]+(\.[a-z][a-z0-9]*)*$ toformat for module PackageName.
This documentation is written and maintained by the Checkstyle community and is covered under the same license as the Checkstyle project.
This class has a bunch of public methods and attributes Open
package io.fluentlenium.core.performance;
import java.util.concurrent.TimeUnit;
import static java.util.concurrent.TimeUnit.MILLISECONDS;- Read upRead up
- Exclude checks
ExcessivePublicCount
Since: PMD 1.04
Priority: Medium
Categories: Style
Remediation Points: 50000
Classes with large numbers of public methods and attributes require disproportionate testing efforts since combinational side effects grow rapidly and increase risk. Refactoring these classes into smaller ones not only increases testability and reliability but also allows new variations to be developed easily.
Example:
public class Foo {
public String value;
public Bar something;
public Variable var;
// [... more more public attributes ...]
public void doWork() {}
public void doMoreWork() {}
public void doWorkAgain() {}
// [... more more public methods ...]
}