catalogtest

Documentation

Index

• func PublishCatalogV1Alpha1IntegrationTestData(t *testing.T, client pbresource.ResourceServiceClient)
• func RunCatalogV1Alpha1IntegrationTest(t *testing.T, client pbresource.ResourceServiceClient)
• func VerifyCatalogV1Alpha1IntegrationTestResults(t *testing.T, client pbresource.ResourceServiceClient)

Functions

func PublishCatalogV1Alpha1IntegrationTestData

func PublishCatalogV1Alpha1IntegrationTestData(t *testing.T, client pbresource.ResourceServiceClient)

PublishCatalogV1Alpha1IntegrationTestData will perform a whole bunch of resource writes for Service, ServiceEndpoints, Workload, Node and HealthStatus objects

func RunCatalogV1Alpha1IntegrationTest

func RunCatalogV1Alpha1IntegrationTest(t *testing.T, client pbresource.ResourceServiceClient)

RunCatalogV1Alpha1IntegrationTest will push up a bunch of catalog related data and then verify that all the expected reconciliations happened correctly. This test is intended to exercise a large swathe of behavior of the overall catalog package. Besides just controller reconciliation behavior, the intent is also to verify that integrations with the resource service are also working (i.e. the various validation, mutation and ACL hooks get invoked and are working properly)

This test specifically is not doing any sort of lifecycle related tests to ensure that modification to values results in re-reconciliation as expected. Instead there is another RunCatalogIntegrationTestLifeCycle function that can be used for those purposes. The two are distinct so that the data being published and the assertions made against the system can be reused in upgrade tests.

func VerifyCatalogV1Alpha1IntegrationTestResults

func VerifyCatalogV1Alpha1IntegrationTestResults(t *testing.T, client pbresource.ResourceServiceClient)