Add a code coverage tool
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- java
- Domain
- build-system, testing-qa
Research direction
No files, build entry point, or test path are named. Start by inspecting the Java project's build configuration and unit-test setup, then identify where a coverage tool would be integrated; done means unit-test coverage is collected and its report can be verified.
Written by the indexing model from the issue text.
Description
Add a tool like jacoco to track code coverage of unit tests
- Dominant language
- Java
- Stars
- 6
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Appdynamics/iot-java-sdk
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
Appdynamics/iot-java-sdk#13 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in Appdynamics/iot-java-sdk
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
elastic/gradle-plugins#157 ·
-
enhancement Tools
Difficulty 1/5 Under an hour Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
apache/rocketmq-dashboard#5008 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
DETECT_PARAMETER_NAMES=false silently disables @ConstructorProperties-based Creator detection too Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
FasterXML/jackson-databind#6229 ·