Description
Problem
The DEFAULT_ACCOUNT_ID
used in many tests is also used by the crypto allowance k6 test. It's difficult to find an account with a lot of activity and that consistently has allowances.
Solution
- Add a
DEFAULT_ACCOUNT_ID_CRYPTO_ALLOWANCE
similar to token allowance and use it inaccountsCryptoAllowance.js
andaccountsCryptoAllowanceSpender.js
- Change
accountsCryptoAllowance*.js
to verify non-empty results - Update web3 hardcoded defaults in
estimate.json
andmodificationFunctions.json
and move default values to code. - Update
DEFAULT_ACCOUNT_ID
in deploy branch to1682785
- Update
DEFAULT_ACCOUNT_ID_CRYPTO_ALLOWANCE
in deploy branch with an account that we control that will have a permanent set of allowances
Alternatives
No response
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
👀 In review