Alex

Most recent commit provides visibility on how very basic test structure might look like. One more thing to add is message validation option on consumption via externally pluggable validator.

@bharathv , updated to fit simplification. Will continue on Monday to debug and polish. Right now there is strange count mismatch happening ``` [INFO:2024-07-12 22:09:04,105]: RunnerClient: rptest.transactions.stream_verifier_test.StreamVerifierTest.test_streaming_upgrade: Data: None test_id:...

Sample test runs using EC2 ``` test_id: rptest.transactions.stream_verifier_test.StreamVerifierTest.test_simple_produce_consume_txn_with_add_node status: PASS run time: 2 minutes 21.611 seconds --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- test_id: rptest.transactions.stream_verifier_test.StreamVerifierTest.test_simple_produce_consume_txn_with_add_node status: PASS run time: 2 minutes 41.324 seconds --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- test_id: rptest.transactions.stream_verifier_test.StreamVerifierTest.test_simple_produce_consume_txn_with_add_node...

@bharathv, yes, I keep forgetting that CDT runs in docker and there should be different set of timings

/cdt release rp_version=build skip-units dt-repeat=20 tests/rptest/transactions/stream_verifier_test.py

/cdt release rp_version=build skip-units dt-repeat=20 tests/rptest/transactions/stream_verifier_test.py

/ci-repeat 1

/ci-repeat 1

/ci-repeat 1

/ci-repeat 1