Sometimes, integration tests do need a database, a messaging system etc in order to properly run. This is not trivial especially when it comes to cloud provided services (e.g. amazon relational database service). This is where the Kubernetes Service Catalog would shine.
Explore, the possibility of having arquillian-cube integrate with the service catalog in order to allow provisioning of those services via cube.
Note, this is something that should be usable with or without the kubernetes module of cube.
Now, if we took it one step further and leverage the servicecatalog-connector we could possibly be able to even inject a DataSource, ConnectionFactory and what not directly into our tests.
Sometimes, integration tests do need a database, a messaging system etc in order to properly run. This is not trivial especially when it comes to cloud provided services (e.g. amazon relational database service). This is where the Kubernetes Service Catalog would shine.
Explore, the possibility of having arquillian-cube integrate with the service catalog in order to allow provisioning of those services via cube.
Note, this is something that should be usable with or without the kubernetes module of cube.
Now, if we took it one step further and leverage the servicecatalog-connector we could possibly be able to even inject a DataSource, ConnectionFactory and what not directly into our tests.