plutus-e2e-tests

End-to-end tests using cardano-testnet to configure and start a local Cardano testnet and cardano-api to build transactions and query ledger state. These tests focus on functionality involving plutus scripts.

Status

This framework is still in early stages of development with only a handful of tests covering:

• Using plutus builtin functions verifySchnorrSecp256k1Signature and verifyEcdsaSecp256k1Signature in different protocol versions with different expected outcomes (success or particular errors).
• Spending funds locked at script using reference script, reference inputs and providing datum as witness in txbody.
• Minting tokens using reference script and providing script witness in txbody.

It is also possible to run these tests on a public testnet, see preconditions:

• Have a directory containing at least these two directories:
  • "utxo-keys" containing "test.skey" and "test.vkey" files. These must both be text envelope PaymentKey format, currently no support for PaymentExtendedKey.
  • "ipc" containing the active node.socket
• Cardano node is fully synced on a public network (e.g. preview testnet)
• There is at least one ada-only UTxO at the test account. Each test will spend a few ada so make sure there's enough funds.
• Modify the test options passed to each test to be run from TestnetOptions to LocalNodeOptions. E.g. swap testnetOptionsBabbage8 for localNodeOptionsPreview.
• Ensure the LocalNodeOption's localEnvDir points to the directory containing your keys ("utxo-keys") and node socket ("ipc").

There are plans to add the following features:

• Shared instance of cardano-testnet for all tests targeting a common protocol version, e.g. Babbage PV8. This should make overall execution time shorter.
• Test reporting, e.g. tasty-html or Allure.
• Nightly CI test execution.