Blockchain technology testing systems, devices and equipment

Abstract

This application relates to blockchain technology testing systems, devices, and equipment. Based on blockchain testing specifications and standards, it utilizes a systematic management system with test outline, test template, and test case modules to centrally establish and maintain basic testing resources. According to the customized project needs of testing users, it obtains flexibly configurable test scripts and isolated execution environments through the independent environment creation and test template copying and adjustment mechanism of the project management module. Based on the automation requirements during test execution, it achieves automatic execution of test cases, status tracking, and report generation through script calls in the dynamic management module and implementation recording in the log module, ensuring the integrity and traceability of functional and performance testing. This application achieves standardization, flexibility, and traceability in blockchain testing through modular resource management, project environment isolation and template customization, and automated test execution.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular to a blockchain technology testing system, apparatus and equipment. Background Technology

[0002] like Figure 2 As shown, testing traditional blockchain systems heavily relies on manually developing customized test scripts and setting up dedicated test environments. Due to the diverse underlying technical architectures of blockchains (such as Fabric-like and Ethereum-like systems), the implementation of their core components (such as consensus mechanisms, ledger models, and smart contract engines) varies significantly, making it difficult to build universal testing tools and methods. Existing testing technologies are typically designed for specific blockchain platforms, lacking universal adaptability to different architectures, resulting in long test preparation cycles and high costs.

[0003] However, even for specific blockchain systems, traditional testing methods still face a series of serious challenges. First, when the same blockchain system needs to be applied to different fields such as finance and supply chain, it must comply with the specific specifications and standards of each field. Existing testing systems cannot effectively manage these standard differences, resulting in the need for independent, complete test construction, from case design to script development, for each new standard, leading to a large amount of repetitive work. Second, the highly customized development requirements of test scripts and tools not only extend project cycles but also inevitably introduce risks to the accuracy and consistency of test results due to differences in the technical skills of testers.

[0004] In the test execution phase, traditional systems suffer from low levels of automation. Most only provide a script execution environment and cannot automatically verify the blockchain system's response data against expected results based on preset judgment conditions, heavily relying on manual comparison and judgment. This manual intervention is not only inefficient but also a major source of missed and incorrect judgments, affecting the objectivity and credibility of test results. Furthermore, traditional deployment methods are typically limited to specific servers, making it difficult to flexibly construct and simulate the complex network topology and node configurations of a blockchain in a real-world operating environment. This means that test results cannot accurately reflect the system's performance in a production environment. Finally, at the test management level, traditional systems have weak support for batch test case execution scheduling, centralized recording and analysis of test logs, and automatic generation of test reports, making it difficult to meet the needs of large-scale, systematic testing.

[0005] Based on the above analysis, this invention proposes a unified testing system and method for mainstream blockchain technology architectures. This system aims to achieve efficient reuse of basic testing resources, automated execution and accurate judgment of the testing process, and realistic simulation of the testing environment by establishing a standardized testing resource library and a flexible template customization mechanism. This systematically solves the problems of poor universality, low efficiency, and insufficient reliability in traditional blockchain testing. Summary of the Invention

[0006] This application provides a blockchain technology testing system, including: Based on blockchain testing specifications and standards, a systematic management system is implemented through testing outline, testing template, and testing case modules to achieve centralized establishment and maintenance of basic testing resources. Based on the customized project requirements of test users, the independent environment creation and test template copying and adjustment mechanism of the project management module can be used to obtain flexibly configurable test scripts and isolated execution environments; Based on the automation requirements during test execution, the system utilizes script calls from the dynamic management module and logging to automatically execute test cases, track their status, and generate reports, ensuring the integrity and traceability of functional and performance testing.

[0007] Optionally, based on blockchain testing specifications and standards, the system manages basic testing resources through a test outline module, a test template module, and a test case module, enabling centralized establishment and maintenance of these resources. This includes: The test outline module allows you to create and adjust the test outline, generating a comprehensive test outline set consisting of multiple test cases. The test template module allows you to create and adjust test templates, generating a test template library with multiple architectures, and pre-configuring basic test scripts and tool templates. The test case module allows you to create and adjust test cases, generating a set of functional test cases and a set of performance test cases.

[0008] Optionally, based on the customized project requirements of the test user, the process utilizes the independent environment creation and test template copying and adjustment mechanism of the project management module to obtain flexibly configurable test scripts and isolated execution environments, including: Create a new test project through the project management module to generate a test project with an independent storage area and test execution environment; By selecting the corresponding test template from the test template module in a newly created test project, a copy of that template, independent of the test template library, can be obtained for test users to adjust. By configuring the necessary test parameters in the test project, including the network environment and node configuration information of the blockchain system under test, a test environment that has been deployed, connected, and is usable can be obtained.

[0009] Optionally, based on the automation requirements during test execution, the automatic execution, status tracking, and report generation of test cases are achieved through script calls in the dynamic management module and implementation recording in the log module, ensuring the integrity and traceability of functional and performance testing, including: The dynamic management module allows you to start test cases and obtain the execution process of the test scripts corresponding to the test cases being automatically invoked. The logging module automatically records test logs and system operation logs during test execution, obtaining detailed records including the results and execution process of successful cases and the results and execution process of unsuccessful cases. By integrating log records through the test report module, test reports for the corresponding test projects can be obtained, thus achieving the integrity and traceability of the testing process.

