-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
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
Addition of an example unit test for users to learn from #581
Addition of an example unit test for users to learn from #581
Conversation
…feature/unit_test_example Conflicts: sorc/chgres_cube.fd/grib2_util.F90
…feature/unit_test_example
…aReames-NOAA/UFS_UTILS into feature/unit_test_example
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't know if github notified you of my minor comment.
@LarissaReames-NOAA Let's close out this PR next. Then I will finish my review of #572 next week (I promise). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LarissaReames-NOAA When I click on 'files changes', it shows your surface regridding changes as not part of 'develop' (and the GNU compiler changes are not in 'develop' either). Check how you did your merge from 'develop' to your branch.
1eb06f2
to
cee9177
Compare
Fixed. |
DESCRIPTION OF CHANGES:
Users who are new to unit tests were frequently asking for assistance on how to get started. We decided to add in both instructions on how to do this, and to provide a very simple, well-commented unit test for users to learn from and modify.
TESTS CONDUCTED:
A new unit tests was created and it passes. All system tests pass. Baseline updates not necessary.
DEPENDENCIES:
N/A
DOCUMENTATION:
Added text to the README file in the tests directory to point users towards the new unit test.
ISSUE:
Addresses Issue #573.