Given two fixture building methods (one dependent on the other), returns a single fixture building method where the fixture is the pair of the two.
Given two fixture building methods (one dependent on the other), returns a single fixture building method where the fixture is the pair of the two.
Example:
composeBuilders(createBlockHeaderDAO, createChainHandlerFromBlockHeaderDAO)
Given two fixture building methods (one dependent on the other) and a wrapper for their pair type, returns a single fixture building method where the fixture is wrapper.
Given two fixture building methods (one dependent on the other) and a wrapper for their pair type, returns a single fixture building method where the fixture is wrapper.
Example:
composeBuildersAndWrap( createBitcoind, createChainHandlerWithBitcoindZmq, BitcoindChainHandler.apply)
Given two fixture building methods (one dependent on the other) and a function that processes the result of the builders returning a Future, returns a single fixture building method where the fixture is wrapper.
Given two fixture building methods (one dependent on the other) and a function that processes the result of the builders returning a Future, returns a single fixture building method where the fixture is wrapper.
This method is identical to composeBuildersAndWrap
, except that
the wrapping function returns a Future[C]
instead of a C
Wallet config with data directory set to user temp directory
Wallet config with data directory set to user temp directory
Sets the generator driven tests to perform the given amount of execs
Sets the generator driven tests to perform the given amount of execs
Needed because the default execution context will become overloaded if we do not specify a unique execution context for each suite
Needed because the default execution context will become overloaded if we do not specify a unique execution context for each suite
Property based tests that have been around a long time have a less of a chance failing, so execute them less
Property based tests that have been around a long time have a less of a chance failing, so execute them less
The configuration for property based tests in our testing suite
The configuration for property based tests in our testing suite
http://www.scalatest.org/user_guide/writing_scalacheck_style_properties
Property based tests that are new have a higher chance of failing so execute them more
Property based tests that are new have a higher chance of failing so execute them more
Given functions to build and destroy a fixture, returns a OneArgAsyncTest => FutureOutcome (this version gives the destroy function access to the fixture)
Given functions to build and destroy a fixture, returns a OneArgAsyncTest => FutureOutcome (this version gives the destroy function access to the fixture)
Example:
makeDependentFixture(createBitcoindChainHandler, destroyBitcoindChainHandler)
Given functions to build and destroy a fixture, returns a OneArgAsyncTest => FutureOutcome (this version does not give the destroy function access to the fixture, see makeDependentFixture)
Given functions to build and destroy a fixture, returns a OneArgAsyncTest => FutureOutcome (this version does not give the destroy function access to the fixture, see makeDependentFixture)
Example:
makeFixture(createBlockHeaderDAO, destroyBlockHeaderTable)
This def ensures that shrinks are disabled for all calls to forAll.
This def ensures that shrinks are disabled for all calls to forAll.
If you want to enable shrinking for a specific test, introduce an implicit val into that scope with type Shrink[T] where T is the type of the generator you want to enable shrinking on.
Creates a wallet that is funded with some bitcoin, this wallet is NOT peered with a bitcoind so the funds in the wallet are not tied to an underlying blockchain
Creates a wallet that is funded with some bitcoin, this wallet is NOT peered with a bitcoind so the funds in the wallet are not tied to an underlying blockchain
Fixture for an initialized wallet which produce legacy addresses
Fixture for an initialized wallet which produce legacy addresses
Lets you customize the parameters for the created wallet
Lets you customize the parameters for the created wallet
Fixture for an initialized wallet which produce segwit addresses
Fixture for an initialized wallet which produce segwit addresses
(Since version 3.1.0) The conversionCheckedConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The convertEquivalenceToAToBConversionConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The convertEquivalenceToBToAConversionConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The lowPriorityConversionCheckedConstraint method has been deprecated and will be removed in a future version of ScalaTest. It is no longer needed now that the deprecation period of ConversionCheckedTripleEquals has expired. It will not be replaced.
(Since version 3.1.0) The styleName lifecycle method has been deprecated and will be removed in a future version of ScalaTest with no replacement.