darkcoin testing questions

[darkred]

How do you run automated tests against darkcoin code base?
1. 'make check' fails (see below)
2. wallet.sh fails (see below)
3. Is there other automated tests somewhere?

1. make check output
pi@raspberrypi ~/darkcoin $ make check
Making check in src
make[1]: Entering directory '/home/pi/darkcoin/src'
Making check in .
make[2]: Entering directory '/home/pi/darkcoin/src'
make[2]: Leaving directory '/home/pi/darkcoin/src'
Making check in test
make[2]: Entering directory '/home/pi/darkcoin/src/test'
make check-am
make[3]: Entering directory '/home/pi/darkcoin/src/test'
make check-TESTS
make[4]: Entering directory '/home/pi/darkcoin/src/test'
Running 115 test cases...
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(121): error in "AlertApplies": check alert.CheckSignature() failed
alert_tests.cpp(127): error in "AlertApplies": check alerts[0].AppliesTo(1, "") failed
alert_tests.cpp(128): error in "AlertApplies": check alerts[0].AppliesTo(999001, "") failed
alert_tests.cpp(129): error in "AlertApplies": check alerts[0].AppliesTo(1, "/Satoshi:11.11.11/") failed
alert_tests.cpp(131): error in "AlertApplies": check alerts[1].AppliesTo(1, "/Satoshi:0.1.0/") failed
alert_tests.cpp(132): error in "AlertApplies": check alerts[1].AppliesTo(999001, "/Satoshi:0.1.0/") failed
alert_tests.cpp(134): error in "AlertApplies": check alerts[2].AppliesTo(1, "/Satoshi:0.1.0/") failed
alert_tests.cpp(135): error in "AlertApplies": check alerts[2].AppliesTo(1, "/Satoshi:0.2.0/") failed
alert_tests.cpp(171): error in "AlertNotify": check r.size() == 4u failed [0 != 4]
unknown location(0): fatal error in "AlertNotify": memory access violation at address: 0x00000000: no mapping at fault address
alert_tests.cpp(172): last checkpoint

*** 17 failures detected in test suite "Bitcoin Test Suite"
FAIL: test_darkcoin
=================================
1 of 1 test failed
Please report to [email protected]
=================================
Makefile:1105: recipe for target 'check-TESTS' failed
make[4]: *** [check-TESTS] Error 1
make[4]: Leaving directory '/home/pi/darkcoin/src/test'
Makefile:1228: recipe for target 'check-am' failed
make[3]: *** [check-am] Error 2
make[3]: Leaving directory '/home/pi/darkcoin/src/test'
Makefile:1230: recipe for target 'check' failed
make[2]: *** [check] Error 2
make[2]: Leaving directory '/home/pi/darkcoin/src/test'
Makefile:859: recipe for target 'check-recursive' failed
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory '/home/pi/darkcoin/src'
Makefile:435: recipe for target 'check-recursive' failed
make: *** [check-recursive] Error 1

2. I was trying to run the qa tests, but they fail.
pi@raspberrypi ~/darkcoin/qa/rpc-tests $ perl -p -i -e 's/bitcoind/darkcoind/g' *.sh
pi@raspberrypi ~/darkcoin/qa/rpc-tests $ perl -p -i -e 's/bitcoin-cli/darkcoin-cli/g' *.sh
pi@raspberrypi ~/darkcoin $ cd qa/rpc-tests/
pi@raspberrypi ~/darkcoin/qa/rpc-tests $ ./wallet.sh ../../src
Generating test blockchain...
bad balance: 500.00000000 (expected 50)
pi@raspberrypi ~/darkcoin/qa/rpc-tests $
pi@raspberrypi ~/darkcoin/qa/rpc-tests $ ps -ef | grep darkcoin
pi 4635 1 4 14:25 pts/0 00:00:03 ../../src/darkcoind -datadir=test.JMHdn/node1
pi 4637 1 12 14:25 pts/0 00:00:08 ../../src/darkcoind -datadir=test.JMHdn/node2
pi 4639 1 4 14:25 pts/0 00:00:02 ../../src/darkcoind -datadir=test.JMHdn/node3

 

[UdjinM6]

Yep, tests are mostly broken now. Just fixed few https://github.com/darkcoin/darkcoin/pull/200 but still more needed to be done.

ps. found a small bug tnx to you https://github.com/darkcoin/darkcoin/pull/199

 

[crowning]

Yep, tests are mostly broken now.

Crowning's second law of software testing: when an active software project is older than one year and a test fails, the chances that the test is broken converges to 100%.

 

[UdjinM6]

Crowning's second law of software testing: when an active software project is older than one year and a test fails, the chances that the test is broken converges to 100%.

They were basically left behind on our move to 0.9 bitcoin core, so they are quite fresh but written for bitcoin :grin: I fixed few simple ones, but few still left broken: alert test require someone who hold an alert private key to make test data eduffield subsidy and miner test... well, they don't really make sense imo - you can just run regtest mode... but if anyone feel all test must be fixed - you are welcome to help :wink:

 

[vertoe]

They were basically left behind on our move to 0.9 bitcoin core, so they are quite fresh but written for bitcoin :grin: I fixed few simple ones, but few still left broken: alert test require someone who hold an alert private key to make test data eduffield subsidy and miner test... well, they don't really make sense imo - you can just run regtest mode... but if anyone feel all test must be fixed - you are welcome to help :wink:

exactly. these were the last on my TODO-list of the new 0.11 core release but evan pulled the trigger faster than expected and i never looked into my list again. the tests mentioned in OP were not ported yet since the current client is only 2 months old. Will dig into them later on.