OpenMDAO / OpenMDAO/Aviary

Add interface-level tests to minimize future GASP/FLOPS-based code divergence

Open
#295 1 comment 0 reactions 3 assignees View on GitHub

@ehariton is already working on this.

Since Feb 11, 2026.

epic validation
Dominant language
Python
Stars
287
Forks
140
Avg merge
6d 14h
Merged PRs (30d)
18

Description

Desired capability or behavior.

Create an interface level test at the split between GASP and FLOPS in methods_for_level2 and other places. Have bottom-up tests, start with unit tests and move up the stack to integration tests.

Is your feature request related to a problem? Please describe.

No response

Associated Bug Report

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.