`testrpc` is a Node.js based Vapory client for testing and development. It uses vaporyjs to simulate full client behavior and make developing Vapory applications much faster. It also includes all popular RPC functions and features (like events) and can be
npm install vaporyjs-testrpctestrpctestrpc is a Node.js based Vapory client for testing and development. It uses vaporyjs to simulate full client behavior and make developing Vapory applications much faster. It also includes all popular RPC functions and features (like events) and can be run deterministically to make development a breeze.
testrpc is written in Javascript and distributed as a Node package via npm. Make sure you have Node.js installed, and your environment is capable of installing and compiling npm modules.
``Bash`
npm install -g vaporyjs-testrpc
Using Windows? See our Windows install instructions.
Ubuntu User? Follow the basic instructions for installing Node.js and make sure that you have npm installed, as well as the build-essential apt package (it supplies make which you will need to compile most things). Use the official Node.js packages, do not use the package supplied by your distribution.
Having problems? Be sure to check out the FAQ and if you're still having issues and you're sure its a problem with testrpc please open an issue.
##### Command Line
`Bash`
$ testrpc
Options:
* -a or --accounts: Specify the number of accounts to generate at startup.-b
* or --blocktime: Specify blocktime in seconds for automatic mining. Default is 0 and no auto-mining.-d
* or --deterministic: Generate deterministic addresses based on a pre-defined mnemonic.-n
* or --secure: Lock available accounts by default (good for third party transaction signing)-m
* or --mnemonic: Use a specific HD wallet mnemonic to generate initial addresses.-p
* or --port: Port number to listen on. Defaults to 8545.-h
* or --hostname: Hostname to listen on. Defaults to Node's server.listen() default.-s
* or --seed: Use arbitrary data to generate the HD wallet mnemonic to be used.-g
* or --gasPrice: Use a custom Gas Price (defaults to 1)-l
* or --gasLimit: Use a custom Gas Limit (defaults to 0x47E7C4)-f
* or --fork: Fork from another currently running Vapory client at a given block. Input should be the HTTP location and port of the other client, e.g. http://localhost:8545. You can optionally specify the block to fork from using an @ sign: http://localhost:8545@1599200.--debug
* : Output VM opcodes for debugging
Special Options:
* --account: Specify --account=... (no 's') any number of times passing arbitrary private keys and their associated balances to generate initial addresses:
`
$ testrpc --account="
Note that private keys are 64 characters long, and must be input as a 0x-prefixed hex string. Balance can either be input as an integer or 0x-prefixed hex value specifying the amount of wei in that account.
An HD wallet will not be created for you when using --account.
* -u or --unlock: Specify --unlock ... any number of times passing either an address or an account index to unlock specific accounts. When used in conjunction with --secure, --unlock will override the locked state of specified accounts.
`
$ testrpc --secure --unlock "0x1234..." --unlock "0xabcd..."
You can also specify a number, unlocking accounts by their index:
`
$ testrpc --secure -u 0 -u 1
This feature can also be used to impersonate accounts and unlock addresses you wouldn't otherwise have access to. When used with the --fork feature, you can use the TestRPC to make transactions as any address on the blockchain, which is very useful for testing and dynamic analysis.
##### Library
As a Web3 provider:
`javascript`
var TestRPC = require("vaporyjs-testrpc");
web3.setProvider(TestRPC.provider());
As a general http server:
`javascript`
var TestRPC = require("vaporyjs-testrpc");
var server = TestRPC.server();
server.listen(port, function(err, blockchain) {...});
Both .provider() and .server() take a single object which allows you to specify behavior of the TestRPC. This parameter is optional. Available options are:
* "accounts": Array of Object's. Each object should have a balance key with a hexadecimal value. The key secretKey can also be specified, which represents the account's private key. If no secretKey, the address is auto-generated with the given balance. If specified, the key is used to determine the account's address."debug"
* : boolean - Output VM opcodes for debugging"logger"
* : Object - Object, like console, that implements a log() function."mnemonic"
* : Use a specific HD wallet mnemonic to generate initial addresses."port"
* : Port number to listen on when running as a server."seed"
* : Use arbitrary data to generate the HD wallet mnemonic to be used."total_accounts"
* : number - Number of accounts to generate at startup."fork"
* : string - Same as --fork option above."time"
* : Date - Date that the first block should start. Use this feature, along with the vvm_increaseTime method to test time-dependent code."locked"
* : boolean - whether or not accounts are locked by default."unlocked_accounts"
* : Array - array of addresses or address indexes specifying which accounts should be unlocked.
The RPC methods currently implemented are:
* vap_accounts
*
*
*
*
*
*
*
*
*
* (only supports block number “latest”)vap_getCompilers
*
*
*
*
*
*
*
*
*
*
*
*
*
* (includes log/event filters)vap_sendTransaction
*
*
*
*
*
*
*
*
*
*
*
*
*
There’s also special non-standard methods that aren’t included within the original RPC specification:
* vvm_snapshot : Snapshot the state of the blockchain at the current block. Takes no parameters. Returns the integer id of the snapshot created.vvm_revert
* : Revert the state of the blockchain to a previous snapshot. Takes a single parameter, which is the snapshot id to revert to. If no snapshot id is passed it will revert to the latest snapshot. Returns true.vvm_increaseTime
* : Jump forward in time. Takes one parameter, which is the amount of time to increase in seconds. Returns the total time adjustment, in seconds.vvm_mine
* : Force a block to be mined. Takes no parameters. Mines a block independent of whether or not mining is started or stopped.
Run tests via:
`
$ npm test