Skip to content

Registry API: no API conformance tests; server tests only verify locally-available code. #611

@timburks

Description

@timburks

We currently lack a way to verify that a running server properly conforms to the Registry API specification as described by protos and the unit tests in /server/registry. This makes it difficult to verify hosted instances and alternate implementations that include internal mocks of the Registry API.

How can we avoid redundant test-writing but also address this need?

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions