[RPC-Spec-V2] Add tests for transactionWatch_unstable_submitAndWatch
#3083
Comments
github-merge-queue bot
pushed a commit
that referenced
this issue
Apr 9, 2024
This PR ensures that the transaction API generates an `Invalid` events for transaction bytes that fail to decode. The spec mentioned the `Invalid` event at the jsonrpc error section, however this spec PR makes things clearer: - paritytech/json-rpc-interface-spec#146 While at it have discovered an inconsistency with the generated events. The drop event from the transaction pool was incorrectly mapped to the `invalid` event. Added tests for the API stabilize the API soon: - paritytech/json-rpc-interface-spec#144 Closes: #3083 cc @paritytech/subxt-team --------- Signed-off-by: Alexandru Vasile <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The #3079 introduces a test harness for the transaction class.
Extend the tests with various scenarios to validate the behavior of
transactionWatch_unstable_submitAndWatch.The status of the transaction should be correlated with the state of the transaction pool.
A few scenarios ideas:
ChainEvent::FinalizedReady,InBlock,Finalizedwith events driven from the transaction poolcc @paritytech/subxt-team
The text was updated successfully, but these errors were encountered: