Original cpp-driver allows user to SET the invalid serial consistency.
Then, the request is sent with an invalid serial consistency, resulting in a server error.
However, rust-driver comes with a type safety in this matter, disallowing
the user to set invalid serial consistency, thus we are not able to mimic this behaviour in cpp-rust-driver.
We need to adjust the integration test, and assert that setting the invalid serial consistency fails with an error.
Changes
Adjusted one test in SerialConsistencyTests suite, and enabled the test suite in CI.
Pre-review checklist
[x] I have split my patch into logically separate commits.
[x] All commit messages clearly explain what they change and why.
[x] PR description sums up the changes and reasons why they should be introduced.
~[ ] I have implemented Rust unit tests for the features/changes introduced.~
[x] I have enabled appropriate tests in .github/workflows/build.yml in gtest_filter.
[x] I have enabled appropriate tests in .github/workflows/cassandra.yml in gtest_filter.
Motivation
Original cpp-driver allows user to SET the invalid serial consistency. Then, the request is sent with an invalid serial consistency, resulting in a server error. However, rust-driver comes with a type safety in this matter, disallowing the user to set invalid serial consistency, thus we are not able to mimic this behaviour in cpp-rust-driver. We need to adjust the integration test, and assert that setting the invalid serial consistency fails with an error.
Changes
Adjusted one test in
SerialConsistencyTestssuite, and enabled the test suite in CI.Pre-review checklist
.github/workflows/build.ymlingtest_filter..github/workflows/cassandra.ymlingtest_filter.