New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
run automated tests for libsnark, libzerocash, and zerocashd #78
Comments
Here is the upstream bitcoin's README.md Testing section which describes how to run tests. To execute unit tests: make check |
Should we rename this ticket to be specific to "automated tests" or "unit tests"? I'm interested in deterministic tests which tell the user "success" or "failure" without much other noise, which makes it easy to quickly spot regressions. This would be in contrast to tests as in #71 which require a fair amount of user involvement. |
|
This may be a known error. Remember, libbitcoin_common should not compile period because of alterations I made in Script.cpp that depend on libzerocash functions. , while libzerocash is linked when you compile bitcoind, I at least never tried to get it to link into libbitcoin_common. Ian
|
Just noticed this old ticket. Current status:
|
I believe @ebfull removed The status for self-hosted buildbot is as per my last comment here, except it's executed by buildbot (thus no "artificial" time/memory restrictions). |
We are testing libzerocash and zerocashd. I'll open another ticket for CI testing of libsnark. |
[Softfork] BIP Implementation for TX Replay Protection and BIP 9 implementation
Build fix win32 linux
Run automated tests for libsnark, libzerocash, and zerocashd; make sure that they pass before doing anything else.
The text was updated successfully, but these errors were encountered: