A Metamask fork with Infura removed and default networks editable
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.
 
 
 
 
 
ciphermask/test/e2e/fixtures
Dan Miller 7365f87f9e Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
..
address-entry Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
connected-state Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
import-ui Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
imported-account Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
localization Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
metrics-enabled Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
onboarding Version v9.5.0 RC (#10944) 4 years ago
send-edit Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
threebox-enabled Revert "Adding "What's New" notification for Ledger Support Update (#11188)" 4 years ago
README.md Allow exporting state during e2e tests (#7860) 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:

  1. 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:

  1. Load the unpacked extension in development or test mode
  2. Inspecting the background context of the extension
  3. Call metamaskGetState, then call copy on the results

You can then paste the contents directly in your fixture file.

copy(await metamaskGetState())