Jamison929611 opened a new pull request, #3875:
URL: https://github.com/apache/iggy/pull/3875

   ## Why
   
   The BDD roadmap tracks client-visible stream CRUD coverage, but there was no 
shared feature exercising the lifecycle across SDKs.
   
   ## What
   
   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 blocking or asynchronous client 
abstractions, and focused runner paths cover normal and coverage executions.
   
   Part of #3609
   
   ## Verification
   
   - `cargo fmt --all -- --check`
   - `cargo clippy -p bdd --features bdd --all-targets -- -D warnings`
   - `cargo test -p bdd --features bdd --no-run`
   - `gradle -p bdd/java --no-daemon spotlessCheck testClasses`
   - Java Cucumber dry run for all five `@stream-crud` scenarios
   - `bash -n scripts/run-bdd-tests.sh`
   
   Full server-backed Rust and Java BDD runs are delegated to Linux CI because 
the Iggy server does not build on Windows.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to