scylladb / scylladb/python-rs-driver
Ensure idempotence of test runs
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6
- Forks
- 7
- Avg merge
- 5d 13h
- Merged PRs (30d)
- 9
Description
📌 We're using hardcoded keyspace names, and we're not dropping them at the end of each test. This may have the following consequences:
- Test runs are not idempotent.
- Tests may interfere with each other when (unintentionally) using same keyspace.
In Rust Driver, we have both solutions:
- Tests drop keyspaces they create, so cleanup is ensured.
- Tests use unique keyspace names, generated from timestamps.
As @Lorak-mmk said, we should do both here as well.
Originally posted by @wprzytula in https://github.com/scylladb-zpp-2025-python-rs-driver/python-rs-driver/pull/102#discussion_r3450329582
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the tests that use hardcoded keyspace names and identify how those keyspaces are created. Compare the Rust Driver approach described in the issue: generate unique names and drop created keyspaces during cleanup. Done means repeated test runs are idempotent and tests do not interfere through shared keyspaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- databases, testing-qa
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100