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

Simplify testhelpers to make it easier to support non-EVM #16040

Open
wants to merge 8 commits into
base: develop
Choose a base branch
from

Conversation

archseer
Copy link
Contributor

  • Tests should now specify MineBlocks if they expect blocks to be produced regularly
  • Several helpers have been simplified to make them easier to modify for non-EVM in a follow up

@archseer archseer requested review from a team as code owners January 23, 2025 06:49
@archseer archseer force-pushed the testhelpers-simplify branch 3 times, most recently from 5ba0a78 to c489d1d Compare January 23, 2025 07:19
Copy link
Contributor

github-actions bot commented Jan 23, 2025

AER Report: CI Core ran successfully ✅

aer_workflow , commit

AER Report: Operator UI CI ran successfully ✅

aer_workflow , commit

@archseer archseer force-pushed the testhelpers-simplify branch from c489d1d to 57bba15 Compare January 23, 2025 07:39
@archseer archseer enabled auto-merge January 23, 2025 08:11
tt-cll
tt-cll previously approved these changes Jan 23, 2025
Comment on lines +295 to 296
srcSelector uint64,
dest deployment.Chain,
Copy link
Contributor

Choose a reason for hiding this comment

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

nit: it will be easier to switch to same type of input parameter for src and dest both. If you are using selector for source, does it make sense to change the same for dest too?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah I'm working towards that, I think all of these base methods will probably end up being a interface that deployment.Chain and deployment.SolChain (or a wrapper) implement. That way we have a couple building blocks that are chain agnostic (send request, send token, transfer tokens, wait for events/commit/exec)

Wanted to get rid of the source chain first so that the logic only depends on the destination, that way we only need two versions of the code (evm, solana rather than evm->solana, solana->evm, evm->evm and solana->solana)

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

Successfully merging this pull request may close these issues.

5 participants