-
Notifications
You must be signed in to change notification settings - Fork 26
Feature #2360 Contributor's Guide - MET unit tests #3121
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
Conversation
…de and add scripts to help handle unit test input data for use in automated tests
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.
Thanks for making these changes George. I proposed some edits to the documentation. I note that I have not actually tested the scripts to confirm that they work as expected, but plan to rely on the testing you've already performed.
Please accept/reject my proposed edits as you see fit and re-request my review.
Co-authored-by: John Halley Gotway <johnhg@ucar.edu>
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.
I read through the updates and confirmed that the formatting is rendering well on RTD. I approve. Thanks for all your work on this.
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.
This is great, @georgemccabe. Thank you for all of your work on this! I made two suggestions.
Co-authored-by: Julie Prestopnik <jpresto@ucar.edu>
1662123
and add scripts to help handle unit test input data for use in automated tests
Expected Differences
Do these changes introduce new tools, command line arguments, or configuration file options? [No]
If yes, please describe:
Do these changes modify the structure of existing or add new output data types (e.g. statistic line types or NetCDF variables)? [No]
If yes, please describe:
Pull Request Testing
Ran scripts on mohawk to ensure they work as expected: Created directory for v12.1 and added data needed for #2794
Do these changes include sufficient documentation updates, ensuring that no errors or warnings exist in the build of the documentation? [Yes]
Do these changes include sufficient testing updates? [Yes]
Will this PR result in changes to the MET test suite? [No]
If yes, describe the new output and/or changes to the existing output:
Will this PR result in changes to existing METplus Use Cases? [No]
If yes, create a new Update Truth METplus issue to describe them.
Do these changes introduce new SonarQube findings? [No]
If yes, please describe:
Please complete this pull request review by 4/4/2025.
Pull Request Checklist
See the METplus Workflow for details.
Select: Reviewer(s) and Development issue
Select: Milestone as the version that will include these changes
Select: METplus-X.Y Support project for bugfix releases or MET-X.Y Development project for the next coordinated release