TheDude
/
ciphermask
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
A Metamask fork with Infura removed and default networks editable
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
13129 Commits
2 Branches
1 Tag
200 MiB
 
 
 
 
 
Tag: Branch: Tree: 64e4ce19bc
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '64e4ce19bc'
${ noResults }
ciphermask/test/e2e/fixtures
History
Mark Stacey 7db5d9e527
Add fixture server substitutions (#12476) 		3 years ago
..
address-entry Removing obsolete client-side transaction metrics events (#11329) 3 years ago
connected-state Removing obsolete client-side transaction metrics events (#11329) 3 years ago
custom-rpc Removing obsolete client-side transaction metrics events (#11329) 3 years ago
custom-token Add fixture server substitutions (#12476) 3 years ago
import-ui Replace hardcoded sent ether label on confirm screen (#11802) 3 years ago
imported-account removing the icronUrl in tokens fron the state.json for fixtures (#12309) 3 years ago
localization Removing obsolete client-side transaction metrics events (#11329) 3 years ago
metrics-enabled Removing obsolete client-side transaction metrics events (#11329) 3 years ago
navigate-transactions removing the icronUrl in tokens fron the state.json for fixtures (#12309) 3 years ago
onboarding Refactoring metamask-responsive-ui.spec.js to use fixtures (#10866) 4 years ago
send-edit Replace hardcoded sent ether label on confirm screen (#11802) 3 years ago
threebox-enabled Removing obsolete client-side transaction metrics events (#11329) 3 years ago
README.md Allow exporting state during e2e tests (#7860) 5 years ago

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:

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