Skip to content
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

Revamp regression test infrastructure #1207

Open
charleskawczynski opened this issue Jun 22, 2022 · 0 comments
Open

Revamp regression test infrastructure #1207

charleskawczynski opened this issue Jun 22, 2022 · 0 comments
Assignees
Labels
SDI Software Design Issue

Comments

@charleskawczynski
Copy link
Member

Purpose

The purpose of this SDI is to improve TC's testing infrastructure (i.e., upgrade to how ClimaAtmos' testing infrastructure works).

Cost/Benefits/Risks

The cost is low: users will need to become accustomed to the new workflow, which is only slightly different.

The benefit is that all of our tests will become "first class". Right now, we have two types of tests: "vanilla" tests and "non-vanilla" tests. Our non-vanilla tests only test that the code runs, and no tests are performed regarding the actual output values. So, if someone makes a "refactoring" change that is not actually refactoring, our vanilla tests will catch behavioral changes (i.e., they'll fail) while our non-vanilla "tests" will silently pass.

This means that results for any experimental models, e.g., new closures, can silently change in any PR.

One of the main advantages of applying these changes is that we've already implemented this solution in ClimaAtmos--much of what we did there is portable and we can simply move things over to TC.

People and Personnel

(@ the personnel required/requested to implement the software solution)

Components

The testing infrastructure

Inputs

NCDatasets

Results and deliverables

Regression tests that work like ClimaAtmos

Task Breakdown And Tentative Due Date

We'll need to:

Proposed Delivery Date

I don't know that I have a delivery date, but the whole issue could probably be resolved in ~ 1-2 weeks.

@charleskawczynski charleskawczynski added the SDI Software Design Issue label Jun 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
SDI Software Design Issue
Projects
None yet
Development

No branches or pull requests

3 participants