Tests never exercise @{baseVersion}@ used in DEFAULT constants
- Dominant language
- Java
- Stars
- 2
- Forks
- 7
- Avg merge
- 11h 11m
- Merged PRs (30d)
- 4
Description
## Description
Both `DEFAULT_FILE_NAME_MAPPING` and `DEFAULT_FILE_NAME_MAPPING_CLASSIFIER` use `@{baseVersion}@` in their expressions (`MappingUtils.java:72,78`). However, every test in `MappingUtilsTest.java` uses `@{version}@` in its expressions instead.
## Risk
There is no test coverage verifying that `@{baseVersion}@` resolves correctly, or documenting the behavioral difference between `baseVersion` and `version`.
## Suggestion
Add at least one test that evaluates a mapping expression containing `@{baseVersion}@` to ensure it resolves as expected.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading MappingUtils.java around lines 72 and 78, then inspect MappingUtilsTest.java and run its existing tests. Add a focused test that evaluates an expression containing @{baseVersion}@ and confirms it resolves as expected; done means the test passes and covers the previously untested default mapping behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100