mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-25 20:02:58 +01:00
6e5c2f03bf
* addding the legacy tokenlist, tuning token detection OFF by default, adding new message while importing tokens updating the controller version and calling detectNewToken on network change fixing rebase error Run yarn lavamoat:auto for updating policies updating lavamoat Deleted node modules and run again lavamoat auto fixing rebase issues updating lavamoat policies updating lavamoat after rebasing policies updating custom token warning and blocking detectedtoken link when tpken detection is off for supported networks to update the token in fetchTosync updating the contract map object Revert build-system lavamoat policy changes Move token list selection logic from components to getTokenList selector updating the tokenList Update lavamoat Fix error updating lavamoat lint fix fix unit test fail fix unit test fail lint fix fixing rebase locale error rebase fix Revert build-system policy changes temp addressing review comments * rebase fix |
||
---|---|---|
.. | ||
address-entry | ||
connected-state | ||
custom-rpc | ||
custom-token | ||
eip-1559-v2 | ||
eip-1559-v2-dapp | ||
import-ui | ||
import-utc-json | ||
imported-account | ||
localization | ||
metrics-enabled | ||
navigate-transactions | ||
onboarding | ||
send-edit | ||
send-edit-v2 | ||
special-settings | ||
threebox-enabled | ||
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.json
file 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 callcopy
on the results
You can then paste the contents directly in your fixture file.
copy(await metamaskGetState())