Don't require javadoc for tests

Repository metrics

Stars

1,312 stars (1,312 stars)

PR merge metrics

No merged PRs in 30d (No merged PRs in 30d)

Description

[INFO] Starting audit...
[WARN] /Users/elharo/google-http-java-client/google-http-client-test/src/main/java/com/google/api/client/test/util/store/AbstractDataStoreFactoryTest.java:62:3: Missing a Javadoc comment. [MissingJavadocMethod]
[WARN] /Users/elharo/google-http-java-client/google-http-client-test/src/main/java/com/google/api/client/test/util/store/AbstractDataStoreFactoryTest.java:86:3: Missing a Javadoc comment. [MissingJavadocMethod]
[WARN] /Users/elharo/google-http-java-client/google-http-client-test/src/main/java/com/google/api/client/test/util/store/AbstractDataStoreFactoryTest.java:126:3: Missing a Javadoc comment. [MissingJavadocMethod]

Contributor guide

Research direction

Modify the Checkstyle configuration to suppress the MissingJavadocMethod rule for test source directories. Look for the Checkstyle configuration file (e.g., checkstyle.xml or configured in pom.xml) and add an exclusion for the test directory pattern, such as '**/test/**' or similar. Test that the change works by running `mvn checkstyle:check` on the module.

Tech stack

java

Domain

build systemdeveloper experience

Issue type

Chore

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

Under 1 hour

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

Stale

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

Clear

Prerequisites

Java programmingCheckstyle configuration

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

80