From: Gavin Andresen <gavinandresen@gmail.com>
To: Stefan Thomas <moon@justmoon.de>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] script tests - invalid script in script_valid.json?
Date: Sun, 29 Jul 2012 20:52:28 -0400 [thread overview]
Message-ID: <CABsx9T016OmU2qU1a67=YmpA4VDbzrddOamc8=Mt6x7BhVO1Uw@mail.gmail.com> (raw)
In-Reply-To: <50157450.8070806@justmoon.de>
> 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.
--
--
Gavin Andresen
next prev parent reply other threads:[~2012-07-30 0:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-29 16:31 [Bitcoin-development] script tests - invalid script in script_valid.json? Amir Taaki
2012-07-29 16:33 ` Stefan Thomas
2012-07-29 16:42 ` Amir Taaki
2012-07-29 17:35 ` Stefan Thomas
2012-07-29 18:48 ` Jeff Garzik
2012-07-30 0:52 ` Gavin Andresen [this message]
2012-07-30 14:41 ` Amir Taaki
2012-07-31 14:26 ` Pieter Wuille
2012-07-31 14:39 ` Matt Corallo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABsx9T016OmU2qU1a67=YmpA4VDbzrddOamc8=Mt6x7BhVO1Uw@mail.gmail.com' \
--to=gavinandresen@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=moon@justmoon.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox