Skip to content

(rough sketch dumps) Follow ups from catalogd-integration #187

Closed
@anik120

Description

@anik120
  • Set up e2e infrastructure for catalogd and operator controller:
  • Devise action plan for what's best tested where, in what format (e2e vs unit).
  • For any test that requires access to images hosted in an image registry, set up test suite to configure a local registry and use that registry for tests instead of reaching out to remote registry.
  • For operator installation test, build a catalog with minimal set of operator/s, and use that instead of quay.io/operatorhubio/catalog:latest
  • Review operator-controller e2e test suite:
  • Structure tests to take advantage of ginkgo's DAG test path creation feature instead of laying all tests in a singe "It" block.
  • (optionally)Eventually blocks can return error instead of taking in Gomega object in it's function signature.
  • Clean up "properties' values must be json objects" expectations in variable source implementation, more details here

  • Move catalogd resources get/watch verbs for operator-controller closer to where they're needed (entitysource implementation). More details here

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