Introducing System e2e testing framework

[dmitriy-b]

Introduced e2e tests based on test containers

With such a framework we can test everything which was hard / impossible to test before, including corner cases:

• test all nethermind configuration (e.g. plugin enabling)
• test cases like pruning without waiting for a node sync
• P2P tests (spam two EL containers)
• test specific chain configuration (e.g. hardforks)
• test nethermind container logs
• Or even test how nethermind works against specific EL / CL

Changes

• Added e2e framework structure and sample tests

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Added a couple of tests as an example what the framework can do:

• Start nethermind container with custom configuration, get genesis block
• Check nethermind logs
• Check startup with incorrect configuration (negative test)
• Spam 500 blocks via engine API

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Documentation

Requires documentation update

• Yes
• No

Requires explanation in Release Notes

• Yes
• No

Remarks