[UserStory] Integrate OpenClover into Project Build Environment

[shadycloud]

User Story

Essential components

• [x] Title describes the story
• [x] Stakeholder type is identified
• [x] Outcome is described
• [x] Rationale is explicit
• [x] Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a Developer
I want OpenClover integrated into the build
so that I can better evaluate the quality of the source code.

Acceptance Criteria

• OpenClover is integrated into build.gradle
• OpenClover appears as named task in list shown via gradlew tasks
• OpenClover runs as part of gradlew check
• Behaviors of other QA tools invoked in the build process are unaffected

Supporting Information

Information about OpenClover: http://openclover.org/

Information about the OpenClove plugin: http://openclover.org/doc/manual/4.2.0/gradle--gradle-clover-plugin.html

Dependencies

Dependents

User Stories #104 #2

[jody]

Why does the "Supporting Information" have a statement about "CheckStyle" and no information about where "here" is?

[shadycloud]

ahh, because I copy/pasted from the CheckStyle ticket. I noticed that OpenClover was the only tool in toolsForIntegration.md that was missing in our backlog. I'll find some better acceptance criteria.