[0010] Optionally, the step of selecting a corresponding test template from the test template module in a newly created test project and obtaining a copy of that template, independent of the test template library, for the test user to adjust includes: By selecting from the test template library in the test template module for a newly created test project in the project management module, a template copy that is completely identical to the original template in the test template library but physically isolated can be obtained; By allowing test users to adjust the basic test scripts in the obtained template copy within the test project, a customized and effective test plan can be obtained for the current project. The adjustment process will not affect the integrity of the original templates in the test template library or their use in other projects.

[0011] Optionally, the step of creating and adjusting test cases through the test case module to generate a set of functional test cases and a set of performance test cases includes: The system administrator can create a single test case in the test case module according to the test outline specifications. The test case consists of a test script, execution steps and judgment conditions. The relevant test cases are then categorized to obtain a complete set of functional test cases. The system administrator can create and categorize corresponding performance test cases based on the specifications in the test case module to obtain a complete set of performance test cases.

[0012] Optionally, the step of starting a test case through the dynamic management module and obtaining the execution process of the test script corresponding to the test case being automatically invoked includes: By triggering the operation command to start a test case through the dynamic management module interface, the system automatically locates and calls the test script pre-associated with the test case to start the process. The invoked test script uses the SDK to initiate a request to the blockchain system to call the interface or contract, and receives the execution result returned by it, thus obtaining a complete closed loop of automated test action execution; The dynamic management module automatically records the execution status of test cases during script invocation and execution, enabling real-time tracking and visual feedback of the test process.

[0013] This application also provides a blockchain technology testing device, the device comprising: The user management module is used by system administrators to create and manage test user accounts, and to assign permissions to system administrators and test users. The basic resource management module is used to systematically manage basic testing resources based on blockchain testing specifications and standards through the test outline module, test template module, and test case module, thereby enabling the centralized establishment and maintenance of basic testing resources. The project management module is used to obtain flexibly configurable test scripts and isolated execution environments based on the customized project needs of test users through independent environment creation and test template copying and adjustment mechanisms. The test execution and traceability module is used to automatically execute test cases, track their status, and generate reports based on the automation requirements during the test execution process. This is achieved through script calls from the dynamic management module and implementation records from the log module, ensuring the integrity and traceability of functional and performance tests.

[0014] Optionally, the blockchain technology testing device further includes: The basic resource management module includes a test outline module, a test template module, and a test case module. The test outline module is used by system administrators to establish and manage a set of test outlines consisting of multiple test cases in accordance with blockchain testing specifications and standards, providing a standardized basis for testing. The test template module is used by system administrators to pre-configure and manage a test template library containing basic test scripts and tool templates for different blockchain architectures. The test case module is used by system administrators to create and manage a set of functional and performance test cases consisting of test scripts, execution steps, and judgment conditions, in conjunction with the test outline and system characteristics. The test execution and traceability module includes a dynamic management module, a log module, and a test report module; The dynamic management module is used to test users to start test cases, automatically call the corresponding test scripts to interact with the blockchain system, and record the execution status of the cases in real time. The logging module is used to automatically record detailed logs of test cases, system operation logs and results during test execution to ensure traceability of the process; The test report module is used to generate and manage the final test report for the corresponding test project based on the execution process and results recorded by the log module.

[0015] This application also provides an electronic device for implementing any of the described blockchain technology testing systems, comprising: The processor is used to perform all computational tasks and implement a blockchain technology testing system. Memory is used to store processor-executable instructions and statically stored data.

[0016] The beneficial effects of this application are as follows: By dividing the test outline, templates, and case library based on role-based permissions, the system administrator centrally manages the test outline, templates, and case library, achieving standardization and efficient reuse of basic test resources and reducing the cost of redundant construction; by creating an independent environment and an adjustable copy of the test template for each test project, testers are allowed to flexibly customize scripts in an isolated space to adapt to specific blockchain architectures and customized functions, significantly improving the efficiency and flexibility of test preparation; and by automatically calling test scripts to execute cases through the dynamic management module, recording the entire process data in real time through the log module, and generating detailed reports with one click through the test report module, the entire chain from test execution to result traceability is automated and precise. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the accompanying drawings required in the description of the embodiments or the prior art are briefly introduced below. Obviously, the accompanying drawings described below are only embodiments of this application. For those skilled in the art, other drawings can be obtained based on the provided drawings without creative effort.

[0018] Figure 1 A flowchart illustrating a specific embodiment of the blockchain technology testing system of this application is shown; Figure 2 This illustration shows a prior art schematic diagram of a blockchain technology testing system according to a specific embodiment of this application; Figure 3 This application shows a flowchart illustrating the main steps of a blockchain technology testing system according to a specific embodiment. Figure 4 This diagram illustrates the basic structure of a blockchain technology testing system according to a specific embodiment of this application. Figure 5 This diagram illustrates the operation of a blockchain technology testing system according to a specific embodiment of this application. Figure 6 This diagram illustrates the user function testing steps of a blockchain technology testing system according to a specific embodiment of this application. Figure 7 This diagram illustrates the user performance testing steps of a blockchain technology testing system according to a specific embodiment of this application. Figure 8 This is a block diagram of a blockchain technology testing apparatus according to a specific embodiment of this application. Detailed Implementation

[0019] Various exemplary embodiments, features, and aspects of this application will now be described in detail with reference to the accompanying drawings. The same reference numerals in the drawings denote elements that have the same or similar functions. Although various aspects of the embodiments are shown in the drawings, they are not necessarily drawn to scale unless specifically indicated otherwise.

[0020] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, "multiple" means two or more, unless otherwise explicitly specified.

