On Sun, 2012-07-29 at 20:52 -0400, Gavin Andresen wrote: > > Is there interest to port more tests (P2SH, checksig, checkmultisig, > > block verification, maybe even DoS rules) into data-driven format? It > > might be something that I'd like to help with if pull requests in that > > direction are welcome. > > Yes, more tests are definitely welcome. > > check*sig tests are tricky, because they have to refer to previous > unspent transactions and private keys (so require a particular block > chain to test against). Brilliant ideas on a simple data-driven format > welcome. > > block verification tests would be great; a collection of good/bad > block chains, starting from a common chain (maybe the testnet3 > tesnet-in-a-box chain) would be very useful for regression testing. >
I wrote a simple block chain tester (that is capable of forking, checking invalid blocks, etc) as a part of the bitcoinj test suite. Its more targeted at testing bitcoinj directly and keeping the bitcoinj test suite light weight, so if it were to be more generic some tweaks could be done (not requiring tweaking the minimum difficulty/genesis block hash/etc would be first). It doesn't have that many test cases yet, but it is capable of sanity-testing reorgs/etc. Its mostly the first two commits listed at http://code.google.com/r/bluemattme-bitcoinj/source/list?name=fullverif Matt ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
