Skip to content

Integration test standardization #6

@fordN

Description

@fordN

Much of the integration testing code is repeated for every loader. There seems to be a clear opportunity to avoid the often repeated code while also bringing benefits to testability. If we have a more generalized integration testing setup that each loader can use with points of customization for the loader implementations we may also be able to add a CI step that ensures all of the integration tests are actually implemented for a new loader and are passing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions