Happy path
To test the happy path we are going to use the same sequence of transactions as shown in the Ledger Evolution diagram we saw earlier:
We will use the Corda MockNetwork DSL to generate a sequence of transactions representing the transactions in the diagram:
@Test
fun `check the happy path`() {
val linearId = UniqueIdentifier()
val proposed1 = AgreementState(AgreementStatus.PROPOSED,
alice.party, bob.party, "One bunch of Bananas", Amount(10, Currency.getInstance("GBP")), alice.party, bob.party, linearId = linearId)
val rejected = AgreementState(AgreementStatus.REJECTED,
alice.party, bob.party, "One bunch of Bananas", Amount(10, Currency.getInstance("GBP")), alice.party, bob.party, "Run out of Bananas", bob.party, linearId = linearId)
val proposed2 = AgreementState(AgreementStatus.PROPOSED,
alice.party, bob.party, "One bag of grapes", Amount(8, Currency.getInstance("GBP")), bob.party, alice.party, linearId = linearId)
val agreed = AgreementState(AgreementStatus.AGREED,
alice.party, bob.party, "One bag of grapes", Amount(8, Currency.getInstance("GBP")), bob.party, alice.party, linearId = linearId)
ledgerServices.ledger {
transaction {
command(alice.publicKey, AgreementContract.Commands.Propose())
output(AgreementContract.ID, proposed1)
verifies()
}
transaction {
input(AgreementContract.ID, proposed1)
command(bob.publicKey, AgreementContract.Commands.Reject())
output(AgreementContract.ID, rejected)
verifies()
}
transaction {
input(AgreementContract.ID, rejected)
command(bob.publicKey, AgreementContract.Commands.Repropose())
output(AgreementContract.ID, proposed2)
verifies()
}
transaction {
input(AgreementContract.ID, proposed2)
command(alice.publicKey, AgreementContract.Commands.Agree())
output(AgreementContract.ID, agreed)
verifies()
}
transaction {
input(AgreementContract.ID, agreed)
command(bob.publicKey, AgreementContract.Commands.Complete())
verifies()
}
}
}
This gives us a base line to work off for the non-happy path tests.
Was this page helpful?
Thanks for your feedback!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.
We're sorry this page wasn't helpful. Let us know how we can make it better!
Chat with us
Chat with us on our #docs channel on slack. You can also join a lot of other slack channels there and have access to 1-on-1 communication with members of the R3 team and the online community.
Create an issue
Create a new GitHub issue in this repository - submit technical feedback, draw attention to a potential documentation bug, or share ideas for improvement and general feedback.
Propose documentation improvements directly
Help us to improve the docs by contributing directly. It's simple - just fork this repository and raise a PR of your own - R3's Technical Writers will review it and apply the relevant suggestions.