Add system test for doxygen comments between metadata hooks and CCPP entry point (subroutine)#429
Merged
climbfuji merged 1 commit intoJan 17, 2022
Conversation
… hooks and subroutine
gold2718
approved these changes
Jan 17, 2022
Collaborator
gold2718
left a comment
gold2718
left a comment
There was a problem hiding this comment.
Good test to have, thanks.
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
2 participants
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.
Add system test for doxygen comments between metadata hooks and CCPP entry point (subroutine) to make sure various doxygen comments and blank lines are parsed correctly/ignored between CCPP metadata hooks and the Fortran subroutines.
Issue #369 reports that certain doxygen comments between the metadata hooks and the subroutines are "not parsed correctly" (i.e. are not ignored). I was going to fix this problem and found that the current
capgenmetadata parser can handle those cases just fine. I added a CCPP entry point to cover these tests.User interface changes?: No
"Fixes #369"
Testing:
test removed: None
unit tests: None
system tests: Add one system test to cover blank lines and doxygen comments between metadata hooks and subroutines; note:
test/run_tests.shpasses.manual testing: None