https://github.com/onekeyhq/test-dapp
https://github.com/onekeyhq/test-dapp
Last synced: 12 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/onekeyhq/test-dapp
- Owner: OneKeyHQ
- License: mit
- Archived: true
- Created: 2021-08-16T13:01:13.000Z (over 4 years ago)
- Default Branch: master
- Last Pushed: 2023-03-06T08:22:26.000Z (about 3 years ago)
- Last Synced: 2025-02-26T01:43:32.892Z (about 1 year ago)
- Language: JavaScript
- Size: 2.89 MB
- Stars: 1
- Watchers: 15
- Forks: 1
- Open Issues: 13
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# OneKeyHQ Test Dapp
This is a simple test dapp for use in OneKeyHQ e2e tests and manual QA.
Currently hosted [here](https://onekeyhq.github.io/test-dapp/).
## Usage
If you wish to use this dapp in your e2e tests, install this package and set up a script of e.g. the following form:
```shell
static-server node_modules/@onekeyhq/test-dapp/dist --port 9011
```
## Contributing
### Setup
- Install [Node.js](https://nodejs.org) version 12
- If you are using [nvm](https://github.com/creationix/nvm#installation) (recommended) running `nvm use` will automatically choose the right node version for you.
- Install [Yarn v1](https://yarnpkg.com/en/docs/install)
- Run `yarn setup` to install dependencies and run any requried post-install scripts
- **Warning:** Do not use the `yarn` / `yarn install` command directly. Use `yarn setup` instead. The normal install command will skip required post-install scripts, leaving your development environment in an invalid state.
### Testing and Linting
Run `yarn lint` to run the linter, or run `yarn lint:fix` to run the linter and fix any automatically fixable issues.
This package has no tests.
### Deploying
After merging or pushing to `main`, please run `yarn deploy` in the package root directory if the contents of the `dist/` directory have changed.
### Development
#### Elements Must Be Selectable by XPath
All HTML elements should be easily selectable by XPath.
This means that appearances can be misleading.
For example, consider this old bug:
```html
Approve Tokens Without Gas
```
This appears on the page as `Approve Tokens Without Gas`. In reality, the value included the whitespace on the second line, and caused XPath queries for the intended value to fail.