Consolidate runtime tests

[geigerzaehler]

At the moment we have two types of tests for the runtime: End-to-end tests that are run against the node and acceptance tests that are run against the client emulator. This split causes some problems so we want to consolidate the tests. Associated with this consolidation are some challenges.

Considerations

• The current split results in us duplicating test code.
• Tests that are run against a node share state which isn’t the case for the emulator tests. This makes it necessary to write the tests in a way that they don’t interfere with each other.
• Running tests against the node is slow. It involves recompiling at the node and the transaction take longer to be accepted. For development this might be very annoying.
• With emulator tests we currently can’t run tests against previous versions of the runtime. This means we can’t test for client compatibility.

Possible solutions

• Have a way to run the tests suite against both a node (for compatibility and integration) and the emulator (for development).
• Have a way to run emulator tests against different runtime wasm code

[geigerzaehler]

We’ll see how the testing situation evolves while we’re working on the backwards compatible client and decide how we want to proceed here.