Blockchain Testing Methodology

What is Blockchain?

The world these days is about virtual, digital, and cryptocurrencies in different shapes and sizes (read as rates and valuation respectively) that heavily rely on technology. Blockchain is a distributed ledger, which is validated among different business peers. This ledger further acts like an immutable audit log.

Image courtesy of testingxperts.com

Blockchain Feature

BLOCKCHAIN LEDGER	Value
Decentralized	Trust
Immutability	Auditability
Consensus Mechanism	Security
Smart Contracts	Automation
Fault Tolerant	Availability

Different Types of Blockchain

Public	Consortium	Private
Public, Permission less Blockchain	Federated, Permissioned Blockchain(Single or Multi-Industry)	Private, Permissioned Blockchains
Allow access to any user at any time, ledger management is facilitated by the distributed network (e.g. Bitcoin, Ethereum)	Allow access to users based on the rules defined by the group of entities (consortium) participation in the network, ledger management is facilitated by the consortium (e.g., Ripple, R3, Corda	Allow access to users based on the permission set by the private network, ledger management is facilitated by single company for private use (e.g., Chain, Supplychain, Bankchain)
	Permissioned by many	Permissioned by one

What does it mean for testing?

Challenges in Testing the Blockchain

• Understating the technology Blockchain is a relatively new technology
• Lack of Blockchain Testing Tools Picking up the right tool as per the application is a crucial decision
• Lack of Best Practices New Technology, lack of experience to test blockchain application
• Defining the Test Strategy Requires a deep understanding of the application
• Addition of Blocks Validate all the blocks that get added to the chain post authentication of every transaction
• Block and Chain size A block contains real-time ledger record with encryption and timestamp The chain size can be many blocks as the chain lengthens
• Transmission of Crypto-Graphical Data
• Integration Testing The key responsibility is to ensure that the response from all interfaces is consistent and there are no disconnects
• Security Testing Human-related risks Risks with private and public key Vendors Risks and Untested code Lack of Standards and Regulation
• Performance and Load Testing Focus on: Network latency Performance bottlenecks The sequence of transaction at every node Transaction processing speed Client/User and system interface The responses required from the smart contracts

Why existing Testing solutions are inadequate?

To the best of our knowledge there is no defined process or approach used for testing Blokchain solutions that covers all the dimensions or complexities of Blockchain implementations.

Adhoc testing methodologies an processes are used that may leave Blockchain systems immune to defects and production failures. Our proprietary methodology covers all the aspect of testing requirement for a production grade implementation.

Testing approach should not be platform specific. Client's solutions which are built on existing blockchain platforms should not focus extensively on technical features which are applicable for the specific platform. For example, the way a DLT platform stores users' credentials is not something that need to be tested. It's the platform's responsibility to provide these kind of warranties for their software. However, when using 100% open source platforms we do need to do this level of testing.

Testing Decentralized Solutions

Traditional V-Model Test

Adopted for Blockchain (Verification and Testing)

Blockchain Ecosystem

Elements that should be considered while planning the QA approach:

1.Standard Testing & Validation

• Functional Testing Testing of individual components and system including User Acceptance Testing
• Integration Testing Interfaces between components and different parts of the system which can be on different environment

2.Non-Function Testing

• Security Testing Testing for confidentiality, integrity, authentication, access, and authorization are critical components of security
• Performance Testing The performance and latency vary with the size of network and size of transactions

3.Testing specific to Blockchain

• Peer/Node Testing The strength of the blockchain lies in having the shared ledger be exactly the same at each and every node
• Smart Contract Testing Software modules on the blockchain that automatically execute transactions based on pre-defined conditions.

Blockchain Testing Considered (Specific in the Blockchain solution testing to be considered.)

Blockchain Transactions

• Transaction processing Validation of transaction lifecycle through Apps / Vaults / Wallets
• Transaction State / Event Proof of distribution Basic data model for Blockchain Validation of event notification
• Vault / Wallet Validation of Transactions message verification (signing) Common trusted database Storage algorithm Extensive testing of wallets or hashing algorithms in enterprise blockchain would be more required on 100% open source / permission less solutions

Blockchain Governance

• History & Audit Validation of secure registry and audit of transaction Immutable record Secure Identifications of assets
• Consensus Mechanism Consolidated consistent dataset Various consensus models (PoW, PoS, Byzantine FT) Transaction timestamping
• Smart Contract Validation of business rules through Smart Contracts: Self-enforcing contracts Digitized analog contracts Real-time auditing of transactions

Blockchain Platform

• Interaction with APIS Validation of interface with API's for access control payments, track and trace and balances.
• ** Key & Identify Services** Consortium or private blockchains Public blockchains Validation of tokenization of assets
• Blockchain Applications Web Application Native Application Wallet / Vault Applications

Blockchain testing part of a knowledge sharing platform to leverage up to date information about blockchain and QA. Leverage testing methods and techniques that has been generally accepted and proven in real project. Collaboration between business, developers and QA teams to achieve best possible result.

Reference: https://community-z.com/events/qa-z-days-2020/talks/3929