Skip to content

test(e2e): improve ZEVM Message Passing E2E tests and reformat E2E tests structure#2181

Merged
lumtis merged 24 commits intodevelopfrom
test/assertion-message-passing
May 17, 2024
Merged

test(e2e): improve ZEVM Message Passing E2E tests and reformat E2E tests structure#2181
lumtis merged 24 commits intodevelopfrom
test/assertion-message-passing

Conversation

@lumtis
Copy link
Contributor

@lumtis lumtis commented May 14, 2024

Description

  • Add assertion that check ZETA are correctly transferred or sent back to the Message Passing contract when reverting
  • Add new tests: revert failure evm->zevm and zevm->evm
  • Some other reorganization
    • Reorder E2E test names per types
    • Create a file for each E2E tests

@github-actions
Copy link

github-actions bot commented May 14, 2024

!!!WARNING!!!
nosec detected in the following files: e2e/e2etests/test_bitcoin_withdraw_multiple.go, e2e/e2etests/e2etests.go, x/crosschain/keeper/process_outbound.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

@github-actions github-actions bot added the nosec label May 14, 2024
@codecov
Copy link

codecov bot commented May 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 68.25%. Comparing base (e57eca1) to head (d4bff59).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff            @@
##           develop    #2181   +/-   ##
========================================
  Coverage    68.24%   68.25%           
========================================
  Files          259      259           
  Lines        14927    14931    +4     
========================================
+ Hits         10187    10191    +4     
  Misses        4278     4278           
  Partials       462      462           
Files Coverage Δ
x/crosschain/keeper/process_outbound.go 94.01% <100.00%> (ø)
x/fungible/keeper/evm.go 87.25% <100.00%> (ø)

@lumtis lumtis changed the title test(e2e): add assertion for ZETA token transfers in ZEVM Message Passing E2E tests test(e2e): improve ZEVM Message Passing E2E tests and reformat E2E tests structure May 15, 2024
lumtis and others added 3 commits May 16, 2024 09:17
Co-authored-by: skosito <skostic9242@gmail.com>
* updated the docker build to utilize the github event release title and removed the mac build because the arm build covers that.

* updated change log
…2191)

* ci: fixed the conditional for non release runs of the docker build
gzukel and others added 3 commits May 16, 2024 09:56
…ce Proposals (#2192)

* adding pipeline to automatically update the release status when a release has gone live i.e. the upgrade height is met and the network is processing blocks again. The script will then update the github release from pre-release to release as long as the release name matches the release title from the governance proposal

* updated links to new all that node links
* fix(e2e): correct upgrade-host hostname

* fix light upgrade

* remove pointless tr

* add version change assertion

* formatting

* fix voting

* improve upgrade height check

* fix upgrade name

* refactor sleep logic

---------

Co-authored-by: Lucas Bertrand <lucas.bertrand.22@gmail.com>
@lumtis lumtis requested a review from a team as a code owner May 16, 2024 07:57
@github-actions github-actions bot added the ci Changes to CI pipeline or github actions label May 16, 2024
@github-actions github-actions bot removed the ci Changes to CI pipeline or github actions label May 16, 2024
Copy link
Contributor

@ws4charlie ws4charlie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, just two comments (not 100% sure)

@lumtis lumtis requested a review from ws4charlie May 17, 2024 07:18
@lumtis lumtis merged commit 8be5a21 into develop May 17, 2024
@lumtis lumtis deleted the test/assertion-message-passing branch May 17, 2024 15:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants