Skip to content

Reduce the number of tests that use computationally expensive cases unnecessarily #779

Description

@johnjasa

Reduce the number of tests that use computationally expensive cases unnecessarily

A few tests (across unit, regression, and integration) are using examples or cases that are unnecessarilyc omputationally expensive.
For example, test_sql_timeseries_to_csv.py uses a case that takes minutes to run, whereas we could use one that runs in seconds while still fully testing the capability the test handles.

Proposed solution

Generally change the cases/examples used in tests, especially for the unit test suite.
It may make sense to add new cases if you can make simpler ones that take less time to test the same capability.
Any test that runs HOPP (esp. with floris) or has an optimal controller unnecessarily would be the lowest-hanging fruits.

Alternatives considered

Additional context

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions