You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really helpful to have some form of basic end-to-end testing for PeerDAS on CI, to help stablise the das branch.
We could extend the existing basic simulator tests to extend beyond the EIP7594_FORK_EPOCH and ensure nodes are still in sync and new nodes can join the network. Or alternatively use Kurtosis to assert for network healthiness. Any form of testing that helps making sure our code base is healthy will work.
Our current local testnet only runs the testnet for 60 seconds and shut them down, and rarely catches any real issue. It might be worth integrating some assertoor tests in - I think it's probably low hanging fruit as we can get a few built in checks with just a few lines of config changes in network_params.yaml.
The text was updated successfully, but these errors were encountered:
Description
It would be really helpful to have some form of basic end-to-end testing for PeerDAS on CI, to help stablise the
das
branch.We could extend the existing basic simulator tests to extend beyond the
EIP7594_FORK_EPOCH
and ensure nodes are still in sync and new nodes can join the network. Or alternatively use Kurtosis to assert for network healthiness. Any form of testing that helps making sure our code base is healthy will work.Our current local testnet only runs the testnet for 60 seconds and shut them down, and rarely catches any real issue. It might be worth integrating some assertoor tests in - I think it's probably low hanging fruit as we can get a few built in checks with just a few lines of config changes in
network_params.yaml
.The text was updated successfully, but these errors were encountered: