You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our integration test scenarios (see Test/Integration/Scenario) describe interactions with the API or CLI and expectations from these interactions. In practice, most of these scenarios are backend-agnostic and, we should be able to replay most of them for either cardano-http-bridge or jörmungandr.
PR #334 already makes a first step in that direction by moving the Network environment and backend-specific bits up-to the integration main file, leaving the scenarios really just about the interactions with the API or CLI.
Decision
Move the integration framework (DSL & Request) from the http-bridge module to core.
Set up integration tests in jörmungandr and replay all scenarios using jörmungandr as a backend target (while still playing all the scenarios for the bridge).
We'll probably need to adapt the Faucet module as well although a similar approach should be possible with Jörmungandr too.
Acceptance Criteria
Integration tests scenarios must still run for the http-bridge
Integration tests scenarios must run for jörmungandr
Some scenarios that are too backend-specific may be disabled and/or duplicated for their corresponding backend.
Development Plan
I intend to extend the move DSL and Request to the core in order to reuse them both at http-bridge and jormungandr
I intend to deliver faucet scaffolding for jormungandr that will work with small amount of work when tx API is finalized
I intend to make integration tests scenarios passing with jörmungandr
We have a similar setup as the bridge, running test against both the API and the CLI.
We can probably add more tests that are Jörmungandr-specific, since the CLI is a bit different and, there are now two address encoding formats; this is rather out-of-scope for this ticket though I believe and I'd suggest to tackle that as debts or, in a new story.
The text was updated successfully, but these errors were encountered:
Context
Our integration test scenarios (see Test/Integration/Scenario) describe interactions with the API or CLI and expectations from these interactions. In practice, most of these scenarios are backend-agnostic and, we should be able to replay most of them for either
cardano-http-bridge
orjörmungandr
.PR #334 already makes a first step in that direction by moving the
Network
environment and backend-specific bits up-to the integration main file, leaving the scenarios really just about the interactions with the API or CLI.Decision
http-bridge
module tocore
.Faucet
module as well although a similar approach should be possible with Jörmungandr too.Acceptance Criteria
Development Plan
PR
master
master
master
master
master
master
master
master
master
master
master
QA
Integration tests have been ported, adjusted and are running in CI (https://github.com/input-output-hk/cardano-wallet/blob/master/lib/jormungandr/test/integration/Main.hs#L108-L136)
We have a similar setup as the bridge, running test against both the API and the CLI.
We can probably add more tests that are Jörmungandr-specific, since the CLI is a bit different and, there are now two address encoding formats; this is rather out-of-scope for this ticket though I believe and I'd suggest to tackle that as debts or, in a new story.
The text was updated successfully, but these errors were encountered: