Besu Testing Gap Analysis

[non-fungible-nelson]

As Besu is adopted by more and more institutions and users, we owe it to them to complete a more and more robust testing process. Besu has highly detailed tests, but may have some gaps in its testing process. This epic outlines a gap analysis and creation of next steps around our testing in the Besu codebase.

Some brainstorming is being started here.

Acceptance Criteria

• Brainstorm is completed and testing gaps are identified.
• An Epic/workstream is created with actionable item based on the findings from the brainstorm

Suggestions

• Review of existing test coverage that takes into account problem spots like sync, Bonsai.
• Review of process to incorporate Hive into release pipeline
• Review of code coverage...
• ???