mirror of
https://github.com/kremalicious/metamask-extension.git
synced 2024-12-12 12:47:14 +01:00
0b4532ec1b
* remove state.json files * move file * Update Readme * Create fixture builder * load test fixture * remove redundant method * update snap tests * update stats tests * update extension tests * update extension tests * Update fixture data * snap test dapp connection * Update fixture data * add onboarding fixture * use onboarding fixture * reuse import account vault * remove unnecessary use of class * use fixture builder in new tests * switch to function * update default fixture * update default fixture * update test * update 1559 test fixttures * update 1559 test fixtures * update 1559 test fixtures * dismiss 3box whats new * remove redundant code * move docs * remove unused code * token detection * use default timeout * remove redundant code * Update fixture builder hide `Protect your funds` dialog remove browser environment remove default network details hide dismiss seed backup reminder recursively merges fixture data * add token to tokencontroller * remove network details * add missing identities to preference controller * remove duplicate properties * update bip-32 to use fixturebuilder * alphabetise snap permissions * update get snaps to use fixturebuilder * Update test-snap-bip-32.spec.js wait for window * add popular network state * update test * lint
17 lines
451 B
Markdown
17 lines
451 B
Markdown
## 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`][1] on the results
|
|
|
|
You can then paste the contents directly in your fixture file.
|
|
|
|
```js
|
|
copy(await metamaskGetState())
|
|
```
|
|
|
|
|
|
[1]:https://developers.google.com/web/tools/chrome-devtools/console/utilities
|