Uploaded image for project: 'Clair'
  1. Clair
  2. CLAIRDEV-182

Clair testing: An epic to hold the issues relating to testing clair

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • results, tooling
    • None
    • Clair/claircore testing
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • 100% To Do, 0% In Progress, 0% Done

      Clair's list of dependent applications seems to be increasing and it's hard for Clair maintainers to test the performance implications and the veracity of the results by hand (as is currently the case).

      To negate future headaches it is important to invest time and effort into developing frameworks for testing:

      • Load testing: How the code performs under load?
      • Acceptance testing: How accurate are the results based expected outcomes?

      These tests should be continually running based on a (TBD) schedule, and should alert the maintainers on failure.

              Unassigned Unassigned
              jcroslan@redhat.com Joseph Crosland
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: