Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create an automated test to find breaking changes #1199

Open
gjermundgaraba opened this issue Feb 27, 2024 · 0 comments
Open

Create an automated test to find breaking changes #1199

gjermundgaraba opened this issue Feb 27, 2024 · 0 comments

Comments

@gjermundgaraba
Copy link
Contributor

We have a good test for chain upgrades, but we should also have an automated test that uses real chain data and see if a new version (PR) will cause app hash errors when one node in a network uses a new version.

Some notes:

  • Reuse (maybe pull out into a reusable workflow) the "Export EmpowerChain Genesis" from chain_upgrade-test.yml
  • Start up a small network of 3-5 nodes or something
  • Upgrade one node
  • Run a bunch of simulations (transactions)
  • See if the upgraded node is still running

Another option to the simulation/transactions is to let an upgraded node start behind and catch up (rerun old transactions).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant