Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 1.38 KB

README_DEV.md

File metadata and controls

39 lines (26 loc) · 1.38 KB
Raw

For Developers

Tests and coverage report

Deployment to PyPI

  • Update VERSION constant on top of setup.py file to vX.Y.Z, where X, Y, Z are some integers specifying the new version of the package;
  • Create Git tag with the same version name vX.Y.Z;
  • Push the tag to laser-ethereum repo, CircleCI will take care about the rest (testing, and deployment to PyPI if tests are successful).

In case of mismatch between Git tag and VERSION in CircleCI deployment will be failed.

python version

First, make sure your python version is 3.6.x. Some tests will fail with 3.5.x since some generated easm code is different from 3.6.x.

Run tests:

pip3 install -r requirements.txt
./all_tests.sh

The tests may save their outputs content to ./tests/testdata/outputs_current/, you can compare the files between it and ./tests/testdata/outputs_expected/ to see the difference if there is any changes.

If you think the changes are expected, you can just copy them to outputs_expected and commit them as new expected outputs.

The ./tests/testdata/outputs_current/ directory is deleted and recreated in all_tests.sh and coverage_report.sh each time.

Generate coverage report:

./coverage_report.sh

It will generate the coverage report in ./coverage_html_report/index.html, and which will be automatically opened in browser.