Options for controlling coverage checking requirements

• checkCoverage tells you whether or not to run the coverage checks at all.
• `endpointCoverageEq instance endpointName` tells us what percentage of tests are required to include a call to the endpoint endpointName in the contract at `instance`.
• coverIndex is the coverage index obtained from the CompiledCodeIn of the validator.

Used to freeze other wallets when checking a NoLockedFundsProof.

`delay n` delays emulator execution by n slots

A whitelist entry tells you what final log entry prefixes are acceptable for a given error

A "proof" that you can always recover the funds locked by a contract. The first component is a strategy that from any state of the contract can get all the funds out. The second component is a strategy for each wallet that from the same state, shows how that wallet can recover the same (or bigger) amount as using the first strategy, without relying on any actions being taken by the other wallets.

For instance, in a two player game where each player bets some amount of funds and the winner gets the pot, there needs to be a mechanism for the players to recover their bid if the other player simply walks away (perhaps after realising the game is lost). If not, it won't be possible to construct a NoLockedFundsProof that works in a state where both players need to move before any funds can be collected.

Default coverage checking options are: * not to check coverage * set the requriements for every endpoint to 20% and * not to cover any source locations in the validator scripts.

Default check options that include a large amount of Ada in the initial distributions to avoid having to write ContractModels that keep track of balances.

Run QuickCheck on a property that tracks coverage and print its coverage report.

Check a threat model on all transactions produced by the given actions.

Check a threat model on all transactions produced by the given actions.

Run a Actions in the emulator and check that the model and the emulator agree on the final wallet balance changes. Equivalent to

propRunActions_ hs actions = propRunActions hs (const $ pure True) actions

Run a Actions in the emulator and check that the model and the emulator agree on the final wallet balance changes, and that the given TracePredicate holds at the end. Equivalent to:

propRunActions = propRunActionsWithOptions defaultCheckOptionsContractModel defaultCoverageOptions

The default skeleton of a NoLockedFundsProof - doesn't permit any overhead or error margin.

Check a NoLockedFundsProof. Each test will generate an arbitrary sequence of actions (anyActions_) and ask the nlfpMainStrategy to recover all funds locked by the contract after performing those actions. This results in some distribution of the contract funds to the wallets, and the test then asks each nlfpWalletStrategy to show how to recover their allotment of funds without any assistance from the other wallets (assuming the main strategy did not execute). When executing wallet strategies, the off-chain instances for other wallets are killed and their private keys are deleted from the emulator state.

Check that the last entry in a log is accepted by a whitelist entry

Check that a whitelist does not accept any partial functions

Check that running a contract model does not result in validation failures that are not accepted by the whitelist.

Check that running a contract model does not result in validation failures that are not accepted by the whitelist.