Replies: 2 comments 1 reply
-
There were a few other ideas we had a shell of an idea put into the 1.0 testing plan we built up that I'll drop here as well, we'd need to flesh these ideas out a bit to prioritize them if anyone has any specific ideas on these:
|
Beta Was this translation helpful? Give feedback.
-
I definitely think we want e2e test coverage for upgrade and scale up/down scenarios. Rolling restarts might be good as well. I am not sure about C* config changes. We have unit test coverage for what is supported through k8ssandra. I think that may be sufficient. I don't think we would need to verify anything other than making sure changes are applied to the CassandraDatacenter. That is already done in the unit tests. What would be the goal with testing a missing storage class? I am on the fence for testing size = 0. I tend to think that should be a scenario handled by cass-operator. The install will fail though due to an OpenAPI validation check. See here. |
Beta Was this translation helpful? Give feedback.
-
We've recently built up the capabilities within the project for e2e testing and we should now take advantage of that and continue building out scenarios that are of common/high priority. To focus that effort I'd love to hear what some of those scenarios folks would really like to see covered are and get some sense of why they are important in one way or another.
To get the convo going here's a few ideas that have been sent my way or I'm recalling from various conversations recently:
Beta Was this translation helpful? Give feedback.
All reactions