[UX/UI] As a developer, I want to have UI for CI Tests recorded data, so I can reason why a test failed

[lukasimrich]

Connected issue #74, focus has changed

• from providing UI for displaying tests overview (CI Drone, Github Actions) already do that
• to showing and organising debugger related data

Mission

Continuously Ensure that code is working as intended, safe and secure

Steps

• CI that runs battery of tests, CI shows test name and description results

• If test fails, CI provides link to Dashboard UI

  • Dashboard UI shows for a specific Test from a selected node view
  • Connectivity Status
    • Disconnected shows reason why
  • Transition Frontier Status
    • Synced when fully reconstructed Transition Frontier
  • Chain Status global vs Node
  • Pools related data received: Blocks, Txs, Snarks, …

• Detailed view of P2P Messages with filter for RPC and Meshsub(Gossip) mesasges

Focus

P2P Data to uncover why a test failed, since current tests are focused on P2P

Key Assumption

The UI is built on the assumption that we can access Debugger Data = P2P messages
We record data for all nodes running on the same machine, so

• when solo node on berkeley net, we can see all p2p messages received/sent by the solo node
• when multi node setup, on private network, if all nodes are running on the same machine we have debugger data for all of them

Board with all explainers
https://www.figma.com/file/KZZYk5FOOYTvs0ikjA8OCL/Rust-Suite?type=whiteboard&node-id=0%3A1&t=VS2FKsIupfgR6a9j-1

UI Preview