1
0
mirror of https://github.com/kremalicious/metamask-extension.git synced 2024-11-22 18:00:18 +01:00
metamask-extension/test/e2e/fixtures
Mark Stacey 3a2c81d8bc
Switch signature-request e2e tests to using ganache (#7859)
The signature request e2e tests were previously using ropsten. This
expectation was even hard-coded into the test contract dapp.

Instead the contract-dapp has been updated to use the current `chainId`
when calling `signTypedData` (falling back to the `networkId` if
`chainId` is not set). The fixture used by `signature-request` has been
updated to use ganache.
2020-01-17 18:16:21 -04:00
..
imported-account Switch signature-request e2e tests to using ganache (#7859) 2020-01-17 18:16:21 -04:00
README.md End-to-end test state fixtures (#7663) 2019-12-11 09:26:20 -08: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 loading the unpacked extension, inspecting the background context, dumping chrome.storage.local, and using copy to copy it to the clipboard, and manually pasting the contents into a file on disk.

// Step 1:
chrome.storage.local.get(null, (x) => console.log(x))
// Should print something like:
// > temp1
// > {data: {…}, meta: {…}}

// Step 2:
// Store the value as a global via the 'Store as global variable' option in context menu (shown below)

// Step 3:
copy(temp1)

Store the value as a global variable:

Store as global variable