Skip to content

Latest commit

 

History

History
 
 

06-ethersjs-waffle

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
contract
contract
 
 
test
test
 
 
.env.example
.env.example
 
 
README-cn.md
README-cn.md
 
 
README.md
README.md
 
 
index.js
index.js
 
 
package.json
package.json
 
 
waffle.json
waffle.json
 
 

README.md

中文 / English

Preface

Waffle is a smart contract test library that adapts to ehter.js. This example demonstrates the basic process and usage of Waffle test. You can refer to the offical website of Waffle width the detailed usage(https://ethereum-waffle.readthedocs.io/en/latest/getting-started.html).If you are a developler not familiar with Waffle, you could read the sample code and do exercises, then refer to the official website for a more in-depth understanding.

Contracts Introduction

  • contract/SimpleToken.sol A standard ERC20 contract that implements all interface of ERC20. Users could issue ERC20 tokens using this contract. �

Scripts Introduction

  • test/simpleTokenTest.js The unit test code of SimpleToken.sol contract. There is only one test script here, you could write multiple scripts of unit test codes for different contracts under the "test" directory during the development. Each interface of SimpleToken.sol contract will be simplely tested in the simpleTokenTest.js script.You can refer to the sample to write unit test codes of other contracts.

  • index.js External contracts needs to be invoked separately. When unit test is passed, the script could be called to generate some actions in the production environment.

steps

  • 1 install dependencies
yarn install
  • 2 compile contracts
yarn build
  • 3 config environment variables
cp .env.example .env

## modify PRIVATE_KEY and INFURA_ID in .env
  • 4 Test Execution
yarn test
  • 5 test index.js
node index.js

Note

when it hint that "cannot find yarn commands"(when running on VMWare), you can try:

  1. $ sudo wget https://dl.yarnpkg.com/rpm/yarn.repo -O /etc/yum.repos.d/yarn.rep
  2. $ sudo yum install yarn

check yarn version $ yarn --versionyarn --version

  • If run yarn test on windows, you should change the "export" keyword to the "set" keyword in the "test" command of the "scripts" key of the file named package.json

Before changed:

  "scripts": {
    "build": "waffle",
    "test": "export NODE_ENV=test && mocha --timeout 10000"
  },

afer changed:

  "scripts": {
    "build": "waffle",
    "test": "set NODE_ENV=test && mocha --timeout 10000"
  },

Reference document