Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integration test senarios #187

Open
vazirim opened this issue Aug 28, 2020 · 0 comments
Open

Integration test senarios #187

vazirim opened this issue Aug 28, 2020 · 0 comments

Comments

@vazirim
Copy link
Member

vazirim commented Aug 28, 2020

  • Have a representation of all the services cares about (Mongodb, Redis, Postgres, Elastic search, Cloudant, keyprotect, COS, Event streams).
  • Create a translator service, delete it on Bluemix, make sure it comes back after a couple of minutes
  • Create a Binding, delete the credentials on Bluemix, make sure it comes back after a couple of minutes
  • Create a Binding, delete the secret on Kube, and check the secret comes back with the right content
  • Create a Cloudant with 2 credentials, check that only one Cloudant gets created
  • Create a service Alias where the service pre-exists and check that it gets created ok
  • Create a service Alias where there are 2 pre-existing services with the same name and check that it fails
  • Create a service Alias where there are 2 pre-existing services but the service CR also contains a CRN annotation, and check it succeeds
  • Create a service Alias where the service does not exist and check that its status gets updated accordingly (not online). Then create the service on Bluemix and check that the service becomes online
  • Create a binding Alias where the credentials exists and check that it gets created ok
  • Create a binding Alias where the credentials don't exist and check that it doesn't succeed. Then create the credentials on Bluemix and check that binding CR becomes online
  • Check that the status.instanceID field of a created service shows the correct CRN for a couple of successfully created services
  • Create a service, immediately delete it, see if it's gone without errors
  • Create a service, wait 10secs, delete it, see if it's gone
  • Create a service, wait 1mn, delete it, see if it's gone
  • Apply the creation of a service 10 times, make sure it doesn't get created more than once
  • Create a service, immediately followed by an apply with a change, immediately followed by delete, make sure it's gone
  • Create a service, delete it on Bluemix, then delete the CR, make sure the CR is deleted
  • Create a service, then change the CR, apply the CR again, make sure the CR is restored to its original form (immutability)
  • Create a service with tags field in the CR, check the tags get created on the service in Bluemix
  • Create a COS with context: region: global, with binding that passes parameters (see cos.yaml). Check that they get created successfully
  • Create a service with parameters that have different types (see elastic.yaml)
  • Create a binding with a role field and check that it gets created successfully
  • Create a service with an externalName field and check the created name is that
  • Create a service with the wrong plan name and check that the error message is appropriate
  • Create a service with the wrong serviceClass name and check that the error message is appropriate
  • Create a service with a metadata.namespace field and check that the controller picks up the correct secret and config of that namespace
  • Test the management namespace
  • Create a service in a different resourcegroup than the default one and check that it gets created correctly
  • Create a service with some tags, update the tags and apply the CR, check that the service on Bluemix has updated tags
  • Create a service with some parameters, update the parameters and apply the CR, check that the service on Bluemix has updated params
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant