Unit test cases
Here we list tests on just the operator's core logic that are independent of its deployment or other components in the cluster. We should need to somehow mock PVCs and DBs? Let's get familiar with the Kubebuilder test environment.
Only tests that have to do with the k8s API server or directly parts of the operator's code are in scope here. Specifically, ensuring the functionality of Drupal websites is OUT of scope, since it needs the full environment with all the other components. We'll test that with integration tests in okd4-install.
-
create all objects (apart from route, which is dependent) -
recreate all dependent objects, after they've been deleted -
update of modified objects -
create 2 DrupalSites in the same NS -
no update of modified objects with the admin override annotation -
resources according to QoS class (configmaps, resource limits, replicas) -
[future] changing QoS class