[0021] The term “exemplary” as used herein means “serving as an example, embodiment, or illustration.” Any embodiment illustrated herein as “exemplary” is not necessarily to be construed as superior to or better than other embodiments.

[0022] Furthermore, to better illustrate this application, numerous specific details are provided in the following detailed embodiments. Those skilled in the art should understand that this application can be implemented without certain specific details. In some instances, methods, means, components, and circuits well-known to those skilled in the art have not been described in detail in order to highlight the main points of this application.

[0023] This application proposes a blockchain technology testing system to address the challenge of efficiently and accurately testing diverse and customized blockchain systems in existing technologies. Based on the role division between system administrators and test users, this application designs a modular test management system. At its core, the system administrator pre-builds a standardized test resource library covering multiple blockchain architectures through test outline, test template, and test case modules. For test projects, this application introduces a project isolation and template copy mechanism. When test users create a new project through the project management module, they obtain an independent execution environment and a copy of the standard template. This allows for flexible adjustments to test scripts without affecting the original resource library, precisely adapting to the specific customized functions of the blockchain system under test. During the test execution phase, the dynamic management module automatically calls the case scripts to interact with the blockchain system, and the log module records the execution status and results throughout the process. Finally, the test report module generates a complete and traceable test report. This method effectively reduces the reliance on the blockchain development capabilities of testers. Through resource standardization, environment isolation, execution automation, and process traceability, it achieves a comprehensive improvement in the efficiency and accuracy of functional and performance testing of heterogeneous blockchain systems.

[0024] Example 1 like Figure 1The diagram shown is a flowchart of a blockchain technology testing system according to an embodiment of this application, which specifically includes the following: S100, based on blockchain testing specifications and standards, uses a systematic management approach through test outline, test template, and test case modules to achieve centralized establishment and maintenance of basic testing resources.

[0025] Specifically, based on the standards and norms in the blockchain testing field, a basic resource management system is constructed, consisting of a test outline module, a test template module, and a test case module working collaboratively. The test outline module, serving as the general guideline for testing activities, is responsible for transforming abstract specification clauses into a structured set of test outlines comprised of specific test cases, their execution steps, and judgment conditions, ensuring the standardization of the test scope and objectives. The test template module, targeting the characteristics of mainstream blockchain technology architectures, pre-packages their basic test scripts and tools, forming a reusable, architecturally-based test template library, providing support for rapid adaptation to blockchain systems with different underlying technologies. Building upon this, the test case module, guided by the test outline and referencing the capabilities of the test templates, refines the specific test scripts, execution logic, and pass criteria for each test case, ultimately categorizing them into functional test case sets and performance test case sets. These three modules are uniformly operated and maintained by the system administrator. Through operations such as creating, modifying, deleting, and querying, they jointly achieve centralized establishment, version control, and continuous maintenance of basic test data, laying a standardized and reusable resource foundation for the entire testing system.

[0026] S200, based on the customized project needs of test users, obtains flexibly configurable test scripts and isolated execution environments through the independent environment creation and test template copying and adjustment mechanism of the project management module.

[0027] Specifically, based on the needs of test users to initiate specific test projects, the instantiation and customization of the test environment are achieved through the linkage mechanism between the project management module and the test template module. The core function of the project management module is to respond to the command to create a new test project, allocate it with completely independent storage space and test execution environment, and ensure that the operations and data between different test projects do not interfere with each other, meeting the isolation requirements of parallel testing of multiple projects. During the project initialization phase, test users need to select a matching test template from the system's pre-set test template library based on the actual architecture of the blockchain system under test. This selection operation does not establish a static link, but triggers a template copy mechanism to generate a complete copy of the selected test template for the current test project. This copy is independent of the original template in the template library, giving test users the permission to adjust and modify the test scripts according to the specific needs of the project. After completing the template selection, test users need to configure the network topology, node parameters, and other necessary information of the target blockchain system within the project, thereby completing the transformation from a general template to a specific project environment and obtaining a flexibly adjustable isolated test environment tailored to a specific test target.

[0028] The S300, based on the automation requirements during the test execution process, achieves automatic execution of test cases, status tracking, and report generation through script calls in the dynamic management module and implementation recording in the log module, ensuring the integrity and traceability of functional and performance testing.

[0029] Specifically, based on the core requirements of automation and traceability during the test execution phase, an end-to-end automated test pipeline is constructed through the collaborative operation of the dynamic management module and the log module. The dynamic management module, acting as the engine of test execution, is responsible for receiving test case initiation commands from test users and automatically calling the customized test scripts associated with those test cases. These scripts interact with the blockchain system under test through a software development kit (SDK), initiating transaction calls, contract executions, and capturing the system's response results, thereby completing the automatic execution and status determination of the test cases. During this process, the log module simultaneously initiates full-link recording, capturing not only the pass / fail results output by the test scripts but also detailed records of the test case execution steps, detailed logs generated by system interactions, and the operational status information of the blockchain nodes themselves, forming a complete process record set including both positive and negative results. The test report module, based on the full data accumulated by the log module, automatically summarizes and analyzes the data, ultimately generating a structured test report. This closed loop, from automatic execution, real-time status tracking, full-process recording to automatic report generation, ensures that the process of each test activity is complete and traceable, and the results are accurate and auditable, while significantly improving testing efficiency.

