Unit Tests

[ThePiachu]

As the scope of unit tests from
https://bitcointalk.org/index.php?topic=56095.0
was broadened, I created a new topic for various Bitcoin-related Unit Tests.

Here is the repository:
https://github.com/ThePiachu/Bitcoin-Unit-Tests

For now there are a few tests for ECDSA key pair generation, Address generation, and some Script tests to run, along with description of the files. Everything is in plain text for easy use and reading. All in all, something anyone wanting to develop their own Bitcoin code could use.

I intend on developing more tests soon, and hopefully testing those tests against other major Bitcoin applications. If you are a developer and you ran those tests, please let me know of the results - successfully running the test means my code runs well, failed tests may indicate my code is at fault .

[1714119828]

1714119828

[1714119828]

1714119828

[1714119828]

1714119828

[1714119828]

1714119828

[grau]

If you are a developer and you ran those tests, please let me know of the results - successfully running the test means my code runs well, failed tests may indicate my code is at fault .

Great work, thanks.
Would you mind using JSON format as do the unit tests for the Satoshi, BitcoinJ and bitsofproof implementations?

[behindtext]

As the scope of unit tests from
https://bitcointalk.org/index.php?topic=56095.0
was broadened, I created a new topic for various Bitcoin-related Unit Tests.

Here is the repository:
https://github.com/ThePiachu/Bitcoin-Unit-Tests

For now there are a few tests for ECDSA key pair generation, Address generation, and some Script tests to run, along with description of the files. Everything is in plain text for easy use and reading. All in all, something anyone wanting to develop their own Bitcoin code could use.

I intend on developing more tests soon, and hopefully testing those tests against other major Bitcoin applications. If you are a developer and you ran those tests, please let me know of the results - successfully running the test means my code runs well, failed tests may indicate my code is at fault .

glad to see someone talking about being proactive instead of reactive!

it is often ideal to have unit tests integrated into the main codebase so they can run when builds occur, but not all languages make this easy. i've gotten a lot of mileage out of using a post-commit hook with an automated build system, e.g. jenkins, for testing.