Package-level declarations
Types
Internal API to enable testing of the network map service and node registration process using the internal driver.
Represents a completely custom CorDapp comprising of resources taken from packages on the existing classpath, even including individual disparate classes. The CorDapp metadata that's present in the MANIFEST can also be tailored.
Only used for testing the notary communication path. Can be configured to act as a Raft (singular identity), or a BFT (composite key identity) notary service.
An implementation of Message for in memory messaging by the test MockNodeMessagingService.
A class which provides an implementation of KeyManagementService which is used in MockServices
A mock implementation of WritablePublicKeyToOwningIdentityCache that stores all key mappings in memory. Used in testing scenarios that do not require database access.
A class which provides an implementation of WritableTransactionStorage which is used in MockServices
Keeps track of how many nodes each node sees and gates nodes from completing their startNode CordaFuture until all current nodes see everyone.
An out-of-process RPC user that connects to an RPC server and issues random RPCs with random arguments.
Implementation of the public TestCordapp API.
Represent network management services, network map and doorman, running on the same URL
Represent network management services, network map and doorman, running on different URLs
Extends the public TestCordapp API with internal extensions for use within the testing framework and for internal testing of the platform.
Properties
Custom CorDapp containing the contents of the net.corda.testing.contracts
package, i.e. the dummy contracts. This is not a real CorDapp in the way that FINANCE_CONTRACTS_CORDAPP and FINANCE_WORKFLOWS_CORDAPP are.
Reference to the finance-contracts CorDapp in this repo. The metadata is taken directly from finance/contracts/build.gradle, including the fact that the jar is signed. If you need an unsigned jar then use cordappWithPackages("net.corda.finance.contracts")
.
Reference to the finance-workflows CorDapp in this repo. The metadata is taken directly from finance/workflows/build.gradle, including the fact that the jar is signed. If you need an unsigned jar then use cordappWithPackages("net.corda.finance.flows")
.
Functions
Create a custom CorDapp which contains just the given classes.
Create a custom CorDapp which contains all the classes and resoures located in the given packages. The CorDapp's metadata will be the default values as defined in the CustomCordapp c'tor. Use the copy
to change them. This means the metadata will not be the one defined in the original CorDapp(s) that the given packages may represent. If this is not what you want then use findCordapp instead.
Creates data source configuration for in memory H2 as it would be specified in reference.conf 'datasource' snippet.
Reads database and dataSource configuration from a file denoted by 'databaseProvider' system property, overwritten by system properties and defaults to H2 in memory db.
Create a custom CorDapp which just contains the enclosed classes of the receiver class.
Find the single CorDapp jar on the current classpath which contains the given package. This is a convenience method for TestCordapp.findCordapp but returns the internal ScanPackageTestCordapp.
This is a helper method to allow extending of the DSL, along the lines of interface SomeOtherExposedDSLInterface : DriverDSL interface SomeOtherInternalDSLInterface : InternalDriverDSL, SomeOtherExposedDSLInterface class SomeOtherDSL(val driverDSL : DriverDSLImpl) : InternalDriverDSL by driverDSL, SomeOtherInternalDSLInterface
Creates data source configuration for in memory H2 as it would be specified in reference.conf 'datasource' snippet.
Make properties appropriate for creating a DataSource for unit tests. Defaults configuration of in-memory H2 instance. If 'databaseProvider' system property is set then creates a config from the relevant config file is present in resources folder (used to parametrize test to run against a remote database). Properties retrieval can be parameterized by configSupplier and/or fallBackConfigSupplier methods which are run with nodeName and nodeNameExtension parameters.
Make properties appropriate for creating a Database for unit tests.
Creates data source configuration for on disk H2 as it would be specified in reference.conf 'datasource' snippet.
Should only be used by Driver and MockNode.