Topic: Bitcoin Quality Assurance (Read 945 times)

Sometimes I am blown away by how thorough Pieter Wuille is ...

https://github.com/bitcoin/bitcoin/pull/6954#issuecomment-167126321

For all of the above, we have: * High test coverage (the only missing parts are cryptographically improbable to reach ones). * Hand verifiable proof of correctness for the field multiplication algorithm (provably no overflow, and provably equivalent to the correct response assuming no overflow). * Computer verified proof of correctness for group addition formulae (computer algebra system can prove polynomial equivalence between implementation and mathematical expressions for the result). * Special compilable mode that changes a constant to end up with a very small group, and exhaustive tests that all assumptions remain true (in progress, by Andrew Poelstra). * Test cases for the scalar code that were extracted from a set of 1 trillion randomly generated tests which give very high coverage, and work in progress to algebraically derive cases that trigger the (nearly) unreachable remaining ones. Furthermore: * An old build mode which used OpenSSL's bignum code for integer operations helped discover a bug in OpenSSL square code (CVE-2014-3570). * During tested we discovered an platform inconsistency in OpenSSL's signature parsing code (fixed by BIP66). * Our ECDSA signature fuzzer pointed out several types of previously unknown invalid signature types that OpenSSL accepted (discovered after BIP66 took effect).

Yes. For every single feature that gets added there are tests for it. Anything new pull request for a feature that does not have a test is not merged until the person who opened the request creates tests for it. It is quite thorough.

Has the bitcoin been tested throughly?

Yes exactly Bitcoin is more secure than any other crypto and they are doing there best to keep the scammers at the bay.

Testing is an important aspect of any Software Development Methodology .If you would you read about testing we have different types of testing conducted on different application models:

Unit Testing : Refers to test which are conducted on all the units as one.For example,entire block is being tested as one unit or entire chain is tested as one unit.We have to write the test cases to check if the software or application we're writing will be efficient to all the number of inputs by the users.

Consider a simple example of a calculator : We write a program to add two numbers .Now we will conduct different test cases with n number of inputs like adding two positive numbers/adding two negative numbers/adding a fraction and check in all those scenarios if we're getting the accurate answers from the program.If particular test is unsatisfied we can go ahead and improve the code.

We also perform black box /white box testing on various modules.Its interesting to learn.You could google these concepts .

This is part of the reason why I trust bitcoin more than almost all altcoins (where extensive QA and edge case scenarios are not considered).

The more QA the better.

Some useful links:

https://en.m.wikipedia.org/wiki/Edge_case

https://en.m.wikipedia.org/wiki/Corner_case

http://www.cs.cmu.edu/~rjsimmon/15122-s13/rec/07.pdf

:-)

Part of the QA is the testing to make sure that the software does what it is supposed to. Valid inputs produce valid results and invalid inputs produce invalid results. The test cases are usually a couple of scenarios that are supposed to work and some that aren't. If the software is doing everything correctly, then the ones that should work will work and the ones that shouldn't won't work.

Edge cases would be scenarios that include something completely absurd that normally wouldn't happen but could happen. Those cases still need to be considered as part of the testing in the off chance that someone does something incredibly stupid to cause those cases to happen.

Unit testing just means testing specific functions of the program individually.

A test plan is basically the plan for testing a certain function. It includes the starting point, what you do, and what to expect. A test scenario is pretty much the same thing but I think it also includes the code implementation for the test.

While looking through the Bitcoin Github I stumbled across this page about Bitcoin Quality Assurance.

https://github.com/bitcoin/QA/

After some Googling I discovered that as part of Quality Assurance Bitcoin has Unit testing conducted on its code, and Edge cases are considered.

In simple terms what is Unit testing, and what are Edge cases?

Some other terms I don't understand concern writing test plans, writing test scenarios, and critical path testcases?

What do those terms mean, and what are they used for?