eth2.0-specs/test_libs/pyspec
Michael Sproul cc5b172da3 Test deposit top-up with inconsistent withdrawal credentials (#1133)
* Simplify deposits

* Avoid divisions by zero

Possible fix to avoid four cases of divisions by zero:

* `return state.validator_registry[index].effective_balance // adjusted_quotient // BASE_REWARDS_PER_EPOCH`
* `rewards[index] += get_base_reward(state, index) * attesting_balance // total_balance`
* `validator.effective_balance * min(total_penalties * 3, total_balance) // total_balance`
* `rewards[index] += base_reward * attesting_balance // committee_balance`

See also #1107.

* fix deposit test for new index handling

* tests: deposit with inconsistent withdrawal credentials

* Update README.md

* Update 0_beacon-chain.md

* Fix linter errors

* Update test_process_deposit.py

* fix deposit test

* fix lint
2019-05-29 20:38:55 -06:00
..
eth2spec Test deposit top-up with inconsistent withdrawal credentials (#1133) 2019-05-29 20:38:55 -06:00
tests fix deposit test for new index handling 2019-05-27 16:40:00 -06:00
README.md Merge branch 'dev' into v06x-to-dev 2019-05-27 11:09:52 -06:00
requirements-testing.txt Revert "Only use `setup.py`" 2019-04-24 11:59:13 -06:00
requirements.txt Revert "Only use `setup.py`" 2019-04-24 11:59:13 -06:00
setup.py Revert "Only use `setup.py`" 2019-04-24 11:59:13 -06:00

README.md

Eth 2.0 Executable Python Spec (PySpec)

The executable Python spec is built from the Eth 2.0 specification, complemented with the necessary helper functions for hashing, BLS, and more.

With this executable spec, test-generators can easily create test-vectors for client implementations, and the spec itself can be verified to be consistent and coherent through sanity tests implemented with pytest.

Building

All the dynamic parts of the spec can be build at once with make pyspec.

Alternatively, you can build a sub-set of the pyspec: make phase0.

Or, to build a single file, specify the path, e.g. make test_libs/pyspec/eth2spec/phase0/spec.py.

Py-tests

After building, you can install the dependencies for running the pyspec tests with make install_test.

These tests are not intended for client-consumption. These tests are sanity tests, to verify if the spec itself is consistent.

How to run tests

Automated

Run make test from the root of the specs repository.

Manual

From within the pyspec folder:

Install dependencies:

python3 -m venv venv
. venv/bin/activate
pip3 install -r requirements-testing.txt

Note: Make sure to run make -B pyspec from the root of the specs repository, to build the parts of the pyspec module derived from the markdown specs. The -B flag may be helpful to force-overwrite the pyspec output after you made a change to the markdown source files.

Run the tests:

pytest --config=minimal eth2spec

Note the package-name, this is to locate the tests.

Contributing

Contributions are welcome, but consider implementing your idea as part of the spec itself first. The pyspec is not a replacement.

License

Same as the spec itself; see LICENSE file in the specs repository root.