24ff908240
* Move initialization of wallet entropy into the key manager * Enable key-manager in ci, add coverage minimum * Add coverage minimum for key manager, add KeyManagerParams, start adding KeyManager test harness * Remove success cases on ADTs, start using Either * fix import * Get test coverage to 90% * Add documentation for key-manager.md, add side bar for key-manager * Fix wallet.md * Make seedPath default to baseDatadir, so we don't have a unique seed for every network. Add more documentation * Address code review * Address code review from Ben * Add missing import * Add more tests for coverage |
||
|---|---|---|
| .. | ||
| src | ||
| README.md | ||
Philosphy of testkit
The high level of of the bitcoin-s testkit is to mimic provide functionality to test 3rd party applications.
There are other examples of these in the Scala ecosystem like the akka-testkit and slick-testkit.
We use this testkit to test bitcoin-s it self. For instance, our BitcoindRpcClient is tested with the functionality provided in the testkit. A quick example of a useful utility method is BitcoindRpcTestUtil.startedBitcoindRpcClient(). This spins up a bitcoind regtest instance on machine and generates 101 blocks on that node. This gives you the abililty to start spending money immediately with that bitcoind node.
We have similar utility methods for eclair.
Property based testing
There is also a robust set of generators available in the org.bitcoins.testkit.gen package. This allows you to integrate property based testing into your library and feel confident about implementing your application specific logic correctly.
You can see examples of us using these generators inside of testkit in our Private Key test cases