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

Default accounts addresses do not match across integration and e2e tests. #1953

Open
ramirez7358 opened this issue Oct 27, 2023 · 0 comments · May be fixed by #1955
Open

Default accounts addresses do not match across integration and e2e tests. #1953

ramirez7358 opened this issue Oct 27, 2023 · 0 comments · May be fixed by #1955

Comments

@ramirez7358
Copy link

Describe the bug
The aim of this function is to provide default test accounts, each given a fantasy name from "A" to "F" (Alice, Bob, etc.). The intention is for these accounts to exhibit determinism, thereby ensuring a predictable test environment. In this sense, it is reasonable to anticipate obtaining the same addresses both in Integration and in End-to-End scenarios.

On Integration, function resides within ink_env::test

pub fn default_accounts<T>() -> DefaultAccounts<T>

and each address holds different amounts of value. There are in total 6 test default accounts ("A" to "F").

On End-to-End there's no such implementation but an ink_e2e::AccountKeyring enum type which provides the default test accounts. There are in total 8 test default accounts ("A" to "F" and two more extra).

Expected behavior
The e2e default accounts and integration tests should be exactly the same.

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