Penetration Testing With Periodic QA Checks Eliminated The Vulnerabilities In A Real Estate Blockchain Application

We became the client's go-to testing partner owing to our excellent track record of checking different web assets—web apps, websites, etc. We even have extensive experience in examining the performance of blockchain networks and related assets such as crypto wallets. To begin with, we analyzed key project requirements and created a comprehensive test strategy.

After evaluating the requirements of the project, we included system testing, unit testing, penetration testing, and integration testing in our test strategy. Once our test strategy was finalized, we defined the roles and responsibilities of each team member. Our team consisted of a test leader, individual testers, and a dedicated project manager. Once the roles and responsibilities were confirmed, we started checking the environmental requirements. Running an environmental check was necessary to finalize the operating system used for testing different elements of the website.

Based on our project analysis, we zeroed in on manual testing. We also focused on doing penetration testing to make sure the blockchain application could withstand possible cyberattacks. Besides doing manual testing and penetration testing, we even used different tools to test the assets. These tools included Postman for testing that every API was functioning as intended. Besides, we used Microsoft TFS (Team Foundation Server) -- which is now called Azure DevOps Server -- to build a centralized repository of the artifacts or source files associated with the KeyCalm project.

As testing involves massive risks, we documented all the probable risk factors. By documenting these risks, we predicted their occurrences well ahead of time. We created exhaustive test schedules to give the client a detailed road map of different testing phases. This road map even defined which test cases will be executed by which tester and when.

Since the scope of the project was wide, we restored to regression testing to make sure the site remained bug-free. Whenever a bug was found while we carried out regression testing, we debugged the affected parts of the site. To ensure that the fix was effective, we retested the website against the same criterion.

The success of our testing strategy rested on our test groups. We defined test groups based on a variety of factors, such as traceability matrix requirements, test records maintenance, test priorities, test reporting, and status collection.

Based on our strategy, we tested every asset of the website -- investment portal, crypto wallets, KYC verification, and the underlying blockchain. As we strictly followed regression testing, we retested the affected assets again until they functioned correctly.

Our Testing Process

We followed a robust software testing life cycle that has helped us plan different test schedules seamlessly. In the past, too, our testing process has helped us deliver debugged assets with confidence. We follow the testing process to deliver high-quality software assets, including websites, mobile applications, and web apps. Now, here is a rundown of the different steps our testing process has.

• We started with analyzing the requirements of the client.
• After gathering the requirements, we created a holistic strategy that included several testing phases.
• We created multiple test-case designs.
• Afterward, we established a robust test environment.
• Our team started executing different test cases.
• Last, we followed a test cycle closure where we built different exit criteria and checked the assets against each of them.