Skip to content

Continuous Validation Smoke Test #11

@pastorep

Description

@pastorep

To ensure no future merge or Python library version update causes any regression, we should have a basic smoke test to perform the following:

  • Create two small subsets S1 and S2 of dataset
  • Train a model on S1
  • Test the model on S2
  • Cache the test score and compare to those of previous runs. Ensure scores are within rough margin of error
    ** To begin, fine to compare against hard-coded metrics

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