[0030] In summary, this application revolutionizes the traditional blockchain testing workflow, which relies on manual configuration, lacks reusability, and suffers from a lack of standardization. It constructs a centralized test resource management system based on role-based access control and modular management. Firstly, addressing the pain points of scattered and difficult-to-maintain test resources, the application achieves systematic and standardized management of test specifications, architectural scripts, and specific cases through the collaboration of three modules: test outlines, test templates, and test cases. System administrators can efficiently build a reusable resource library covering multiple architectures, fundamentally solving the problems of inconsistent standards and redundant construction in the test preparation phase, laying a solid foundation for high-quality testing. Secondly, to address the challenges of diverse project requirements, high environmental isolation requirements, and the need to adapt to customized functions in actual testing, an independent environment creation and test template copying and adjustment mechanism based on the project management module is designed. This mechanism ensures that each test project has an independent execution space and allows test users to flexibly adjust standard template copies within the project, thereby achieving a balance between test preparation efficiency and customization flexibility, effectively reducing reliance on the underlying development capabilities of testers. Finally, to achieve end-to-end automation and precise traceability of test execution, an automated pipeline was constructed, driven by a dynamic management module, with a logging module recording the entire process, and a test report module generating conclusions. This pipeline can automatically invoke test scripts, capture system interaction states in real time, completely record process data, and generate reports with one click, ensuring end-to-end traceability from test case execution to result auditing, significantly improving the efficiency and reliability of test execution. Through the above systematic methodological innovation, this solution provides an efficient, accurate, and traceable integrated solution for the functional and performance testing of heterogeneous blockchain systems.

[0031] As an optional implementation of this application, optionally, in step S100, based on blockchain testing specifications and standards, systematic management is carried out through a test outline module, a test template module, and a test case module to achieve centralized establishment and maintenance of basic testing resources, including: S110, through the test outline module, establishes and adjusts the test outline, generating a test outline set consisting of multiple test cases.

[0032] Specifically, such as Figure 4As shown, the test outline module serves as the foundational specification unit of the system. Its core function is to enable system administrators to transform external, text-based blockchain test specifications and standards into a structured data system that is recognizable and executable within the system. Within this module, administrators can manage the entire lifecycle of the test outline through operations such as creating, modifying, deleting, and querying. A complete test outline is essentially a logical container and execution guide for test cases. It is not simply a list of case names, but rather a structured definition of the test objective to which each test case belongs, its execution order in the test process, and the logical relationships between the cases.

[0033] The S120 uses the test template module to create and adjust test templates, generating a test template library containing multiple architectures, and pre-sets basic test scripts and tool templates.

[0034] Specifically, such as Figure 4 As shown, the test template module focuses on solving the compatibility issues when testing blockchain systems with different technical architectures. This module allows system administrators to pre-build and maintain a set of basic test scripts and tools for mainstream blockchain architectures (such as Fabric-like and Ethereum-like architectures). Each test template is a semi-finished test solution package, encapsulating general test logic for a specific architecture, basic interaction interfaces (such as specific SDK calling methods), and necessary testing tools. Administrators can create new architecture templates or update and optimize existing templates within this module. By establishing such an architectural test template library, the system can provide test users with a ready-to-use testing foundation.

[0035] S130 uses the test case module to create and adjust test cases, generating a set of functional test cases and a set of performance test cases.

[0036] Specifically, such as Figure 4 As shown, in the test case module, system administrators, based on the overall plan of the test outline and referring to the script capabilities provided by the test template library, can refine the construction of test cases. Each test case is an independent and executable minimum test unit, defined by three core elements: first, a specific test script containing all the code logic driving test execution; second, clear execution steps describing the order and conditions of script execution; and third, clear judgment conditions specifying how to determine whether the case passes or fails based on the test execution result. This module allows administrators to create, modify, delete, and categorize test cases. Ultimately, all test cases are systematically classified into functional test case sets and performance test case sets, thus forming a complete testing capability covering different quality attributes of the blockchain system.

[0037] As an optional implementation of this application, optionally, in step S130, test cases are created and adjusted through the test case module to generate a set of functional test cases and a set of performance test cases, including: S131, the system administrator creates a single test case in the test case module according to the test outline specifications, consisting of a test case script, execution steps and judgment conditions, and categorizes the relevant cases to obtain a complete set of functional test cases.

[0038] Specifically, the process of constructing the functional test case set is a direct reflection of the system administrator's test design within the test case module, addressing the functional requirements of the blockchain system. The administrator creates test cases one by one according to the functional requirements outlined in the test syllabus. Each functional test case focuses on verifying whether a specific function works as expected, such as the connectivity of peer-to-peer communication, the immutability of ledger data, the correctness of the consensus protocol, the validity of cryptographic algorithms, or the logical accuracy of smart contracts. For each case, the administrator needs to write or configure its own test script, clearly defining the sequence of steps to execute the script, and defining the criteria used to determine whether the function is functioning correctly (such as interface return codes, transaction confirmation status, data consistency, etc.). Categorizing and integrating all these functional test cases forms a systematic functional test case set, designed to comprehensively examine the various functional characteristics of the blockchain system under test.

[0039] S132, the system administrator can create and categorize corresponding performance test cases based on the specifications in the test case module to obtain a complete set of performance test cases.

[0040] Specifically, the construction of a performance test case set aims to evaluate the performance of a blockchain system under high load or specific stress conditions. In the test case module, system administrators design corresponding performance test cases based on the performance metrics (such as transaction throughput (TPS), query throughput (QPS), transaction latency, and resource utilization) requirements outlined in the test syllabus. Unlike functional test cases, performance test case scripts typically include stress generation logic, performance data collection logic, and duration control. Their execution steps may involve gradually increasing the number of concurrent users or transaction frequency, while the judgment criteria focus on measuring whether performance metrics reach preset thresholds or observing system behavior curves. By creating a series of test cases targeting different performance dimensions and stress scenarios, and categorizing and managing them to form a performance test case set, the processing power, scalability, and stability of the blockchain system under test can be scientifically evaluated.

[0041] As an optional implementation of this application, optionally, in step S200, based on the customized project requirements of the test user, a flexibly configurable test script and isolated execution environment are obtained through the independent environment creation and test template copying and adjustment mechanism of the project management module, including: S210 allows you to create a new test project through the project management module, generating a test project with its own independent storage area and test execution environment.

[0042] Specifically, when a test user needs to start a new test task, they initiate a "Create New Test Project" command through this module. Upon responding to this command, the module allocates dedicated storage space at the system level, physically isolated from other projects, and initializes a clean test execution environment. This independent environment ensures that all operations within the project, including configuration modifications, script adjustments, data generation, and logging, are strictly confined to their own boundaries, preventing resource conflicts or data interference with any other concurrently running test projects.

[0043] S220: By selecting the corresponding test template from the test template module in a newly created test project, a copy of the template, independent of the test template library, is obtained for the test user to adjust.

[0044] Specifically, such as Figure 4 As shown, during the creation phase of a test project, test users need to select the most suitable base template from the template library provided by the test template module, based on the specific technical architecture of the blockchain system under test (e.g., Fabric V1 or FISCO BCOS V2). The selection operation performed by the system essentially triggers a copy operation, generating a complete copy of the selected template for the current test project. This copy is initially identical to the original template in the template library, but it is placed in a separate storage area for the project, thus physically independent of the original template library. This mechanism grants test users the authority to freely modify the test scripts in the copy according to the specific needs of the project (such as customized functions of the chain under test), enabling flexible customization of the test plan while perfectly protecting the integrity and stability of the original template.

[0045] S230: By configuring the necessary test parameters in the test project, including the network environment and node configuration information of the blockchain system under test, a test environment that has been deployed, connected and is available can be obtained.

[0046] Specifically, after the test project obtains an independent execution environment and a customized test template copy, this step aims to connect the test system with the target blockchain environment. Test users need to fill in the network connection parameters of the blockchain system under test in detail in the project configuration interface provided by the project management module. These parameters typically include, but are not limited to, the IP addresses, port numbers, access credentials (such as certificates and keys), network topology, and specific node configuration information of each node. Based on this configuration information, the system initializes the communication link between the test system and the blockchain network (for example, configuring the corresponding SDK connection parameters). After this configuration is completed, the test system successfully connects to the target blockchain environment, preparing for subsequent test scripts to realistically call blockchain interfaces, send transactions, and query status, signifying that a truly usable test environment is ready.

[0047] As an optional implementation of this application, optionally, in step S220, by selecting the corresponding test template from the test template module in the newly created test project, a copy of the template independent of the test template library is obtained for the test user to adjust, including: S221, by selecting from the test template library of the test template module for a newly created test project in the project management module, a template copy that is completely identical to the original template in the test template library but physically isolated is obtained.

[0048] Specifically, when a test user selects a specific template (such as the "Fabric V1 template") from the test template library within the context of the project management module, the system does not simply create a symbolic link to the original template; instead, it performs a deep copy operation. This operation completely copies all elements of the original template, including basic test scripts, dependent tools, configuration files, etc., and stores this copy in a separate storage area owned by the current test project. This ensures that while the project copy and the original template in the template library are initially identical in logical content, they are completely separated in physical storage, forming two independent entities. This physical isolation is the technical foundation that ensures test users can safely make any adjustments to the copy without polluting the original template library.

[0049] S222 allows test users to adjust the basic test scripts in the obtained template copy within the test project to obtain a customized and effective test plan for the current project. The adjustment process will not affect the integrity of the original templates in the test template library or their use in other projects.

[0050] Specifically, this step describes how test users can leverage the independence of the template copy for test customization. After obtaining a project-specific template copy, test users can modify, add to, delete from, or optimize the underlying test scripts contained within that copy. For example, when the blockchain system under test adds special smart contract interfaces or customized consensus mechanisms beyond standard functionality, test users can adjust or add test scripts accordingly in the copy to cover these customized features. All these adjustments only apply to the template copy of the current project, and their impact is strictly limited to this project. The original template in the template library remains unchanged, and other newly created or running test projects still reference the unmodified original template.

[0051] As an optional implementation of this application, optionally, in step S300, based on the automation requirements during the test execution process, the automatic execution, status tracking, and report generation of test cases are achieved through script calls in the dynamic management module and implementation recording in the log module, ensuring the integrity and traceability of functional and performance testing, including: S310 uses the dynamic management module to start test cases and obtain the execution process of the test scripts corresponding to the test cases being automatically called.

[0052] Specifically, such as Figure 5 As shown, the dynamic management module is the engine driving the automatic execution of test cases. When a test user selects a test case (e.g., "Test Case N") and issues a start command, this module takes over the subsequent automated process. It first locates the customized test script bound to it in the project resources based on the test case's unique identifier. Then, the module automatically schedules system resources, loads, and executes the test script. This process requires no manual intervention in the script's invocation and startup details, freeing users from tedious command-line operations and is a key step in improving testing efficiency.

[0053] The S320 automatically records test logs and system operation logs during test execution through the log module, obtaining detailed records including the results and execution process of successful cases and the results and execution process of unsuccessful cases.

[0054] Specifically, such as Figure 5As shown, the logging module is responsible for recording events and data across the entire test execution process, from multiple dimensions. It not only captures the simple "pass" or "fail" result output by the test script, but also records detailed lifecycle information of the test case execution, including: key step logs within the test script, requests sent and responses received when interacting with the blockchain system via the SDK, error messages and exception stacks generated during the interaction, and the running status output of the blockchain node under test. All this information is collected and stored in real-time and in a structured manner, forming a comprehensive record set containing both positive and negative results. This provides raw data support for problem localization, process review, and report generation, ensuring a high degree of transparency and traceability in the testing process.

[0055] The S330 uses the test report module to integrate log records and obtain test reports for the corresponding test items, thus achieving the integrity and traceability of the testing process.

[0056] Specifically, such as Figure 5 As shown, the test report module is the final stage of the testing process. Its function is to refine, analyze, and format the massive amount of raw data recorded by the log module, generating a human-readable and clearly structured test report. This module automatically extracts key information from the logs, such as the list of executed cases, the execution status of each case (pass / fail), execution time, details of discovered errors, and system resource consumption. Then, following a predefined report template, it integrates this information into a complete test report. This report objectively reflects the overall results and quality assessment of the testing activity, clearly demonstrating the coverage and verification conclusions of functional and performance testing, ultimately achieving a complete summary and authoritative archiving of the entire testing project process.

[0057] As an optional implementation of this application, optionally, in step S310, the operation of starting the test case is performed through the dynamic management module, and the execution process of the test script corresponding to the test case being automatically called is obtained, including: S311, by triggering the operation command to start the test case through the dynamic management module interface, the system automatically locates and calls the test script pre-associated with the test case to start the process.

[0058] Specifically, the user executes a "start" operation on a specific test case in the front-end interface (such as a web console). This operation generates an instruction containing a case ID. Upon receiving this instruction, the server-side component of the dynamic management module first parses it to identify the target case. Then, based on the case-script binding relationship within the current test project's resource index, it precisely locates the corresponding project-level customized test script file or script entry point for that case. Once successfully located, the module calls the script interpreter or execution engine, passing in the necessary parameters, and starts the script execution.

[0059] S312 uses the SDK to initiate a request to the blockchain system to call the interface or contract through the called test script, and receives the execution result returned by it, thus obtaining a complete closed loop of automated test action execution.

[0060] Specifically, the test script invoked by the dynamic management module contains logic for programming interaction through the blockchain system's Software Development Kit (SDK). Following its preset process, the script constructs specific transaction or query requests and sends them to the configured blockchain network under test via the SDK's interface. These requests may involve calling smart contract functions, initiating a transaction, or querying ledger status. The script then waits synchronously or asynchronously for the blockchain network's processing results. After the network completes consensus and execution processes, it returns the execution results (such as transaction receipts, return values, and error messages) to the test script via the SDK. Upon receiving the results, the script analyzes them according to its embedded decision logic. This closed loop of "request-execution-return-analysis" is the substantive step in actually verifying the functionality and performance of the blockchain system.

[0061] S313 automatically records the execution status of test cases during script invocation and execution through a dynamic management module, providing real-time tracking and visual feedback of the test process.

[0062] Specifically, throughout the entire lifecycle of a test script being invoked and executed, the dynamic management module does not passively wait for the script to finish, but actively monitors its running status. It can capture the script's execution progress information (such as start, in progress, completed), exit codes, and the status of key checkpoints actively reported by the script in real time. This status information is collected and updated in real time by the dynamic management module to its internal state machine and user interface. This allows test users to visually observe the progress of test execution in real time, such as which test case is currently being executed, the number of passed and failed test cases, and whether any test cases have timed out or encountered exceptions. This real-time tracking and feedback mechanism greatly enhances control over the testing process, facilitating timely detection of problems and interruption of abnormal tests.

[0063] Example 2 As an application example of this method, such as Figure 3 As shown, the specific implementation process is as follows: Step S1: The system administrator creates and manages test outlines through the test outline module. A test outline is a comprehensive collection of test specifications and standards. The system administrator has permissions to create, modify, delete, and query test outlines. Step S2: The system administrator establishes and manages a test template library through the test template module. Test templates are pre-built libraries of basic test scripts and tools for different blockchain systems. The system administrator has permissions to create, modify, delete, and query test templates. Step S3: The system administrator creates and manages test cases through the test case module. The test case template combines blockchain specifications, standards, and blockchain system characteristics. A test case consists of a test script, execution steps, and decision conditions. Depending on the required SDK and decision conditions, there may be multiple versions of the test script, execution steps, and decision conditions for a single test case. The system administrator selects the test case based on specific system characteristics when creating the test outline template. The system administrator has permissions to create, modify, delete, and query test cases. Step S4: The system administrator creates test users through the user management module. Each newly created test user corresponds to a tester, and each tester can only create a test user once.

[0064] Step S5: Test users create a new test project through the project management module. Once the project is created, it has an independent storage area and test execution environment, which is independent of other newly created test projects. Step S6: The test user selects a test template for the newly created test project through the test template module. The newly created test project has a copy of the selected test template, which allows the test user to quickly conduct tests based on the various templates created by the system administrator without needing extensive blockchain system development capabilities. After creation, the necessary test parameters such as the network environment and node configuration information of the blockchain system under test are configured, completing the deployment of the network environment of the blockchain system under test and the connection between the test system and the blockchain system. Step S7: The test user selects a test project and views the project configuration, node status, and test cases; Step S8: Test users conduct tests through various operations of the dynamic management module and automatically record the execution status of test cases; Step S9: Test users record test logs and system operation logs of the tested cases through the log module; Step S10: Test users manage the test reports for the corresponding test projects through the test report module.

