mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-11-23 18:41:38 +01:00
7db5d9e527
The fixture server now supports state substitutions. This allows us to embed dynamic values in our fixtures. The `custom-token` fixture has been updated to include such a fixture. The date that the seed phrase reminder was last shown has been updated to always be the current date, to prevent the reminder from showing up during e2e tests. This fixes the e2e test failure for the test "add-hide-token.spec.js" that we've been seeing on CI lately. |
||
|---|---|---|
| .. | ||
| address-entry | ||
| connected-state | ||
| custom-rpc | ||
| custom-token | ||
| import-ui | ||
| imported-account | ||
| localization | ||
| metrics-enabled | ||
| navigate-transactions | ||
| onboarding | ||
| send-edit | ||
| 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.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())