Learn About Blockchain Quality Assurance

Posted By Abhimanyu Garg | 27-Apr-2018

Blockchain technology set the new breakthrough in the path of conducted today businesses on the base of Promise of secure, decentralized peer to peer trust network, smart contracts, and distributed ledger. Before starting the testing of blockchain-based applications we need to analyze the different validation and verification methods and pointers.

Knowledge of Blockchain – The Tester should have knowledge of different blockchain technologies and frameworks. They should understand the basic algorithms of cryptographic and consensus protocols.

P2P Networking Testing – Need to prepare the three-dimensional aspects of P2P systems: Functionality, scalability, and volatility. Instead of that, Tester needs to prepare test coverage for the following components of the network:
1. Nodes:
 a) Verify all nodes are up and running.
 b) Data should be same at all the nodes after propagation of data.
 c) Nodes sending data simultaneously to the other nodes.
 d) Verify able to add a new node to the network.
 e) Verify able to remove a node from the network.
 f) Shared ledger same at each and every node after data diffusion.
 g) Verifying Address of node.
 h) Get the address/secret keys from all the nodes and save it.

2. Data Transmission in the network:
 a) Check all node receives the data and verify if the data store is updated in either in chronological order or not.
 b) Start propagating data from two more nodes at the same time and verify the data store of all the other nodes.


3. Test Network Types:
 a) Public - Anybody can access the ledger and see transactions.
 b) Private - Only selected users are able to access the ledger and see transactions.
 c) Read/Write permission - Verify who can take part in making changes to a distributed ledger (e.g., who can add blocks to a blockchain).
 d) Permissionless (open): To define the certain user level permission to participate in the general agreement process (in practice, however, often limited by resource requirements such as owning suitable hardware or cryptocurrency).
 e) Permissioned (closed) - Only selected parties can make changes to the distributed ledger.


Nonfunctional Testing — Performance and latency can vary based on network size and transaction load. Testing for multi-layered security system on the network and privacy of data in the ledger based on selective permissions is also required.

Request for Proposal

Recaptcha is required.

Sending message..