Expectations for Developers

Testing Expectations

• Run the full RT suite, preferably on Ursa, Hercules, or Derecho (unless changes are specific to a different machine):

  ./rt.sh -a <account>
  

  Developers often choose to add the -e or -r options, too, to expedite testing:

  ./rt.sh -a <account> -e
  

• Commit the updated test_changes.list file.
• Push the log file (RegressionTest_<machine>.log). In the case of baseline changes, this log file will show failures, but this is fine as long as the failures are reasonable (e.g., a comparison failure because a test has baseline updates).
• Exceptions: Regression testing is not required for text-only changes, such as documentation updates, or for updates to the CI, which do not touch the model code.

Review Expectations

• Before we can schedule a PR for testing, all subcomponent PRs need to be approved.