1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-12-01 21:57:06 +01:00
metamask-extension/test/e2e/fixtures
2021-05-31 17:31:23 -02:30
..
address-entry Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
connected-state Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
import-ui Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
imported-account Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
localization Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
metrics-enabled Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
onboarding Version v9.5.0 RC (#10944) 2021-05-05 11:08:59 -07:00
send-edit Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
threebox-enabled Revert "Revert "Adding "What's New" notification for Ledger Support Update (#11188)"" 2021-05-31 17:31:23 -02:30
README.md Allow exporting state during e2e tests (#7860) 2020-01-17 18:59:25 -04:00

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())