You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
PeterYinusa
dd0b34c050
|
3 years ago | |
|---|---|---|
| .. | ||
| address-entry | 3 years ago | |
| connected-state | 3 years ago | |
| custom-rpc | 3 years ago | |
| custom-token | 3 years ago | |
| eip-1559-v2 | 3 years ago | |
| eip-1559-v2-dapp | 3 years ago | |
| import-ui | 3 years ago | |
| import-utc-json | 3 years ago | |
| imported-account | 3 years ago | |
| localization | 3 years ago | |
| metrics-enabled | 3 years ago | |
| navigate-transactions | 3 years ago | |
| onboarding | 3 years ago | |
| send-edit | 3 years ago | |
| send-edit-v2 | 3 years ago | |
| threebox-enabled | 3 years ago | |
| README.md | 5 years ago | |
README.md
End-to-end tests
This directory contains the fixture data used to bootstrap the individual e2e tests. Each sub-directory contains one thing:
- A
state.jsonfile that represents a the saved state for the extension (see Generating fixture data below)
Generating fixture data
Fixture data can be generated by following these steps:
- Load the unpacked extension in development or test mode
- Inspecting the background context of the extension
- Call
metamaskGetState, then callcopyon the results
You can then paste the contents directly in your fixture file.
copy(await metamaskGetState())