monzero-core.git/tests, branch v0.9.0Monzero core node, command-line wallet, consensus code, and release tooling.
https://code.monzero.org/monzero-core.git/atom?h=v0.9.02015-12-31T06:39:56Zupdated copyright year2015-12-31T06:39:56ZRiccardo Spagniric@spagni.net2015-12-31T06:39:56Zurn:sha1:de0392685063d93dbdad3a6b1a2712eaf94dd51aMerge pull request #5802015-12-31T06:18:27ZRiccardo Spagniric@spagni.net2015-12-31T06:18:27Zurn:sha1:be7a93f51fbfb4687ebb9cb0a327fd033f796f2a
1813736 unit_tests: remove an unused variable (moneromooo-monero)
70dd346 unit_tests: fix hardfork test build (moneromooo-monero)
unit_tests: remove an unused variable2015-12-30T17:30:54Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T17:30:54Zurn:sha1:18137365627bd1f30bc59755ac2614bdd11aaa44unit_tests: fix hardfork test build2015-12-30T17:30:01Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T17:30:01Zurn:sha1:70dd34634cd20c19ede2eb1d19fa2419aa760e56
The dummy blockchain class needed to have the newly added
is_read_only virtual function.
core_tests: deinit core before destroying it2015-12-30T16:05:52Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-30T16:05:52Zurn:sha1:b2452151931ffe98337181567aaf797c1f530c3f
This fixes a use after free by ioservice threads
tests: add a unit test for canonical decomposed amounts2015-12-26T11:41:50Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-26T11:41:50Zurn:sha1:b90e14d9274aac4fb01f8eb14a97333a1fd3af7dtests: fix various tests by using parameters better suited to monero2015-12-25T22:26:34Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:26:34Zurn:sha1:79beed221d9b3842b652587b5eaeed17423bd9de
Either smaller coin values (as monero has smaller block rewards),
or pre-hard fork values (full reward zone), or post-Bytecoin values
(emission speed).
tests: fix some double spending tests2015-12-25T22:23:36Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:23:36Zurn:sha1:d0a8362b6bceeb9f99ee29360c84ce49db9904d1
Some tests assume the first output in a transaction goes to the recipient.
However, it can be the change. When it is, the recipient's keys will not
recognize this output. To fix this, we send all we have, to ensure there
is no change, and the first output goes to the recipient.
I'm not sure why this worked with Cryptonote. The tests sent 17 coins,
which seems way smaller than the first Bytecoin block reward, so there
would have been change too. Maybe outputs were not shuffled originally.
tests: use 255 as a "too high" block version2015-12-25T22:22:12Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:22:12Zurn:sha1:2358d0d5be34f8dca0c14f94979300ed49e3f29f
While the original cryptonote accepted only the current major
version, we can accept higher ones.
blockchain: fix bitflipping test with quantized block rewards2015-12-25T22:07:58Zmoneromooo-moneromoneromooo-monero@users.noreply.github.com2015-12-25T22:07:58Zurn:sha1:81cb0fcdccf08afd6f37d21ccfefb31131fd3950
Block reward may now be less than the full amount allowed.
This was breaking the bitflipping test.
We now keep track of whether a block which was accepted by the core
has a lower than allowed block reward, and allow this in the test.