We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The unit test TestParseIdentifier (trunk@59ced546f5227abcbd0b4c8a7d5bcddcb8ba6667) is identical to TestParseBareIdentifier.
TestParseIdentifier
TestParseBareIdentifier
Both call the parseBareIdentifier function, so parseIdentifier isn't directly covered. Seems like a minor typo?
parseBareIdentifier
parseIdentifier
Changing https://github.com/hkolbeck/kdl4j/blob/trunk/src/test/java/dev/hbeck/kdl/parse/TestParseBareIdentifier.java line 46 to call parseIdentifier results in a passing unit test calling the correct function, but should it have a different set of test data?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The unit test
TestParseIdentifier(trunk@59ced546f5227abcbd0b4c8a7d5bcddcb8ba6667) is identical toTestParseBareIdentifier.Both call the
parseBareIdentifierfunction, soparseIdentifierisn't directly covered. Seems like a minor typo?Changing https://github.com/hkolbeck/kdl4j/blob/trunk/src/test/java/dev/hbeck/kdl/parse/TestParseBareIdentifier.java line 46 to call
parseIdentifierresults in a passing unit test calling the correct function, but should it have a different set of test data?The text was updated successfully, but these errors were encountered: