2017-01-28 02:54:25 +01:00
|
|
|
// Copyright (c) 2016-2017 The btcsuite developers
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
// Use of this source code is governed by an ISC
|
|
|
|
// license that can be found in the LICENSE file.
|
|
|
|
|
|
|
|
package rpctest
|
|
|
|
|
|
|
|
import (
|
|
|
|
"fmt"
|
|
|
|
"io/ioutil"
|
|
|
|
"net"
|
|
|
|
"os"
|
|
|
|
"path/filepath"
|
|
|
|
"strconv"
|
|
|
|
"sync"
|
|
|
|
"testing"
|
|
|
|
"time"
|
|
|
|
|
|
|
|
"github.com/btcsuite/btcd/chaincfg"
|
|
|
|
"github.com/btcsuite/btcd/chaincfg/chainhash"
|
|
|
|
"github.com/btcsuite/btcd/wire"
|
|
|
|
"github.com/btcsuite/btcrpcclient"
|
|
|
|
"github.com/btcsuite/btcutil"
|
|
|
|
)
|
|
|
|
|
2016-09-20 23:09:48 +02:00
|
|
|
const (
|
|
|
|
// These constants define the minimum and maximum p2p and rpc port
|
|
|
|
// numbers used by a test harness. The min port is inclusive while the
|
|
|
|
// max port is exclusive.
|
|
|
|
minPeerPort = 10000
|
|
|
|
maxPeerPort = 35000
|
|
|
|
minRPCPort = maxPeerPort
|
|
|
|
maxRPCPort = 60000
|
2016-08-29 00:52:27 +02:00
|
|
|
|
|
|
|
// BlockVersion is the default block version used when generating
|
|
|
|
// blocks.
|
|
|
|
BlockVersion = 4
|
2016-09-20 23:09:48 +02:00
|
|
|
)
|
|
|
|
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
var (
|
|
|
|
// current number of active test nodes.
|
|
|
|
numTestInstances = 0
|
|
|
|
|
2016-09-20 23:09:48 +02:00
|
|
|
// processID is the process ID of the current running process. It is
|
|
|
|
// used to calculate ports based upon it when launching an rpc
|
|
|
|
// harnesses. The intent is to allow multiple process to run in
|
|
|
|
// parallel without port collisions.
|
|
|
|
//
|
|
|
|
// It should be noted however that there is still some small probability
|
|
|
|
// that there will be port collisions either due to other processes
|
|
|
|
// running or simply due to the stars aligning on the process IDs.
|
2016-09-22 06:14:51 +02:00
|
|
|
processID = os.Getpid()
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
|
|
|
|
// testInstances is a private package-level slice used to keep track of
|
|
|
|
// all active test harnesses. This global can be used to perform
|
|
|
|
// various "joins", shutdown several active harnesses after a test,
|
|
|
|
// etc.
|
|
|
|
testInstances = make(map[string]*Harness)
|
|
|
|
|
|
|
|
// Used to protest concurrent access to above declared variables.
|
|
|
|
harnessStateMtx sync.RWMutex
|
|
|
|
)
|
|
|
|
|
|
|
|
// HarnessTestCase represents a test-case which utilizes an instance of the
|
|
|
|
// Harness to exercise functionality.
|
|
|
|
type HarnessTestCase func(r *Harness, t *testing.T)
|
|
|
|
|
|
|
|
// Harness fully encapsulates an active btcd process to provide a unified
|
|
|
|
// platform for creating rpc driven integration tests involving btcd. The
|
|
|
|
// active btcd node will typically be run in simnet mode in order to allow for
|
|
|
|
// easy generation of test blockchains. The active btcd process is fully
|
|
|
|
// managed by Harness, which handles the necessary initialization, and teardown
|
|
|
|
// of the process along with any temporary directories created as a result.
|
|
|
|
// Multiple Harness instances may be run concurrently, in order to allow for
|
|
|
|
// testing complex scenarios involving multiple nodes. The harness also
|
|
|
|
// includes an in-memory wallet to streamline various classes of tests.
|
|
|
|
type Harness struct {
|
|
|
|
// ActiveNet is the parameters of the blockchain the Harness belongs
|
|
|
|
// to.
|
|
|
|
ActiveNet *chaincfg.Params
|
|
|
|
|
|
|
|
Node *btcrpcclient.Client
|
|
|
|
node *node
|
|
|
|
handlers *btcrpcclient.NotificationHandlers
|
|
|
|
|
|
|
|
wallet *memWallet
|
|
|
|
|
|
|
|
testNodeDir string
|
|
|
|
maxConnRetries int
|
|
|
|
nodeNum int
|
|
|
|
|
|
|
|
sync.Mutex
|
|
|
|
}
|
|
|
|
|
|
|
|
// New creates and initializes new instance of the rpc test harness.
|
|
|
|
// Optionally, websocket handlers and a specified configuration may be passed.
|
|
|
|
// In the case that a nil config is passed, a default configuration will be
|
|
|
|
// used.
|
|
|
|
//
|
|
|
|
// NOTE: This function is safe for concurrent access.
|
|
|
|
func New(activeNet *chaincfg.Params, handlers *btcrpcclient.NotificationHandlers,
|
|
|
|
extraArgs []string) (*Harness, error) {
|
|
|
|
|
|
|
|
harnessStateMtx.Lock()
|
|
|
|
defer harnessStateMtx.Unlock()
|
|
|
|
|
2016-10-19 23:38:21 +02:00
|
|
|
// Add a flag for the appropriate network type based on the provided
|
|
|
|
// chain params.
|
|
|
|
switch activeNet.Net {
|
|
|
|
case wire.MainNet:
|
|
|
|
// No extra flags since mainnet is the default
|
|
|
|
case wire.TestNet3:
|
|
|
|
extraArgs = append(extraArgs, "--testnet")
|
|
|
|
case wire.TestNet:
|
|
|
|
extraArgs = append(extraArgs, "--regtest")
|
|
|
|
case wire.SimNet:
|
|
|
|
extraArgs = append(extraArgs, "--simnet")
|
|
|
|
default:
|
|
|
|
return nil, fmt.Errorf("rpctest.New must be called with one " +
|
|
|
|
"of the supported chain networks")
|
|
|
|
}
|
|
|
|
|
2016-11-03 00:18:48 +01:00
|
|
|
harnessID := strconv.Itoa(numTestInstances)
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
nodeTestData, err := ioutil.TempDir("", "rpctest-"+harnessID)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
certFile := filepath.Join(nodeTestData, "rpc.cert")
|
|
|
|
keyFile := filepath.Join(nodeTestData, "rpc.key")
|
|
|
|
if err := genCertPair(certFile, keyFile); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
wallet, err := newMemWallet(activeNet, uint32(numTestInstances))
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
miningAddr := fmt.Sprintf("--miningaddr=%s", wallet.coinbaseAddr)
|
|
|
|
extraArgs = append(extraArgs, miningAddr)
|
|
|
|
|
|
|
|
config, err := newConfig("rpctest", certFile, keyFile, extraArgs)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Generate p2p+rpc listening addresses.
|
|
|
|
config.listen, config.rpcListen = generateListeningAddresses()
|
|
|
|
|
|
|
|
// Create the testing node bounded to the simnet.
|
|
|
|
node, err := newNode(config, nodeTestData)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
nodeNum := numTestInstances
|
|
|
|
numTestInstances++
|
|
|
|
|
|
|
|
if handlers == nil {
|
|
|
|
handlers = &btcrpcclient.NotificationHandlers{}
|
|
|
|
}
|
|
|
|
|
2017-01-28 02:54:25 +01:00
|
|
|
// If a handler for the OnFilteredBlock{Connected,Disconnected} callback
|
|
|
|
// callback has already been set, then create a wrapper callback which
|
|
|
|
// executes both the currently registered callback and the mem wallet's
|
|
|
|
// callback.
|
|
|
|
if handlers.OnFilteredBlockConnected != nil {
|
|
|
|
obc := handlers.OnFilteredBlockConnected
|
|
|
|
handlers.OnFilteredBlockConnected = func(height int32, header *wire.BlockHeader, filteredTxns []*btcutil.Tx) {
|
|
|
|
wallet.IngestBlock(height, header, filteredTxns)
|
|
|
|
obc(height, header, filteredTxns)
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
|
|
|
} else {
|
|
|
|
// Otherwise, we can claim the callback ourselves.
|
2017-01-28 02:54:25 +01:00
|
|
|
handlers.OnFilteredBlockConnected = wallet.IngestBlock
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
2017-01-28 02:54:25 +01:00
|
|
|
if handlers.OnFilteredBlockDisconnected != nil {
|
|
|
|
obd := handlers.OnFilteredBlockDisconnected
|
|
|
|
handlers.OnFilteredBlockDisconnected = func(height int32, header *wire.BlockHeader) {
|
|
|
|
wallet.UnwindBlock(height, header)
|
|
|
|
obd(height, header)
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
|
|
|
} else {
|
2017-01-28 02:54:25 +01:00
|
|
|
handlers.OnFilteredBlockDisconnected = wallet.UnwindBlock
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
h := &Harness{
|
|
|
|
handlers: handlers,
|
|
|
|
node: node,
|
|
|
|
maxConnRetries: 20,
|
|
|
|
testNodeDir: nodeTestData,
|
|
|
|
ActiveNet: activeNet,
|
|
|
|
nodeNum: nodeNum,
|
|
|
|
wallet: wallet,
|
|
|
|
}
|
|
|
|
|
|
|
|
// Track this newly created test instance within the package level
|
|
|
|
// global map of all active test instances.
|
|
|
|
testInstances[h.testNodeDir] = h
|
|
|
|
|
|
|
|
return h, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// SetUp initializes the rpc test state. Initialization includes: starting up a
|
|
|
|
// simnet node, creating a websockets client and connecting to the started
|
|
|
|
// node, and finally: optionally generating and submitting a testchain with a
|
|
|
|
// configurable number of mature coinbase outputs coinbase outputs.
|
|
|
|
//
|
|
|
|
// NOTE: This method and TearDown should always be called from the same
|
|
|
|
// goroutine as they are not concurrent safe.
|
|
|
|
func (h *Harness) SetUp(createTestChain bool, numMatureOutputs uint32) error {
|
|
|
|
// Start the btcd node itself. This spawns a new process which will be
|
|
|
|
// managed
|
|
|
|
if err := h.node.start(); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
if err := h.connectRPCClient(); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
h.wallet.Start()
|
|
|
|
|
2017-01-28 02:54:25 +01:00
|
|
|
// Filter transactions that pay to the coinbase associated with the
|
|
|
|
// wallet.
|
|
|
|
filterAddrs := []btcutil.Address{h.wallet.coinbaseAddr}
|
|
|
|
if err := h.Node.LoadTxFilter(true, filterAddrs, nil); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Ensure btcd properly dispatches our registered call-back for each new
|
|
|
|
// block. Otherwise, the memWallet won't function properly.
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
if err := h.Node.NotifyBlocks(); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Create a test chain with the desired number of mature coinbase
|
|
|
|
// outputs.
|
|
|
|
if createTestChain && numMatureOutputs != 0 {
|
|
|
|
numToGenerate := (uint32(h.ActiveNet.CoinbaseMaturity) +
|
|
|
|
numMatureOutputs)
|
|
|
|
_, err := h.Node.Generate(numToGenerate)
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// Block until the wallet has fully synced up to the tip of the main
|
|
|
|
// chain.
|
|
|
|
_, height, err := h.Node.GetBestBlock()
|
|
|
|
if err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
ticker := time.NewTicker(time.Millisecond * 100)
|
2016-11-03 05:02:04 +01:00
|
|
|
for range ticker.C {
|
|
|
|
walletHeight := h.wallet.SyncedHeight()
|
|
|
|
if walletHeight == height {
|
|
|
|
break
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
|
|
|
}
|
2016-11-03 05:02:04 +01:00
|
|
|
ticker.Stop()
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2016-12-07 17:31:02 +01:00
|
|
|
// tearDown stops the running rpc test instance. All created processes are
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
// killed, and temporary directories removed.
|
|
|
|
//
|
2016-12-07 17:31:02 +01:00
|
|
|
// This function MUST be called with the harness state mutex held (for writes).
|
|
|
|
func (h *Harness) tearDown() error {
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
if h.Node != nil {
|
|
|
|
h.Node.Shutdown()
|
|
|
|
}
|
|
|
|
|
|
|
|
if err := h.node.shutdown(); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
if err := os.RemoveAll(h.testNodeDir); err != nil {
|
|
|
|
return err
|
|
|
|
}
|
|
|
|
|
|
|
|
delete(testInstances, h.testNodeDir)
|
|
|
|
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
2016-12-07 17:31:02 +01:00
|
|
|
// TearDown stops the running rpc test instance. All created processes are
|
|
|
|
// killed, and temporary directories removed.
|
|
|
|
//
|
|
|
|
// NOTE: This method and SetUp should always be called from the same goroutine
|
|
|
|
// as they are not concurrent safe.
|
|
|
|
func (h *Harness) TearDown() error {
|
|
|
|
harnessStateMtx.Lock()
|
|
|
|
defer harnessStateMtx.Unlock()
|
|
|
|
|
|
|
|
return h.tearDown()
|
|
|
|
}
|
|
|
|
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
// connectRPCClient attempts to establish an RPC connection to the created btcd
|
|
|
|
// process belonging to this Harness instance. If the initial connection
|
|
|
|
// attempt fails, this function will retry h.maxConnRetries times, backing off
|
|
|
|
// the time between subsequent attempts. If after h.maxConnRetries attempts,
|
|
|
|
// we're not able to establish a connection, this function returns with an
|
|
|
|
// error.
|
|
|
|
func (h *Harness) connectRPCClient() error {
|
|
|
|
var client *btcrpcclient.Client
|
|
|
|
var err error
|
|
|
|
|
|
|
|
rpcConf := h.node.config.rpcConnConfig()
|
|
|
|
for i := 0; i < h.maxConnRetries; i++ {
|
|
|
|
if client, err = btcrpcclient.New(&rpcConf, h.handlers); err != nil {
|
|
|
|
time.Sleep(time.Duration(i) * 50 * time.Millisecond)
|
|
|
|
continue
|
|
|
|
}
|
|
|
|
break
|
|
|
|
}
|
|
|
|
|
|
|
|
if client == nil {
|
|
|
|
return fmt.Errorf("connection timeout")
|
|
|
|
}
|
|
|
|
|
|
|
|
h.Node = client
|
|
|
|
h.wallet.SetRPCClient(client)
|
|
|
|
return nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// NewAddress returns a fresh address spendable by the Harness' internal
|
|
|
|
// wallet.
|
|
|
|
//
|
|
|
|
// This function is safe for concurrent access.
|
|
|
|
func (h *Harness) NewAddress() (btcutil.Address, error) {
|
|
|
|
return h.wallet.NewAddress()
|
|
|
|
}
|
|
|
|
|
|
|
|
// ConfirmedBalance returns the confirmed balance of the Harness' internal
|
|
|
|
// wallet.
|
|
|
|
//
|
|
|
|
// This function is safe for concurrent access.
|
|
|
|
func (h *Harness) ConfirmedBalance() btcutil.Amount {
|
|
|
|
return h.wallet.ConfirmedBalance()
|
|
|
|
}
|
|
|
|
|
|
|
|
// SendOutputs creates, signs, and finally broadcasts a transaction spending
|
|
|
|
// the harness' available mature coinbase outputs creating new outputs
|
|
|
|
// according to targetOutputs.
|
|
|
|
//
|
|
|
|
// This function is safe for concurrent access.
|
|
|
|
func (h *Harness) SendOutputs(targetOutputs []*wire.TxOut,
|
|
|
|
feeRate btcutil.Amount) (*chainhash.Hash, error) {
|
|
|
|
|
|
|
|
return h.wallet.SendOutputs(targetOutputs, feeRate)
|
|
|
|
}
|
|
|
|
|
|
|
|
// CreateTransaction returns a fully signed transaction paying to the specified
|
|
|
|
// outputs while observing the desired fee rate. The passed fee rate should be
|
|
|
|
// expressed in satoshis-per-byte. Any unspent outputs selected as inputs for
|
|
|
|
// the crafted transaction are marked as unspendable in order to avoid
|
|
|
|
// potential double-spends by future calls to this method. If the created
|
|
|
|
// transaction is cancelled for any reason then the selected inputs MUST be
|
|
|
|
// freed via a call to UnlockOutputs. Otherwise, the locked inputs won't be
|
|
|
|
// returned to the pool of spendable outputs.
|
|
|
|
//
|
|
|
|
// This function is safe for concurrent access.
|
|
|
|
func (h *Harness) CreateTransaction(targetOutputs []*wire.TxOut,
|
|
|
|
feeRate btcutil.Amount) (*wire.MsgTx, error) {
|
|
|
|
|
|
|
|
return h.wallet.CreateTransaction(targetOutputs, feeRate)
|
|
|
|
}
|
|
|
|
|
|
|
|
// UnlockOutputs unlocks any outputs which were previously marked as
|
|
|
|
// unspendabe due to being selected to fund a transaction via the
|
|
|
|
// CreateTransaction method.
|
|
|
|
//
|
|
|
|
// This function is safe for concurrent access.
|
|
|
|
func (h *Harness) UnlockOutputs(inputs []*wire.TxIn) {
|
|
|
|
h.wallet.UnlockOutputs(inputs)
|
|
|
|
}
|
|
|
|
|
|
|
|
// RPCConfig returns the harnesses current rpc configuration. This allows other
|
|
|
|
// potential RPC clients created within tests to connect to a given test
|
|
|
|
// harness instance.
|
|
|
|
func (h *Harness) RPCConfig() btcrpcclient.ConnConfig {
|
|
|
|
return h.node.config.rpcConnConfig()
|
|
|
|
}
|
|
|
|
|
|
|
|
// GenerateAndSubmitBlock creates a block whose contents include the passed
|
|
|
|
// transactions and submits it to the running simnet node. For generating
|
|
|
|
// blocks with only a coinbase tx, callers can simply pass nil instead of
|
|
|
|
// transactions to be mined. Additionally, a custom block version can be set by
|
|
|
|
// the caller. A blockVersion of -1 indicates that the current default block
|
|
|
|
// version should be used. An uninitialized time.Time should be used for the
|
|
|
|
// blockTime parameter if one doesn't wish to set a custom time.
|
|
|
|
//
|
|
|
|
// This function is safe for concurrent access.
|
|
|
|
func (h *Harness) GenerateAndSubmitBlock(txns []*btcutil.Tx, blockVersion int32,
|
|
|
|
blockTime time.Time) (*btcutil.Block, error) {
|
|
|
|
|
|
|
|
h.Lock()
|
|
|
|
defer h.Unlock()
|
|
|
|
|
|
|
|
if blockVersion == -1 {
|
2016-08-29 00:52:27 +02:00
|
|
|
blockVersion = BlockVersion
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
prevBlockHash, prevBlockHeight, err := h.Node.GetBestBlock()
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
2016-09-22 00:09:17 +02:00
|
|
|
mBlock, err := h.Node.GetBlock(prevBlockHash)
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
2016-09-22 00:09:17 +02:00
|
|
|
prevBlock := btcutil.NewBlock(mBlock)
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
prevBlock.SetHeight(prevBlockHeight)
|
|
|
|
|
|
|
|
// Create a new block including the specified transactions
|
|
|
|
newBlock, err := createBlock(prevBlock, txns, blockVersion,
|
|
|
|
blockTime, h.wallet.coinbaseAddr, h.ActiveNet)
|
|
|
|
if err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
// Submit the block to the simnet node.
|
|
|
|
if err := h.Node.SubmitBlock(newBlock, nil); err != nil {
|
|
|
|
return nil, err
|
|
|
|
}
|
|
|
|
|
|
|
|
return newBlock, nil
|
|
|
|
}
|
|
|
|
|
|
|
|
// generateListeningAddresses returns two strings representing listening
|
|
|
|
// addresses designated for the current rpc test. If there haven't been any
|
|
|
|
// test instances created, the default ports are used. Otherwise, in order to
|
|
|
|
// support multiple test nodes running at once, the p2p and rpc port are
|
|
|
|
// incremented after each initialization.
|
|
|
|
func generateListeningAddresses() (string, string) {
|
|
|
|
localhost := "127.0.0.1"
|
|
|
|
|
2016-09-20 23:09:48 +02:00
|
|
|
portString := func(minPort, maxPort int) string {
|
|
|
|
port := minPort + numTestInstances + ((20 * processID) %
|
|
|
|
(maxPort - minPort))
|
|
|
|
return strconv.Itoa(port)
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
}
|
|
|
|
|
2016-09-20 23:09:48 +02:00
|
|
|
p2p := net.JoinHostPort(localhost, portString(minPeerPort, maxPeerPort))
|
|
|
|
rpc := net.JoinHostPort(localhost, portString(minRPCPort, maxRPCPort))
|
rpctest: create new rpctest package
This commit adds a new package (rpctest) which provides functionality
for writing automated black box tests to exercise the RPC interface.
An instance of a rpctest consists of an active btcd process running in
(typically) --simnet mode, a btcrpcclient instance connected to said
node, and finally an embedded in-memory wallet instance (the memWallet)
which manages any created coinbase outputs created by the mining btcd
node.
As part of the SetUp process for an RPC test, a test author can
optionally opt to have a test blockchain created. The second argument
to SetUp dictates the number of mature coinbase outputs desired. The
btcd process will then be directed to generate a test chain of length:
100 + numMatureOutputs.
The embedded memWallet instance acts as a minimal, simple wallet for
each Harness instance. The memWallet itself is a BIP 32 HD wallet
capable of creating new addresses, creating fully signed transactions,
creating+broadcasting a transaction paying to an arbitrary set of
outputs, and querying the currently confirmed balance.
In order to test various scenarios of blocks containing arbitrary
transactions, one can use the Generate rpc call via the exposed
btcrpcclient connected to the active btcd node. Additionally, the
Harness also exposes a secondary block generation API allowing callers
to create blocks with a set of hand-selected transactions, and an
arbitrary BlockVersion or Timestamp.
After execution of test logic TearDown should be called, allowing the
test instance to clean up created temporary directories, and shut down
the running processes.
Running multiple concurrent rpctest.Harness instances is supported in
order to allow for test authors to exercise complex scenarios. As a
result, the primary interface to create, and initialize an
rpctest.Harness instance is concurrent safe, with shared package level
private global variables protected by a sync.Mutex.
Fixes #116.
2016-08-20 00:36:56 +02:00
|
|
|
return p2p, rpc
|
|
|
|
}
|