1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-12-02 06:07:06 +01:00
metamask-extension/test/e2e/fixtures
2021-04-22 14:03:47 -04:00
..
address-entry Refactoring address-book.spec.js to use fixtures (#10804) 2021-04-02 22:40:53 -04:00
connected-state Refactoring ethereum-on.spec.js to use fixtures (#10778) 2021-03-31 13:06:44 -04:00
import-ui Refactoring from-import-ui.spec.js to use fixtures (#10907) 2021-04-22 14:03:47 -04:00
imported-account Remove localhost provider type (#9551) 2020-10-12 12:05:40 -07:00
localization Remove localhost provider type (#9551) 2020-10-12 12:05:40 -07:00
metrics-enabled Add metrics e2e test (#9784) 2020-12-01 17:54:56 -03:30
onboarding Refactoring metamask-responsive-ui.spec.js to use fixtures (#10866) 2021-04-15 09:58:51 -04:00
send-edit Refactoring send-edit.spec.js to use fixtures (#10792) 2021-04-04 15:06:26 -04:00
threebox-enabled Refactoring threebox.spec.js to use fixtures (#10849) 2021-04-08 19:53:18 -04:00
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())