[0065] Among them, such as Figure 6 and 7As shown, the specific process of step S7 is as follows: Step S71: Conduct point-to-point communication testing; Step S72: Conduct ledger technology testing; Step S73: Conduct consensus protocol testing; Step S74: Conduct cryptographic algorithm testing; Step S75: Conduct smart contract testing; Step S76: Functional testing completed; Step S77: Conduct transaction throughput testing; Step S78: Conduct query throughput testing; Step S79: Performance test complete.

[0066] Example 3 Based on the same principle as the aforementioned method, a blockchain technology testing device is also proposed, see [link to relevant documentation]. Figure 8 A blockchain technology testing device 100 according to an embodiment of this disclosure includes: User management module 110 is used by system administrators to create and manage test user accounts, and to assign permissions to system administrators and test users. The Basic Resource Management Module 120 is used to systematically manage basic testing resources based on blockchain testing specifications and standards through the Test Outline Module, Test Template Module, and Test Case Module, thereby enabling centralized establishment and maintenance of basic testing resources. The project management module 130 is used to obtain flexibly configurable test scripts and isolated execution environments based on the customized project needs of test users through independent environment creation and test template copying and adjustment mechanisms. The test execution and traceability module 140 is used to automatically execute test cases, track their status, and generate reports based on the automation requirements during the test execution process, through script calls from the dynamic management module and implementation records from the log module, ensuring the integrity and traceability of functional and performance tests.

[0067] As an optional implementation of this application, the blockchain technology testing device 100 may optionally include: The basic resource management module 120 includes a test outline module 121, a test template module 122, and a test case module 123; The test outline module 121 is used by the system administrator to establish and manage a set of test outlines consisting of multiple test cases in accordance with blockchain testing specifications and standards, so as to provide a standardized basis for testing. The test template module 122 is used by the system administrator to pre-configure and manage a test template library containing basic test scripts and tool templates for different blockchain architectures. The test case module 123 is used by the system administrator to establish and manage a set of functional and performance test cases consisting of test scripts, execution steps and judgment conditions, in conjunction with the test outline and system characteristics. The test execution and traceability module 140 includes a dynamic management module 141, a log module 142, and a test report module 143; The dynamic management module 141 is used to test users to start test cases, automatically call the corresponding test scripts to interact with the blockchain system, and record the execution status of the cases in real time. The log module 142 is used to automatically record detailed logs of test cases, system operation logs and results during test execution to ensure process traceability; The test report module 143 is used to generate and manage the final test report for the corresponding test project based on the execution process and results recorded by the log module.

[0068] Obviously, those skilled in the art should understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the control methods described above. The modules or steps of this application described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. Optionally, they can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Therefore, this application is not limited to any specific hardware and software combination.

[0069] Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the control methods described above. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD), etc.; the storage medium can also include combinations of the above types of memory.

[0070] Example 4 Furthermore, this application proposes an electronic device for implementing any of the described blockchain technology testing systems, comprising: The processor is used to perform all computational tasks and implement a blockchain technology testing system. Memory is used to store processor-executable instructions and statically stored data.

[0071] The electronic device of this disclosure includes a processor and a memory for storing processor-executable instructions. The processor is configured to implement any of the blockchain technology testing systems described above when executing the executable instructions.

[0072] It should be noted that the number of processors can be one or more. Furthermore, the electronic device in this embodiment may also include input devices and output devices. The processor, memory, input devices, and output devices can be connected via a bus or other means, without specific limitations herein.

[0073] Memory, as a method for resolving dependency conflicts in open-source libraries, is a computer-readable storage medium that can be used to store software programs, computer-executable programs, and various modules, such as the program or module corresponding to the blockchain technology testing system in this disclosure. The processor executes various functional applications and data processing of the electronic device by running the software program or module stored in the memory.

[0074] Input devices can be used to receive input digital numbers or signals. These signals can be key signals related to user settings and function control of the device / terminal / server. Output devices can include display devices such as screens.

[0075] The various embodiments of this application have been described above. These descriptions are exemplary and not exhaustive, nor are they limited to the disclosed embodiments. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described embodiments. The terminology used herein is chosen to best explain the principles, practical application, or improvement of the technology in the market, or to enable others skilled in the art to understand the embodiments disclosed herein.

Claims

1. A blockchain technology testing system, characterized in that, include: Based on blockchain testing specifications and standards, a systematic management system is implemented through testing outline, testing template, and testing case modules to achieve centralized establishment and maintenance of basic testing resources. Based on the customized project requirements of test users, the project management module utilizes its independent environment creation and test template copying and adjustment mechanisms to obtain flexibly configurable test scripts and isolated execution environments, including: Create a new test project through the project management module to generate a test project with an independent storage area and test execution environment; By selecting the corresponding test template from the test template module in a newly created test project, a copy of that template, independent of the test template library, can be obtained for test users to adjust. By configuring the necessary test parameters in the test project, including the network environment and node configuration information of the blockchain system under test, a test environment that has been deployed, connected and is usable can be obtained. By selecting from the test template library in the test template module for a newly created test project in the project management module, a template copy that is completely identical to the original template in the test template library but physically isolated can be obtained; By allowing test users to adjust the basic test scripts in the obtained template copy within the test project, a customized and effective test plan can be obtained for the current project. The adjustment process will not affect the integrity of the original templates in the test template library or their use in other projects. Based on the automation requirements during test execution, the system utilizes script calls from the dynamic management module and logging to automatically execute test cases, track their status, and generate reports, ensuring the integrity and traceability of functional and performance testing.

