Testing CDL code

To test CDL Code we want to maintain and extend the structure we used to map the CDL considerations to the implemented code. We can show this diagrammatically:

The ContractUtils has its own extensive testing, which can be seen in the cdl-example ContractUtilsTests.kt

It is sensible to run some FlowTests early in the Smart Contract development. There are some structures such as MutableLists which do not serialise across Corda Flows; you want to spot these early, not after you have spent weeks working on your smart contract implementation.

The main part of testing concerns testing the AgreementContract. The approach taken in the cdl-example is to define a ‘happy path’ set of tests which represent a set of transactions where everything verifies, then for each type of constraint exhaustively test the conditions which should cause that constraint to fail.