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.
15063 Commits
2 Branches
1 Tag
200 MiB
 
 
 
 
 
Tag: Branch: Tree: d0adb5f697
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'd0adb5f697'
${ noResults }
ciphermask/test/e2e/fixtures
History
ryanml 7b04bf8b47
Adding Sepolia as a default test network (#15787) 		2 years ago
..
address-entry Adding Sepolia as a default test network (#15787) 2 years ago
connected-state Adding Sepolia as a default test network (#15787) 2 years ago
custom-rpc Adding Sepolia as a default test network (#15787) 2 years ago
custom-token Show 3box deprecation message in whats new (#15763) 2 years ago
eip-1559-v2 Adding Sepolia as a default test network (#15787) 2 years ago
eip-1559-v2-dapp Adding Sepolia as a default test network (#15787) 2 years ago
import-ui Show 3box deprecation message in whats new (#15763) 2 years ago
import-utc-json e2e test import json file as import account strategy (#14449) 3 years ago
imported-account Adding Sepolia as a default test network (#15787) 2 years ago
localization Adding Sepolia as a default test network (#15787) 2 years ago
metrics-enabled Adding Sepolia as a default test network (#15787) 2 years ago
navigate-transactions Adding Sepolia as a default test network (#15787) 2 years ago
onboarding Show 3box deprecation message in whats new (#15763) 2 years ago
send-edit Adding Sepolia as a default test network (#15787) 2 years ago
send-edit-v2 Adding Sepolia as a default test network (#15787) 2 years ago
special-settings Adding Sepolia as a default test network (#15787) 2 years ago
threebox-enabled Show 3box deprecation message in whats new (#15763) 2 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())