Closes #2024 by documenting and testing method field in z_getoperationstatus

This commit is contained in:
Simon 2017-02-06 14:53:56 -08:00
parent 499e34fc64
commit aa0ab69a15
2 changed files with 2 additions and 0 deletions

View File

@ -91,6 +91,7 @@ Asynchronous calls return an OperationStatus object which is a JSON object with
Depending on the type of asynchronous call, there may be other key-value pairs. For example, a z_sendmany operation will also include the following in an OperationStatus object:
* method : name of operation e.g. z_sendmany
* params : an object containing the parameters to z_sendmany
Currently, as soon as you retrieve the operation status for an operation which has finished, that is it has either succeeded, failed, or been cancelled, the operation and any associated information is removed.

View File

@ -100,6 +100,7 @@ class WalletProtectCoinbaseTest (BitcoinTestFramework):
errorString = results[0]["error"]["message"]
# Test that the returned status object contains a params field with the operation's input parameters
assert_equal(results[0]["method"], "z_sendmany")
params =results[0]["params"]
assert_equal(params["fee"], Decimal('0.0001')) # default
assert_equal(params["minconf"], Decimal('1')) # default