As a developer I'd like to be confident my tests can detect refactori

Some additional comments from <a class="user-mention notranslate" data-hovercard-type=

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Fixed by <a class="issue-link js-issue-link" data-error-text="Failed to load title" da

Increase code coverage (1) about waggle-dance HOT 3 CLOSED

expediagroup commented on May 18, 2024

Increase code coverage (1)

from waggle-dance.

Comments (3)

massdosage commented on May 18, 2024

Some additional comments from @ddcprg received via e-mail:

The initial list of classes which can be added/extended (or removed?) to improve coverage:
GraphiteConfiguration
WaggleDanceConfiguration
YamlStorageConfiguration
CommonVFSResource
Replace tunneling classes with the ones in common-ssh -> this should help to bump the coverage
MonitoringConfiguration -> probably needs to be a SpringTest
TunnelingMetaStoreClientFactory -> there are untested branches
FederatedHMSHandler -> seems can be 100% tested, depends on how much time we want to spend on this, 100% coverage here may be important
FederatedHMSHandlerFactory -> there are untested branches
The first 3 are just configuration objects which I think should be tested for validations and would help to understand the configuration details of WD.

Anything else not on the list is probably better to be covered with integration test since unit test would be hard to figure out. I think we already have some and the framework may not be properly reporting coverage for those.

from waggle-dance.