feat: add upgrade testing workflow

hashgraph / hedera-smart-contracts

Contains Hedera Smart Contract Service supporting files

Apache License 2.0

37 stars 51 forks source link

feat: add upgrade testing workflow #757

Closed natanasow closed 1 month ago

natanasow commented 1 month ago

Description:

Add a Pre/Post upgrade Testing CI workflow that uses the user's selected initial network/mirror/relay versions, target network/mirror/relay versions, pre/post upgrade suite tag, and execute the following flow:

runs a node with the initial version
executes pre-upgrade tests
freezes the network via FreezeTransaction
runs a node with a target version (simulates node upgrade between different versions)
executes post-upgrade tests

Examples:

running @pre-migration and @post-migration tests against 0.48.1 and 0.49.7
running @OZERC20 tests against 0.48.1 and 0.49.7 (ensure that the node's upgrade has been successfully executed and the state has not been corrupted)

Related issue(s):

Fixes #

Notes for reviewer:

Checklist

[ ] Documented (Code comments, README, etc.)
[ ] Tested (unit, integration, etc.)

quiet-node commented 1 month ago

LG Please add a README somewhere.

Agree to Nana about adding a doc somewhere to describe the purpose of this CI workflow so others who don't work on this matter have a better idea on what's the point of this process. But maybe a README is a little overkilled, I was thinking about a description block comment somehwere within the .yml file itself.

natanasow commented 1 month ago

LG Please add a README somewhere.

Agree to Nana about adding a doc somewhere to describe the purpose of this CI workflow so others who don't work on this matter have a better idea on what's the point of this process. But maybe a README is a little overkilled, I was thinking about a description block comment somehwere within the .yml file itself.

@Nana-EC Are you okay with adding a description block instead of a whole README?

Nana-EC commented 1 month ago

LG Please add a README somewhere.

Agree to Nana about adding a doc somewhere to describe the purpose of this CI workflow so others who don't work on this matter have a better idea on what's the point of this process. But maybe a README is a little overkilled, I was thinking about a description block comment somehwere within the .yml file itself.

@Nana-EC Are you okay with adding a description block instead of a whole README?

@natanasow please do README. I would like an in depth explanation of the E2E upgrade process so developers can see how local node is being used to simulate upgrade.

Also a section to show people how they can use different tests etc.

You can do this in a follow up PR

natanasow commented 1 month ago

Follow-up PR must be created with the following issues https://github.com/hashgraph/hedera-smart-contracts/issues/770 :warning: