Skip to content

Accuracy benchmarks and official QA process? #17

@benhalpern

Description

@benhalpern

I don't think this is an immediate concern, but once there is some momentum in the community I think it could make sense to have an official process and recommendation for verifying improvements and regressions?

I'm thinking something along the lines

  1. Automated testing against a static stash of images with known outcomes
  2. Manual QA testing checklist instructions for IRL swing testing accompanied by non-interfering third-party LMs
  3. Automated performance benchmarks

I imagine this could create a powerful feedback loop for community QA contribution if the process is laid out in an easy-to-follow formula.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    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