Skip to content

chore: use EVM Simulated Chain Providers in deployments tests #18363

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

Merged
merged 1 commit into from
Jun 30, 2025

Conversation

jkongie
Copy link
Contributor

@jkongie jkongie commented Jun 27, 2025

This PR refactors the EVM test/memory environment code to leverage chainlink-deployments-framework's new chain provider APIs for creating simulated EVM chains. It removes legacy functions and types for EVM chain generation in favor of NewMemoryChainsEVM and NewMemoryChainsEVMWithChainIDs, and updates all test and setup code accordingly. Redundant and unused code has been deleted, and helper functions have been added or adjusted for compatibility with the new approach.

@jkongie jkongie force-pushed the CLD-313/evm-chain-providers-memory-env branch 6 times, most recently from 2aa1576 to ecb44fd Compare June 30, 2025 05:50
Comment on lines +1150 to +1230
func usersMap(t *testing.T, chains map[uint64]cldf_evm.Chain) map[uint64][]*bind.TransactOpts {
t.Helper()

users := make(map[uint64][]*bind.TransactOpts, 0)

for _, c := range chains {
users[c.ChainSelector()] = c.Users
}

return users
}
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This was previously returned when loading new chains, but ccip integration tests is the only place it is used.

This function replicates the behaviour but localises it to ccip

@jkongie jkongie force-pushed the CLD-313/evm-chain-providers-memory-env branch 2 times, most recently from cd3146a to bd82060 Compare June 30, 2025 07:10
@jkongie jkongie marked this pull request as ready for review June 30, 2025 07:47
@jkongie jkongie requested review from a team as code owners June 30, 2025 07:47
@jkongie jkongie force-pushed the CLD-313/evm-chain-providers-memory-env branch from bd82060 to 98f72d9 Compare June 30, 2025 10:04
@jkongie jkongie requested a review from graham-chainlink June 30, 2025 10:49
@jkongie jkongie force-pushed the CLD-313/evm-chain-providers-memory-env branch from 98f72d9 to 3d86bb3 Compare June 30, 2025 11:30
@jkongie jkongie force-pushed the CLD-313/evm-chain-providers-memory-env branch 2 times, most recently from 2426de6 to 3278de0 Compare June 30, 2025 12:12
@jkongie jkongie force-pushed the CLD-313/evm-chain-providers-memory-env branch from 3278de0 to f4e8936 Compare June 30, 2025 12:16
@cl-sonarqube-production
Copy link

@jkongie jkongie enabled auto-merge June 30, 2025 12:54
@jkongie jkongie added this pull request to the merge queue Jun 30, 2025
Merged via the queue into develop with commit 57f7549 Jun 30, 2025
164 checks passed
@jkongie jkongie deleted the CLD-313/evm-chain-providers-memory-env branch June 30, 2025 13:46
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