DEV Community: Hirok Sarker

Blockchain Testing Methodology

Hirok Sarker — Mon, 31 May 2021 12:47:25 +0000

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

Extract All of Regular-Expression matches from html page using JMeter

Hirok Sarker — Fri, 22 May 2020 14:29:03 +0000

All are well known about JMeter Regular Expression Extractor but today I will share with how to extract all the matches from HTML page and print those value comma(,) separated.

JMeter, the most popular open source performance testing tool, can work with regular expressions, with the Regular Expression Extractor. Regular expressions are a tool used to extract a required part of the text by using advanced manipulations. Regular expressions are popular when testing web applications because they can be used to validate and to perform operations on a response from a web application.

In this article, I’m going to share how to use extract all of Regular Expression Extractor matches form html in JMeter.

I created a very simple test-plan, look at Figure 1:

Figure 2:
Sampler HTTP Request

Figure 3:
Debug PostProcessor - To check total matchNr and value represent a pattern.

Figure 4:
After extracting ids it will be put to BeanShell PostProcessor

Of course, I cannot cover in one article all possible and impossible cases about using regular expressions. For more information you can refer to JMeter Regular Expressions Tutorial (https://jmeter.apache.org/usermanual/regular_expressions.html) which has exhaustive information.

JMeter uses Jakarta ORO for regular expressions processing. You can quickly test your regular expressions using Jakarta ORO Demonstration (http://jakarta.apache.org/oro/demo.html) Applet which is the fastest way of seeing result matches/groups/etc.

Performance and Functional Testing using TAURUS (Blazemeter)

Hirok Sarker — Fri, 01 Nov 2019 17:38:08 +0000

I am always wondering to know something new in Testing (Automation & Performance). Last few months fully concentrating on Automation, Performance and Functional Testing. Though today discusses performance and functional testing using TAURUS (Automation-friendly framework for Continuous Testing) open-source project created by BlazeMeter and great community members who are always contributing to help our technology community. Those who are using JMeter for performance and functional testing, you will happy to hear that TAURUS helps you to see the real-time performance and function testing and BlazeMeter Report.

Why TAURUS:
Hides the complexity of performance and functional tests with an automation-friendly convenience wrapper. Taurus relies on JMeter, Gatling, Locust.io, Grinder and Selenium WebDriver as its underlying tools. Free and open source under Apache 2.0 License.

Resource Documentation:
Url: http://gettaurus.org/docs/Index/
Github Url: https://github.com/Blazemeter/taurus
If you are using multiple testing executor. Don’t worry also TAURUS has great features.

Supporting Testing Executor:
(JMeter, Selenium, JUnit, TestNG, Apiritif, PyTest, RSpec, Mocha, WebdriverIO, NUnit, Robot, Gatling, Grinder, Locust, PBench, Siege, ApacheBenchmark, Tsung, Molotov, Postman/Newman) executor and also Existing Results Loader.
Install Process: Url: http://gettaurus.org/install/Installation/
Full details information on how to install TAURUS and also all kinds of operating system support.

jMeter Executor Download and Example:
Download Taurus Installer Software and Install.
Windows — https://gettaurus.org/builds/TaurusInstaller_1.13.9_x64.exe

Windows User:
-> Run Command Prompt — cmd
-> bzt jMeter .jmx file full location like (C:\Users\jmx\testing.jmx) Example: bzt C:\Users\jmx\testing.jmx
-> run

Sample Execution Code:
INFO: Taurus CLI Tool v1.13.9
INFO: Starting with configs: [‘C:\Users\jmx\testing.jmx’]
INFO: Configuring…
INFO: Artifacts dir: C:\Users\2019–11–01_21–07–26.754978
INFO: Preparing…
INFO: Starting…

Also have YMAL support:

# execution:
# - scenario: simple
# scenarios:
# simple:
# script: tests/jmx/testing.jmx

(Remove hash symbol before creating .yml file.)

save file as test.yml

Windows User (yml run command):
-> Run Command Prompt
-> bzt yml file full location like (C:\Users\yml\test.yml) Example: bzt C:\Users\yml\test.yml
-> run

jMeter Taurus Configuration Details: http://gettaurus.org/docs/JMeter/ and see as your requirement.
Automation-friendly framework for Continuous Testing by http://gettaurus.org
Thanks

How to fixed Postman API Test Collection using Nodejs (newman)and Unicode Problem Windows 10

Hirok Sarker — Tue, 22 Oct 2019 10:47:38 +0000

Our main goal of continuous integration is to identify the problems that may occur during the development process earlier and more easily.
Passionate about automation and optimizing the best processes. Continuous Integration (CI) is a software development practice that is based on a frequent integration of the code into a shared repository.
Most commonly used Jenkins because Jenkins is an open-source automation server. Its main objectives are to detect changes in subversion or git and to perform tasks repeatedly (i.e., build, test, deploy, package, integrate). In general, Jenkins allows one to create a complete CI cycle.
Continuous Integration Systems has many benefits but sometimes face setup related issues. To fixed two-issue windows to console reports and Unicode related issues.

How to run newman command in Jenkins-
Pre-requirement — Install Nodejs — https://nodejs.org/en/
Choose new FreeStyle Project-

Then choose Build > Execute Windows batch command

The console output result should look like this: (Windows)

Ok. Now everything ready but newman issue. Now we need to fix that newman issue.
First Need to install — Nodejs Plugin > Manage Plugins > Available > Search — Nodejs > Check box > Install and Restart
Now let’s go to Jenkins > Manage Jenkins > Global Tools Configuration

Apply then Save. :)
Now Edit Project —

Check box click — Provide Node & npm bin / folder to PATH. Apply & Save
Again Build Now —

Congratulations! but one more issue again. Unicode related issue :(.
UTF-8 encoding issue resolution method in Jenkins — (One)
Go to Install Project directory — C:\Program Files (x86)\Jenkins
Open > jenkins.xml

-Dfile.encoding=UTF8
Save then Restart — Jenkins Service

Again Build Now —

Congratulations and Successfully Fixed Unicode Issue.
Another different way to fix Unicode issue -
To resolve the encoding issue we have to add the environment variable in system as shown below first.

Save then Restart — Jenkins Service

These environment variables were added in Jenkins as well which has resolved the encoding issue.
Jenkins -> Manage Jenkins -> Configure System ->Global properties.