Test: expand unit coverage for scalar converters in ConverterTest - #999
Open
leehaut wants to merge 1 commit into
Open
Test: expand unit coverage for scalar converters in ConverterTest#999leehaut wants to merge 1 commit into
leehaut wants to merge 1 commit into
Conversation
Signed-off-by: lance <leehaut@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose of the pull request
Improve unit test coverage for individual scalar converter implementations.
ConverterTestpreviously only exercisedFloatNumberConverterwrite conversion;this change turns it into a focused
@Tag(unit)suite covering the commonBoolean / Number / String converters.
What's changed?
ConverterTestas pure unit tests (no Excel I/O / round-trip).supportJavaTypeKey()/supportExcelTypeKey()across 31 converters.Boolean,Integer,Long,Short,Byte,Float,DoubleBigDecimal,BigIntegerString(STRING/BOOLEAN/NUMBER/ERROR)supportKeysProvider) to avoid JUnit@MethodSourcename clashes.No functional changes are included in this PR.