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

K8SSAND-1411 ⁃ Tests after merging should check e2e against all supported Cassandra types #300

Closed
burmanm opened this issue Mar 17, 2022 · 2 comments
Labels
done Issues in the state 'done' enhancement New feature or request

Comments

@burmanm
Copy link
Contributor

burmanm commented Mar 17, 2022

What is missing?
Our e2e tests are run against 3.11.x / 4.0.x / dse, depending a bit on the test. We should modify this behavior to verify that all versions work for every test. However, this consumes too much time to do in each PR, so we should keep the PR tests targetting one version, such as 4.0.3 and then only smoke test against other versions.

When merged to main however, we should run the tests against all known versions (with ability to skip the test if the feature is not supported, such as FQL vs 3.11.x / DSE, or DSE features in OSS versions).

Why do we need it?
We might miss a bug (and have) that only affects certain versions. Occasionally Cassandra isn't backwards compatible.

Environment

  • Cass Operator version:

    Insert image tag or Git SHA here

    **Anything else we need to know?**:

┆Issue is synchronized with this Jira Task by Unito
┆friendlyId: K8SSAND-1411
┆priority: Medium

@burmanm burmanm added the enhancement New feature or request label Mar 17, 2022
@sync-by-unito sync-by-unito bot changed the title Tests after merging should check e2e against all supported Cassandra types K8SSAND-1411 ⁃ Tests after merging should check e2e against all supported Cassandra types Apr 4, 2022
@burmanm
Copy link
Contributor Author

burmanm commented Jul 26, 2022

This requires refactoring, probably worth doing with #291

@adejanovski adejanovski moved this to Ready in K8ssandra Nov 8, 2022
@adejanovski adejanovski moved this from Ready to Product Backlog in K8ssandra Nov 16, 2022
@burmanm
Copy link
Contributor Author

burmanm commented Feb 3, 2023

This is done

@burmanm burmanm closed this as completed Feb 3, 2023
@github-project-automation github-project-automation bot moved this from Product Backlog to Done in K8ssandra Feb 3, 2023
@adejanovski adejanovski added the done Issues in the state 'done' label Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
done Issues in the state 'done' enhancement New feature or request
Projects
No open projects
Archived in project
Development

No branches or pull requests

2 participants