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.
11979 Commits
2 Branches
1 Tag
200 MiB
 
 
 
 
 
Tag: Branch: Tree: c339f28ce8
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c339f28ce8'
${ noResults }
ciphermask/test/e2e/fixtures
History
Niranjana Binoy 966b2dcb43
Refactoring send-edit.spec.js to use fixtures (#10792) 		4 years ago
..
address-entry Refactoring address-book.spec.js to use fixtures (#10804) 4 years ago
connected-state Refactoring ethereum-on.spec.js to use fixtures (#10778) 4 years ago
imported-account Remove localhost provider type (#9551) 4 years ago
localization Remove localhost provider type (#9551) 4 years ago
metrics-enabled Add metrics e2e test (#9784) 4 years ago
send-edit Refactoring send-edit.spec.js to use fixtures (#10792) 4 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())