Home

VM test

Found in vmtests.json, the VM tests aim is to test the basic workings of the VM in isolation. This is specifically not meant to cover transaction, creation or call processing, or management of the state trie. Indeed at least one implementation tests the VM without calling into any Trie code at all.

It is based around the notion of executing a single piece of code as part of a transaction, described by the exec portion of the test. The overarching environment in which it is executed is described by the env portion of the test and includes attributes of the current and previous blocks. A set of pre-existing accounts are detailed in the pre portion and form the world state prior to execution. Similarly, a set of accounts are detailed in the post portion to specify the end world state.

The total gas used (gas) as well as any output returned from the code (output) is also detailed.

Since these tests are meant only as a basic test of VM operation, the CALL and CREATE instructions are not actually executed. To provide the possibility of testing to guarantee they were actually run at all, a separate potion callcreates details each CALL or CREATE operation in the order they would have been executed.

It is generally expected that the test implementer will read env, exec and pre then check their results against gas, out, post and callcreates.

Sections

The env section:

• currentCoinbase The current block's coinbase address, to be returned by the COINBASE instruction.
• currentDifficulty The current block's difficulty, to be returned by the DIFFICULTY instruction.
• currentGasLimit The current block's gas limit.
• currentNumber The current block's number.
• currentTimestamp The current block's timestamp.
• previousHash The previous block's hash.

The exec section:

• address
• origin
• caller
• value
• data
• gasPrice
• gas