You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a thread to discussing strategies for increasing the testing coverage of the MDTF code. This is in advance of the "beta 3" release, but a broader issue that needs to be addressed.
Specifically, we need:
1. rapid, commit-level or PR testing of
framework installation
code flow of the PODs
checks for broken links
code quality (security, formatting)
documentation generation
2. more through scientific and workflow vetting
tests on other GFDL and NCAR experiments
tests on different model resolutions
tests on different data naming conventions (DRS vs. internal NCAR/GFDL formats)
testing-CIIssues related to testing. (Bugs found via testing should get the "bug" tag instead.)
1 participant
Converted from issue
This discussion was converted from issue #67 on October 25, 2022 15:36.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
This is a thread to discussing strategies for increasing the testing coverage of the MDTF code. This is in advance of the "beta 3" release, but a broader issue that needs to be addressed.
Specifically, we need:
1. rapid, commit-level or PR testing of
2. more through scientific and workflow vetting
Beta Was this translation helpful? Give feedback.
All reactions