[UserStory] Re-establish test coverage metrics assessment in build

[ghost]

User Story

Essential components

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

Story

As a Maintainer
I want a working test coverage evaluation as part of the build process
so that measures of the adequacy of tests for the code base is evaluated.

Acceptance Criteria

• Test coverage metric evaluation is available in the automated build process that measures the amount of coverage the tests have over source code.

Scenario 1
Given ant coverage command has been executed,
when viewing the associated report
then accurate test coverage evaluation is displayed.

Supporting Information

Test coverage is no longer evaluated. This appears to be a consequence of changes in test classes made to migrate from JUnit 5 Vintage to JUnit 5 Jupiter resulting in the Jacoco tool evaluation no longer working as intended.

Dependencies

Depends On

Dependents

[jody]

"contributor" is not one of the specified stakeholder types in Vision and Stakeholders.

The story rationale uses an undefined term, "test range".

Acceptance criterion Scenario 1 has vague specification: "when reports html file is opened".

[ghost]

I've updated to maintainer, removed the undefined term, and included more detail in acceptance criteria and scenario 1.

[jody]

Thanks! This is a relatively high priority issue!!

(I made a few wording updates.)