test(bdd): add stream CRUD coverage for Rust and Java - #3875
Conversation
|
The pre-merge and PR title workflows are currently waiting for first-time contributor approval. Could a maintainer approve the workflow runs when convenient? The focused Rust and Java compile, formatting, lint, and Cucumber dry-run checks pass locally. |
There was a problem hiding this comment.
some small issue.
One thing worth noting is that we don't have the logic to clean up the stream/topic/user.... we created in the process (not introduced by this PR)
P.S. Please make sure to use the PR template for your description. it's a huge help!
|
Updated the PR description to the current template. Resource cleanup is a pre-existing cross-feature gap, so it remains outside this focused stream CRUD coverage change. |
|
It might be a bit late to bring this up, but I double-checked the Java BDD tests and it seems that each This probably warrants confirmation from someone more familiar with the Java SDK. Except that, LGTM |
|
Java code LGTM. Rust as well. |
9bc89c2 to
0b2c24b
Compare
|
Hi maintainers, I've updated the branch with the latest target branch. The previous approvals were automatically dismissed after the update, and the latest checks are passing. Could you please re-approve this PR when you have a chance? Thanks! |
Add shared client-visible scenarios for creating, retrieving, listing, updating, and deleting streams. Wire the Rust and Java implementations into focused and coverage BDD runs.
7de20d9 to
fe5b9b9
Compare
|
Updated the branch with the latest |
Which issue does this PR address?
Part of #3609
Rationale
The BDD roadmap tracks client-visible stream CRUD coverage, but there was no shared feature exercising the lifecycle across SDKs.
What changed?
This adds five independent scenarios for creating a stream, retrieving it by numeric ID, finding it in the stream list, renaming it, and deleting it. Rust and Java step definitions use their existing client abstractions, and focused runner paths cover normal and coverage executions.
The review follow-up extracts shared Rust step helpers and centralizes unsupported-SDK handling in the BDD runner.
Local Execution
cargo fmt --all -- --checkcargo clippy -p bdd --features bdd --all-targets -- -D warningscargo test -p bdd --features bdd --no-rungradle --no-daemon spotlessCheck testClassesinbdd/javagit diff --checkAI Usage