afa4659292
* New acceptance test tool prototype * Fix transaction filter helper * Address https://github.com/digital-asset/daml/pull/2282#discussion_r308081386 * Address https://github.com/digital-asset/daml/pull/2282#discussion_r308082432 Moreover, creates specific helpers for test DAML code. * Move helpers from session to context Remove a circular dependency between session and context, and limits the usage of implicits. * Run tests with ledgers out of process * Prepare for drop in * Temporary timeout increase * Move bulk of the logic to the test runner * Have a map of tests for CLI integration * Timeout per-test, runner uses context, renaming * Allow usage of time service, integrate semantic tests * Integrate CLI SSL configuration * Integrate failure expectation CLI option * Integrate with failure output verbosity CLI option * Integrate with test listing and picking CLI options * Integrate with timeout scaling CLI option * Integrate with command TTL CLI option * Review CODEOWNERS * Drop previously unimplemented CLI parameters * Expand test todo list to encompass latest additions * Deduplicate some testing infrastructure, swap in new test tool * Remove unused rule * Address https://github.com/digital-asset/daml/pull/2282#discussion_r311045444 * Address https://github.com/digital-asset/daml/pull/2282#discussion_r311051974 * Address https://github.com/digital-asset/daml/pull/2282#discussion_r311035287 * Address https://github.com/digital-asset/daml/pull/2282#discussion_r311055290 * WIP * Make gRPC thread factory spawn non-deamon threads * Remove debug prints, complete divulgence test (missing assertion messages) * Try to detect assertion failure line number * Add Sandbox binary that starts an ephemeral postgres instance This allows us to use the client_server_test bazel macro to run against the sandbox backed by postgres. Fixes #1543 * Add Sandbox binary that starts an ephemeral postgres instance This allows us to use the client_server_test bazel macro to run against the sandbox backed by postgres. Fixes #1543 * Address https://github.com/digital-asset/daml/pull/2282#discussion_r311400695 * Remove TlsConfiguration duplicate, move original to commons * Make assertion more readable Co-Authored-By: Gerolf Seitz <gerolf.seitz@digitalasset.com> * Fix build errors introduced in previous commit - exclude time service tests from reference-v2 - add copyright header to TlsConfiguration * Complete divulgence test and address review comments Restores comments from original divulgence tests and strives to be as close to them as possible. - Address https://github.com/digital-asset/daml/pull/2282#discussion_r311429169 - Address https://github.com/digital-asset/daml/pull/2282#discussion_r311431156 - Address https://github.com/digital-asset/daml/pull/2282#discussion_r311431913 * Delete old divulgence tests * Restore methods to fetch contracts by template identifier * Run conformance tests on in-memory sandbox * Run conformance tests on the persistent sandbox * Remove workflow identifier workaround * New contract keys test (#2452) * Set channel type for LedgerSession * Add ContractKeysIT * Run tests against reference-server v2 * Removed the old ContractKeysIT. However, ... ... I cannot remove ContractKeysChecks completely, because we have another test path for DARs created prior to DAML-LF 1.6, which doesn't have the submitter == maintainer restriction for contract keys. * Use codegen instead of custom code * Add missing copyright headers * Drop sandbox conformance test suite (seems to not work on Windows CI) * Make time simpler * Test tool tests to run only semantic tests * Make CI behave more consistently * Add missing files to run tests on Postrgres * Fix flaky divulgence test, introduce readable identifiers * Increase sandbox conformance tests timeout * Address https://github.com/digital-asset/daml/pull/2282#discussion_r312363246 * Reintroduce test resource extraction * Read semantic tests from the classpath rather than Bazel * Use codegen types for ContractKeys integration test allocateParty returns Primitive.Party and create and exercise also accept Primitive.Party. This way we don't have to keep a String and Primitive.Party representation around. * Bump timeout for sandbox conformance tests * Remove dependency on Bazel runfiles
1.8 KiB
Ledger API Test Tool
Status: ALPHA
This is a standalone command line tool for testing the correctness of DAML ledger implementations.
Development
Running via Bazel
To build and run the tool, use:
bazel run //ledger/ledger-api-test-tool:ledger-api-test-tool
It wraps
SemanticTester.scala
into a standalone command line tool with embedded
//ledger/test-common:SemanticTests.dar.
Running standalone
Run
bazel build //ledger/ledger-api-test-tool:ledger-api-test-tool_deploy.jar
to a "fat" JAR at
bazel-bin/ledger/ledger-api-test-tool/ledger-api-test-tool_deploy.jar which
can be run with:
java -jar bazel-bin/ledger/ledger-api-test-tool/ledger-api-test-tool_deploy.jar
Publishing
The tool is automatically released as part of SDK releases into paths like (note the version string in the url) https://bintray.com/digitalassetsdk/DigitalAssetSDK/sdk-components/100.11.31#files/com%2Fdaml%2Fledger%2Ftesttool
Usage
See Ledger API Test Tool docs for usage docs. Publicly released docs are available at https://docs.daml.com/tools/ledger-api-test-tool/index.html
Connecting over TLS to a DAML Ledger, e.g. the Digital Asset Ledger
NOT IMPLEMENTED, see https://github.com/digital-asset/daml/issues/556 for some extra context.
You might want to use this tool to verify that a deployment of Digital Asset Ledger have been deployed correctly with regards to Ledger API conformance.
By default, Ledger API Test Tool is configured to use an unencrypted connection to the ledger.
To run Ledger API Test Tool against a secured Digital Asset Ledger, configure
TLS certificates using the --pem, --crt, and --cacrt command line
parameters.