zingolib
zingolib copied to clipboard
Test Infrastructure Upgrade, port lib-to-node tests to lib-to-darkside
Setup
Ordered Set of Tasks:
Ensure that you can run these tests:
-
https://github.com/zingolabs/zingolib/blob/dev/integration-tests/tests/integrations.rs
-
https://github.com/zingolabs/zingolib/tree/dev/darkside-tests/tests
-
Rename this directory https://github.com/zingolabs/zingolib/tree/dev/integration-tests TO: "lib-to-node-tests"
-
Rename this directory https://github.com/zingolabs/zingolib/tree/dev/darkside-tests TO: "lib-to-darkside-tests"
Create darkside-parity-tests
Start with the test that you understand best. Best Understood Test (BUT)
For each test in the "lib-to-node-tests":
- create a new test in "lib-to-darkside" with the same name
- make the new test in "lib-to-darkside" validate all of the same behavior as the original test, it should make the same assertions in the same order. If the original test should have more assertions, then add them!
This issue is complete when every test in lib-to-node has a darkside-parity test that performs the same lightclient-behavior-validation as the original test.
There should be (at least initially), a single PR for each test that is ported.