2. The blockchain technology testing system as described in claim 1, characterized in that, Based on blockchain testing specifications and standards, the system employs a comprehensive management approach through testing outline, testing template, and testing case modules to centrally establish and maintain basic testing resources. This includes: The test outline module allows you to create and adjust the test outline, generating a comprehensive test outline set consisting of multiple test cases. The test template module allows you to create and adjust test templates, generating a test template library with multiple architectures, and pre-configuring basic test scripts and tool templates. The test case module allows you to create and adjust test cases, generating a set of functional test cases and a set of performance test cases.

3. The blockchain technology testing system as described in claim 1, characterized in that, Based on the automation requirements during test execution, the system utilizes script calls from the dynamic management module and logging to automatically execute test cases, track their status, and generate reports. This ensures the integrity and traceability of functional and performance testing, including: The dynamic management module allows you to start test cases and obtain the execution process of the test scripts corresponding to the test cases being automatically invoked. The logging module automatically records test logs and system operation logs during test execution, obtaining detailed records including the results and execution process of successful cases and the results and execution process of unsuccessful cases. By integrating log records through the test report module, test reports for the corresponding test projects can be obtained, thus achieving the integrity and traceability of the testing process.

4. The blockchain technology testing system as described in claim 2, characterized in that, The test case module is used to create and adjust test cases, generating a set of functional test cases and a set of performance test cases, including: The system administrator can create a single test case in the test case module according to the test outline specifications. The test case consists of a test script, execution steps and judgment conditions. The relevant test cases are then categorized to obtain a complete set of functional test cases. The system administrator can create and categorize corresponding performance test cases based on the specifications in the test case module to obtain a complete set of performance test cases.

5. The blockchain technology testing system as described in claim 3, characterized in that, The operation of starting a test case through the dynamic management module, and obtaining the execution process of the test script corresponding to the test case being automatically called, includes: By triggering the operation command to start a test case through the dynamic management module interface, the system automatically locates and calls the test script pre-associated with the test case to start the process. The invoked test script uses the SDK to initiate a request to the blockchain system to call the interface or contract, and receives the execution result returned by it, thus obtaining a complete closed loop of automated test action execution; The dynamic management module automatically records the execution status of test cases during script invocation and execution, enabling real-time tracking and visual feedback of the test process.

6. A blockchain technology testing device, characterized in that, The device includes: The user management module is used by system administrators to create and manage test user accounts, and to assign permissions to system administrators and test users. The basic resource management module is used to systematically manage basic testing resources based on blockchain testing specifications and standards through the test outline module, test template module, and test case module, thereby enabling the centralized establishment and maintenance of basic testing resources. The project management module is used to obtain flexibly configurable test scripts and isolated execution environments based on the customized project needs of test users, through mechanisms for creating independent environments and copying and adjusting test templates. This includes: Create a new test project through the project management module to generate a test project with an independent storage area and test execution environment; By selecting the corresponding test template from the test template module in a newly created test project, a copy of that template, independent of the test template library, can be obtained for test users to adjust. By configuring the necessary test parameters in the test project, including the network environment and node configuration information of the blockchain system under test, a test environment that has been deployed, connected and is usable can be obtained. By selecting from the test template library in the test template module for a newly created test project in the project management module, a template copy that is completely identical to the original template in the test template library but physically isolated can be obtained; By allowing test users to adjust the basic test scripts in the obtained template copy within the test project, a customized and effective test plan can be obtained for the current project. The adjustment process will not affect the integrity of the original templates in the test template library or their use in other projects. The test execution and traceability module is used to automatically execute test cases, track their status, and generate reports based on the automation requirements during the test execution process. This is achieved through script calls from the dynamic management module and implementation records from the log module, ensuring the integrity and traceability of functional and performance tests.

7. The blockchain technology testing device according to claim 6, characterized in that: The basic resource management module includes a test outline module, a test template module, and a test case module. The test outline module is used by system administrators to establish and manage a set of test outlines consisting of multiple test cases in accordance with blockchain testing specifications and standards, providing a standardized basis for testing. The test template module is used by system administrators to pre-configure and manage a test template library containing basic test scripts and tool templates for different blockchain architectures. The test case module is used by system administrators to create and manage a set of functional and performance test cases consisting of test scripts, execution steps, and judgment conditions, in conjunction with the test outline and system characteristics. The test execution and traceability module includes a dynamic management module, a log module, and a test report module; The dynamic management module is used to test users to start test cases, automatically call the corresponding test scripts to interact with the blockchain system, and record the execution status of the cases in real time. The logging module is used to automatically record detailed logs of test cases, system operation logs and results during test execution to ensure traceability of the process; The test report module is used to generate and manage the final test report for the corresponding test project based on the execution process and results recorded by the log module.

8. An electronic device, characterized in that, For implementing the blockchain technology testing system according to any one of claims 1 to 5, comprising: The processor is used to perform all computational tasks and implement a blockchain technology testing system. Memory is used to store processor-executable instructions and statically stored data.

Images