U-Test method, device, equipment, medium and program product for assisting centralized U-Test management

Abstract

The present disclosure provides a U-shield test method for assisting centralized U-shield test management, which can be applied to the fields of big data technology and artificial intelligence technology. The U-shield test method for assisting centralized U-shield test management comprises: obtaining test data information matched with a business test category of a target test U-shield; determining a current occupation state of target test data corresponding to the test data information according to centralized U-shield test information corresponding to the centralized U-shield test management; and performing test on a target test U-shield corresponding to the target test data based on the current occupation state. The present disclosure also provides a U-shield test device, equipment, storage medium and program product for assisting centralized U-shield test management.

Description

Technical Field

[0001] This disclosure relates to the field of computer technology, and more specifically to a U-shield testing method, apparatus, equipment, medium, and program product for assisting centralized U-shield testing management. Background Technology

[0002] In business application systems provided by banks and other financial institutions, for transactions involving account changes, to ensure transaction security and prevent impersonation, existing technologies typically provide USB tokens (U-shields) as proof of user identity. Users must insert the U-shield into a computer or other terminal device to conduct transactions within the system. In other words, the U-shield, as an important identity authentication security medium, is widely used in customer transactions by banks and other financial institutions. As an identity authentication identifier for each customer, the digital certificate stored in the U-shield is unique; generally, each customer can only use a U-shield containing their own identity information. Typically, different users must use physical U-shield devices containing their own digital certificates when conducting financial transactions; U-shield devices from different customers cannot be used interchangeably. With the accelerated pace of version development, automated verification of business application systems has become the preferred solution in the U-shield testing process. Summary of the Invention

[0003] In view of the technical problems existing in the automated verification of business application systems based on U-shield business application tasks, this disclosure provides a U-shield testing method, device, equipment, medium and program product that can further improve the level and efficiency of existing automated U-shield software testing and assist centralized U-shield test management.

[0004] The first aspect of this disclosure provides a U-shield testing method to assist centralized U-shield test management, comprising: acquiring test data information matching the business test category of the target U-shield; determining the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management; and performing a test on the target U-shield corresponding to the target test data based on the current occupancy status.

[0005] According to an embodiment of this disclosure, before obtaining test data information matching the business test category of the target test U-shield, the method further includes: obtaining the current status information of the target test U-shield; and performing preprocessing on the target test U-shield based on the current status information.

[0006] According to an embodiment of this disclosure, the process of obtaining test data information that matches the business test category of the target test U-shield includes: extracting business test data corresponding to the business test category according to a preset data extraction rule to form the test data information.

[0007] According to an embodiment of this disclosure, determining the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management includes: querying the target test data in the test data information; retrieving the centralized U-shield test information in response to a received data retrieval instruction corresponding to the target test data; and determining the current occupancy status of the target test data based on the centralized U-shield test information.

[0008] According to an embodiment of this disclosure, determining the current occupancy status of the target test data based on the centralized U-shield test information includes: when the current test data corresponding to the target test data in the centralized U-shield test information is in an idle state, the current occupancy status of the target test data is idle; or when the current test data corresponding to the target test data in the centralized U-shield test information is in a test state, the current occupancy status of the target test data is occupied.

[0009] According to an embodiment of this disclosure, the step of performing a test on the target test U-shield corresponding to the target test data based on the current occupancy status includes: based on the current occupancy status, calling a digital certificate matching the target test data to infuse the target test U-shield; and performing a test click operation on the target test U-shield after the digital certificate has been infused.

[0010] According to an embodiment of this disclosure, the step of performing a test click operation on the target test U-shield after digital certificate infusion includes: responding to a received click control command, performing a click on the target test U-shield according to a preset click position correspondence; and obtaining click feedback information generated when the target test U-shield is clicked.

[0011] According to an embodiment of this disclosure, after performing a test on the target test U-shield corresponding to the target test data based on the current occupancy state, the method further includes: generating a data release command in response to the execution test of the target test U-shield; and performing a release operation on the target test data of the completed target test U-shield in response to the data release command, so as to update the centralized U-shield test information.

[0012] The second aspect of this disclosure provides a USB key testing device for assisting centralized USB key testing management, comprising an information acquisition module, a status determination module, and a test execution module. The information acquisition module acquires test data information matching the business testing category of the target USB key being tested; the status determination module determines the current occupancy status of the target test data corresponding to the centralized USB key testing management based on the centralized USB key testing information; and the test execution module performs testing on the target USB key corresponding to the target test data based on the current occupancy status.

[0013] A third aspect of this disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the aforementioned U-shield testing method for assisted centralized U-shield testing management.

[0014] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the aforementioned U-shield testing method for assisted centralized U-shield testing management.

[0015] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned U-shield testing method for assisted centralized U-shield testing management.

[0016] This disclosure provides a U-shield testing method, apparatus, equipment, medium, and program product to assist centralized U-shield testing management. The U-shield testing method includes: acquiring test data information matching the business testing category of the target U-shield; determining the current occupancy status of the target test data corresponding to the centralized U-shield testing information; and performing testing on the target U-shield corresponding to the target test data based on the current occupancy status. Therefore, compared to the data interference caused by insufficient testing U-shield equipment in existing centralized U-shield testing management processes, this method achieves consistency between the test data of each tester and the centralized test data. This significantly avoids data interference caused by inconsistent query rules and methods used by different testers, preventing data from interfering with each other after multiple uses and generating dirty or abnormal data. This greatly improves the reliability of test results, enhances the quality of test data preparation, and ensures the efficiency of U-shield testing, thereby significantly improving the testing efficiency of U-shield business applications and the level of U-shield testing management. Attached Figure Description

[0017] The foregoing contents, as well as other objects, features, and advantages of this disclosure, will become clearer from the following description of embodiments with reference to the accompanying drawings, in which:

[0018] Figure 1 The illustration schematically depicts an application scenario of a U-shield testing method, apparatus, device, medium, and program product for assisted centralized U-shield testing management according to embodiments of the present disclosure.

[0019] Figure 2 A flowchart illustrating a U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure is shown schematically.

[0020] Figure 3 This diagram schematically illustrates another application scenario of the U-shield testing method for assisted centralized U-shield testing management according to embodiments of the present disclosure;

[0021] Figure 4A This illustration schematically shows a display content diagram of a target test U-shield in a U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure;

[0022] Figure 4B This schematically illustrates another display of a target U-shield in a U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure;

[0023] Figure 5 This schematically illustrates a structural block diagram of a U-shield testing device for assisted centralized U-shield testing management according to an embodiment of the present disclosure; and

[0024] Figure 6 A block diagram of an electronic device suitable for implementing a U-shield testing method for assisted centralized U-shield testing management, according to an embodiment of the present disclosure, is shown schematically. Detailed Implementation

[0025] The embodiments of the present disclosure will now be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the disclosure. In the following detailed description, numerous specific details are set forth to provide a thorough understanding of the embodiments of the present disclosure for ease of explanation. However, it will be apparent that one or more embodiments may be practiced without these specific details. Furthermore, descriptions of well-known structures and techniques are omitted in the following description to avoid unnecessarily obscuring the concepts of the present disclosure.

[0026] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The terms “comprising,” “including,” etc., as used herein indicate the presence of the stated features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0027] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein are to be interpreted in a manner consistent with the context of this specification, and not in an idealized or overly rigid way.

[0028] When using expressions such as "at least one of A, B, and C", they should generally be interpreted in accordance with the meaning that is commonly understood by a person skilled in the art (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, a system having A alone, a system having B alone, a system having C alone, a system having A and B, a system having A and C, a system having B and C, and / or a system having A, B, and C, etc.).

[0029] In financial transactions, U-shield physical security devices (i.e., U-shields or U-shield devices) are widely used in banks and other financial institutions for various high-risk and high-importance transactions as a type of identity authentication security medium with high encryption security and low application and promotion costs. They can authenticate the identity of the user who is currently entering the command, ensuring that the transaction operation represents the user's true intention.

[0030] As a secure identity authentication medium, the digital certificate stored in the U-shield is unique. Each customer has their own digital certificate, which is stored and bound to a dedicated U-shield device for use. The U-shield and the customer account are one-to-one. Each account can only use the corresponding U-shield for transaction authorization. U-shield devices of different accounts and different users cannot be exchanged for each other.

[0031] During acceptance testing of USB token transactions, testers must use actual physical USB tokens and load pre-defined test data into them to ensure functional correctness. When there are many testers and the version is large, the preparation of USB token test data, its creation, and the preparation and exchange of physical USB token media require a significant amount of work. Therefore, a centralized deployment scheme for USB token physical devices is often adopted to reduce the resources required to prepare individual USB token test devices.

[0032] Among them, a centralized U-shield testing deployment solution is adopted. During the test execution process, large-scale operations will use a unified U-shield backend deployment, unified test data management, unified test record tracking, and unified test log capture mode for integrated management, which facilitates overall processing. Automated technologies are usually introduced to centrally manage test data preparation, U-shield digital certificate injection, U-shield physical button clicks, and U-shield screen display information collection. This includes pre-setting test data extraction rules, adding centralized management and injection of U-shield certificates, automatic U-shield physical button clicks, automatic collection of U-shield screen display information, and matching and analysis of operation logs and execution results. While reducing the resource input in the testing process, it also greatly improves the standardization and quality of test result analysis and reduces problems such as data reuse conflicts.

[0033] However, for the aforementioned USB key testing model, during peak version testing periods, when the number of physically deployed USB key testing devices in the backend is insufficient, the deployment and online provisioning of the centrally deployed testing media takes a considerable amount of time. Therefore, the timely deployment of additional devices cannot be guaranteed during the testing process. Testers either have to wait or manually prepare data through various transactions, which can lead to issues such as duplicate data preparation and log interference. Typically, testers reserve some blank USB keys as emergency resources during testing. In situations like the aforementioned problems, they manually query the required test data in the test environment, create digital certificates, and install the corresponding digital certificates into the USB key devices before commencing testing.

[0034] However, this work model suffers from several problems. Firstly, the inconsistent query rules and methods used by testers during data extraction, coupled with discrepancies in the target data range and repeated referencing of the same data, can lead to inconsistencies. Secondly, the large number of testers conducting tests simultaneously—some using centralized USB-shield testing equipment, others using individually prepared USB-shields—often results in inconsistent data extraction rules. This inconsistency leads to interference from multiple tests by different personnel, generating dirty and abnormal data, ultimately reducing the reliability of test results and significantly decreasing testing efficiency.

[0035] Meanwhile, the button operations of the test USB tokens manually prepared by testers, as well as the corresponding screen feedback information after the operations, cannot be collected centrally and uniformly. This results in missing test log information, and when troubleshooting problems, the incomplete test execution log information corresponding to the manually prepared USB tokens easily leads to low troubleshooting efficiency. Moreover, during the testing process using their own manually prepared test USB tokens, the repeated manual button clicks and checks interrupt the operation, increasing the workload for testers and significantly impacting the overall efficiency of the test execution process.

[0036] For example, during the creation of the backend USB key, the payment account data 0200003309220022346 from the Account Manager account was extracted for the purchase of the wealth management product "No Fixed Term Ultra-Short-Term RMB Wealth Management Product - 0701CDQB" in the corporate wealth management enterprise online channel business. However, when a business person was verifying the batch payment instruction submission, they found that all the USB key devices centrally stored in the backend were occupied, and they had to manually prepare the test data, also using the payment account of the Account Manager account. After the two different businesses completed the transactions, they needed to verify the account balance. When the transactions were executed simultaneously and the amounts in the accounts were changed at the same time, the final balance would be inconsistent with the expectation: "Available balance verification: failed. [Available Balance] A2: 28105302.65, [Available Balance] A1: 28107402.65, [Purchase Share] D1: 10000", thus causing the test verification result to fail to meet expectations.

[0037] Therefore, to address the technical problem of low efficiency in U-shield testing due to insufficient U-shield testing equipment in traditional centralized U-shield testing solutions during peak version testing periods, which causes data interference (such as data duplication, data anomalies, and dirty data) among testers, this disclosure provides a U-shield testing method, device, equipment, media, and program product that can significantly avoid data interference problems such as duplicate use of test data or dirty data caused by inconsistent extraction standards, improve the reliability of test results, ensure the quality of test data, and thus improve the efficiency of business testing.

[0038] It should be noted that the U-shield testing method and apparatus for assisting centralized U-shield testing management described in the embodiments of this disclosure can be used in the fields of big data technology and artificial intelligence technology, as well as in the financial field and any field outside the financial field. The application fields of the U-shield testing method and apparatus for assisting centralized U-shield testing management described in the embodiments of this disclosure are not limited.

[0039] In the technical solution disclosed herein, the collection, storage, use, processing, transmission, provision, disclosure, and application of data, including user personal information, all comply with relevant laws and regulations, necessary confidentiality measures have been taken, and they do not violate public order and good morals. Furthermore, user authorization or consent has been obtained before acquiring or collecting user personal information.

[0040] The embodiments of this disclosure provide a U-shield testing method to assist centralized U-shield test management, including: acquiring test data information matching the business test category of the target U-shield; determining the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management; and performing a test on the target U-shield corresponding to the target test data based on the current occupancy status.

[0041] Figure 1 The diagram illustrates an application scenario of a U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure.

[0042] like Figure 1 As shown, application scenario 100 according to this embodiment may include terminal devices 101, 102, and 103, network 104, and server 105. Network 104 is used as a medium to provide a communication link between terminal devices 101, 102, and 103 and server 105. Network 104 may include various connection types, such as wired or wireless communication links or fiber optic cables, etc.

[0043] Users can use terminal devices 101, 102, and 103 to interact with server 105 via network 104 to receive or send messages, etc. Various communication client applications can be installed on terminal devices 101, 102, and 103, such as shopping applications, web browser applications, search applications, instant messaging tools, email clients, social media platform software, etc. (for example only).

[0044] Terminal devices 101, 102, and 103 can be various electronic devices with displays and web browsing capabilities, including but not limited to smartphones, tablets, laptops, and desktop computers.

[0045] Server 105 can be a server that provides various services, such as a backend management server that supports websites browsed by users using terminal devices 101, 102, and 103 (for example only). The backend management server can analyze and process data such as received user requests, and feed back the processing results (such as web pages, information, or data obtained or generated according to user requests) to the terminal devices.

[0046] It should be noted that the U-shield testing method for centralized U-shield testing management provided in this embodiment can generally be executed by server 105. Correspondingly, the U-shield testing device for centralized U-shield testing management provided in this embodiment can generally be located in server 105. The U-shield testing method for centralized U-shield testing management provided in this embodiment can also be executed by a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105. Correspondingly, the U-shield testing device for centralized U-shield testing management provided in this embodiment can also be located in a server or server cluster that is different from server 105 and capable of communicating with terminal devices 101, 102, 103 and / or server 105.

[0047] It should be understood that Figure 1 The number of terminal devices, networks, and servers shown is merely illustrative. Depending on implementation needs, any number of terminal devices, networks, and servers can be included.

[0048] The following will be based on Figure 1 The described scene, through Figures 2-6 The U-shield testing method for assisted centralized U-shield testing management according to the disclosed embodiments is described in detail.

[0049] Figure 2 A flowchart illustrating a U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure is shown.

[0050] like Figure 2 As shown, the U-shield testing method for the auxiliary centralized U-shield testing management in this embodiment includes operations S201-S203.

[0051] In operation S201, obtain test data information that matches the business test category of the target test U-shield;

[0052] In operation S202, based on the centralized U-shield test information corresponding to the centralized U-shield test management, the current occupancy status of the target test data corresponding to the test data information is determined; and

[0053] In operation S203, based on the current occupancy status, a test is performed on the target test U-shield corresponding to the target test data.

[0054] Centralized USB key testing involves testing a large number of USB key devices in a centralized manner. The unified retrieval, binding, and testing of test data for this type of centralized testing requires efficient management to ensure optimal testing results. While centralized USB key testing can handle large numbers of devices, a single centralized USB key test management device typically only supports one tester. During peak version testing periods, when the number of centralized USB key test management devices is insufficient, other testers either have to wait or perform manual testing. This can easily lead to data interference, such as duplicate data preparation and log conflicts, between centralized and manual testing. Furthermore, manual testing is prone to inconsistencies in test data range standards due to differences in rules or methods, resulting in repeated referencing of the same data. This further generates dirty and abnormal data, reducing the reliability of test results and significantly decreasing testing efficiency.

[0055] In the event of a shortage of centralized USB key testing equipment during peak testing periods, the target USB key will be the USB key device to be tested by other testers who are no longer conducting centralized USB key testing. The business test category refers to the business category of the target test data for the aforementioned target USB key. This category can be set according to specific business content. For example, personal online banking, corporate wealth management, and pension wealth management are all different business categories with different business contents, and the corresponding test data will also differ. The test data information is a collection of business test data corresponding to a specific business test category. For example, the personal online banking business test category corresponds to one set of test data information, which includes business test data for multiple different account names or account numbers. These business test data can all be used as test data to match the target USB key and achieve the corresponding USB key testing objectives. The test data information can be stored in the form of a data table in a corresponding database or cloud database for easy retrieval and execution at any time.

[0056] For each centralized USB key testing device, the test log data generated during its corresponding USB key testing process is uploaded and updated in real time, thus forming centralized USB key testing information. Centralized USB key testing information is a collection of test log data generated by at least one centralized USB key testing device during the USB key testing process. The test log data includes log records such as the real-time test status of each USB key participating in the corresponding centralized USB key testing device. All relevant data of each USB key device throughout the entire testing process is categorized and stored, and can be updated in real time. The centralized USB key testing information can be stored in the form of a data table in a corresponding database or cloud database to reflect the current status of each business test data during the centralized USB key testing process at the current moment.

[0057] The target test data refers to the business test data corresponding to the target test USB key that matches the business test type required by the tester. It can be used to bind with the target test USB key provided by the tester and to execute the test process. The target test data is one of many business test data within the test data information, matching the corresponding business test category. The current occupancy status refers to the test occupancy information of the target test data at the current moment in the corresponding centralized U-shield test information. For example, if the current status of the business test data corresponding to the target test data in the centralized U-shield test information is "occupied," then the business test data is in the test execution state during the centralized U-shield test at the current moment. In other words, the current occupancy status of the corresponding target test data is "occupied" or "unavailable," and it is impossible to bind the target test data with the target test U-shield in this case. However, if the current status of the business test data corresponding to the target test data in the centralized U-shield test information is "idle," then the business test data is not in the test execution state during the centralized U-shield test at the current moment. In other words, the current occupancy status of the corresponding target test data is "idle" or "available," and it is possible to bind the target test data with the target test U-shield, thereby enabling the test execution of the target test U-shield.

[0058] When the current occupancy status of the business test data corresponding to the target test data is idle or available as reflected in the centralized U-shield test information, the corresponding target test U-shield can be tested based on the target test data. This provides an alternative U-shield testing solution while ensuring the centralized U-shield testing process, thus achieving an auxiliary effect on the entire centralized U-shield test management, avoiding testers' waiting time, and preventing data interference with centralized testing during the entire testing process, significantly improving testing speed and efficiency.

[0059] Therefore, compared to the data interference caused by insufficient testing U-shield equipment in the existing centralized U-shield testing management process, this method can unify the testing data of each tester with the centralized testing data. This significantly avoids data interference caused by inconsistent query rules and methods used by different testers, thus preventing data from interfering with each other after multiple uses and generating dirty or abnormal data. This greatly improves the reliability of test results, enhances the quality of test data preparation, and ensures the efficiency of U-shield testing. As a result, it greatly improves the testing efficiency of U-shield business applications and the level of U-shield testing management.

[0060] This disclosure further provides a U-shield testing auxiliary device for implementing the U-shield testing method of the above-described auxiliary centralized U-shield testing management in this disclosure. The U-shield testing auxiliary device may include a communication connection module, a U-shield device user console, a test data extraction module, a U-shield certificate injection module, a U-shield click operation module, a U-shield display information acquisition module, a U-shield device connection management module, and a U-shield device operation log recording module, etc.

[0061] The communication connection module can establish a data connection channel with the cloud database or database containing test data and / or centralized U-shield test information via 5G communication mode and other communication methods. It also interacts with the data to obtain information such as the business test category of available test data, corresponding data extraction rules, test data usage application status, U-shield button click operation logs, and U-shield screen display information logs. The U-shield device user console mainly provides testers with functions such as selecting the business test category of U-shield test data, viewing test data extraction rules, selecting target test data, releasing business test data, creating U-shield digital certificates, binding U-shield digital certificates, clicking buttons on the U-shield device, and displaying information on the U-shield device screen. The test data extraction module primarily responds to extraction commands to testers to extract business test data. During extraction, it first obtains the data extraction rules and interacts with the centralized U-Shield cloud device to acquire information on currently occupied test data. Using standard extraction rules, it obtains unoccupied business test data and provides it to testers for selection. After selecting a target test data, the tester can interact with the centralized U-Shield cloud device to request its use for subsequent auxiliary testing. If successful, it provides a success notification, updates the test data's status in real-time, and calls the U-Shield certificate injection module to inject the corresponding digital certificate. If unsuccessful, it notifies the user of failure and prompts them to select another target test data. The U-Shield certificate injection module generates a corresponding U-Shield digital certificate from the target test data provided by the test data extraction module, injects and binds the digital certificate to the connected target U-Shield, and provides feedback on the digital certificate injection and binding result to the U-Shield device user console. The U-Shield click operation module can receive click commands from the user's console of the U-Shield device, call the clicker to perform physical button clicks on the U-Shield device, and feed the click operation results back to the U-Shield device's operation log recording module as operation log information. Simultaneously, it can also call the U-Shield display information acquisition module to capture the information displayed on the U-Shield device's screen. The U-Shield display information acquisition module is mainly used to collect information displayed on the U-Shield device and feed the corresponding collected information back to the operation log recording module and the user console interface. It also feeds the screen-captured information back to the U-Shield device's operation log recording module as operation log information. The U-Shield device connection management module is mainly used to manage the usage status of the target test U-Shield device on the current auxiliary testing device. It is responsible for establishing and disconnecting the data connection link between the current auxiliary testing device and the target test U-Shield device, recording the test target data corresponding to the certificate used by the current test U-Shield, and calling the communication connection module to establish a data communication link between the auxiliary testing device and the centralized U-Shield cloud testing device.The U-Shield device operation log recording module is mainly used to record the user's U-Shield operation and the information displayed by the U-Shield device, and to feed the relevant operation logs back to the corresponding database or cloud database.

[0062] Figure 3 This illustration schematically shows another application scenario of the U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure.

[0063] like Figure 2 and Figure 3 As shown, according to an embodiment of this disclosure, before obtaining test data information matching the business test category of the target test U-shield as described in operation S201, the method further includes:

[0064] Obtain the current status information of the target test U-shield;

[0065] Based on the current status information, preprocessing is performed on the target test U-shield.

[0066] like Figure 3 As shown, in operation S301, the connection between the U-shield device and the auxiliary testing device can be realized. For example, U-shield devices 1-3 can be connected to the corresponding auxiliary testing device to realize the connection management of the corresponding U-shield devices. Specifically, refer to the corresponding communication connection module and the U-shield device user console. The U-shield device user console can be a device or system that provides display and operation functions and has a visual display screen. Testers can log in to the U-shield device user console using their account password and manually connect multiple U-shields to be tested to the system of the U-shield device user console. By clicking the U-shield device connection, data connection can be established between each U-shield device and the U-shield device connection association module, thus realizing the connection link between the U-shield device and a database or cloud database.

[0067] For the connected USB security tokens, at least one can be selected as the target test USB security token, depending on the tester's needs. At this time, the current status information of the target test USB security token can be obtained through the communication connection module. This current status information includes the target test USB security token's digital certificate, corresponding business test data, and its corresponding business test category, among other test-related status data. The target test USB security token can also be an idle USB security token, i.e., without a bound digital certificate or business test data.

[0068] If the target test U-shield reported by the current status information is a non-empty U-shield device, then the business test data in the target test U-shield needs to be extracted and compared with multiple business test data in the centralized U-shield test information stored in the database or cloud database. When the business test data corresponds to one of the business test data in the centralized U-shield test information, the subsequent test execution operation can be performed on the target test U-shield. When the business test data cannot be found in the corresponding centralized U-shield test information, then the target test U-shield needs to be preprocessed, specifically, the business test data in the target test U-shield is unbound to form an empty target test U-shield.

[0069] This ensures that the business test data in each target test USB key matches the test requirements. If the data does not match the test requirements, the business test data of the target test USB key can be preprocessed to prevent interference with the test data due to mismatch in business test data during subsequent business test execution.

[0070] like Figure 2 and Figure 3 As shown, according to an embodiment of this disclosure, the step of obtaining test data information matching the business test category of the target test U-shield in operation S201 includes:

[0071] According to the preset data extraction rules, business test data corresponding to the business test category is extracted to form the test data information.

[0072] like Figure 3 As shown in operations 321 and S302, for the target test U-shield in an idle state, testers need to extract and bind business test data according to test requirements to achieve subsequent corresponding business tests. The preset data extraction rule is the data retrieval rule between the data extraction command issued by the tester and the business test data in the corresponding database or cloud database. That is, according to the business test category defined by the tester, the system can generate a data extraction command for the business test data matching the corresponding business test category. In response to the data extraction command, the system can further extract the business test data of the corresponding business test category in the database or cloud database, forming a set of business test data corresponding to the same business test category as the test data information to constitute an available data list, as shown in Table 1 below.

[0073]

[0074]

[0075] Table 1

[0076] As shown in Table 1, for the business test category belonging to "Personal Online Banking," multiple business test data sets can be generated. Each business test data set includes parameters for multiple attributes such as business category, operation permissions, user account data usage status, occupation category, occupation device number, associated U-shield, start time of use, and end time of use. The parameters for each attribute are different. This allows for precise extraction of multiple business test data sets within the same business test category. Specifically, in operation S302, the user can select the desired business test category, such as Personal Online Banking, Corporate Wealth Management, or Pension Wealth Management, through the U-shield device's user console. The selected business test category then interacts with a database or cloud database to retrieve the corresponding business test data as an available data list.

[0077] By extracting test data information according to the above-mentioned preset data extraction rules, the extracted test data information can be guaranteed to match the corresponding business test needs. This can effectively prevent the business test data from being inconsistent with the business test data in the database or cloud database, avoid mutual interference between test data, and ensure that the test data of the target test U-shield can be consistent with the overall centralized test data management content, thus strongly guaranteeing the accuracy of the test results.

[0078] like Figure 2 and Figure 3 As shown, according to an embodiment of this disclosure, in operation S202, determining the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management includes:

[0079] Query the target test data in the test data information;

[0080] In response to a received data retrieval command corresponding to the target test data, the centralized USB key test information is retrieved; and

[0081] Based on the centralized U-shield test information, determine the current occupancy status of the target test data.

[0082] like Figure 3 As shown, in operation S304, the target test data can be selected according to the testing needs of the business testers. For example, through the U-shield device user console, the testers can directly select a specific business test data from the available data list as the target test data. The U-shield device user console can respond to the tester's selection operation by generating a data query command. Executing the data query command will retrieve the business test data specified by the tester as the target test data from the corresponding test data information.

[0083] Furthermore, in operation S304, in response to the retrieved target test data, a data retrieval instruction can be directly generated based on the target test data. The data retrieval instruction is sent to the database or cloud database, and after the database or cloud database receives the data retrieval instruction, it performs the corresponding retrieval operation on the stored centralized U-shield test information.

[0084] This ensures that the usage status of the current business test data corresponding to the target test data can be determined during the centralized U-shield testing process, thereby preventing data interference caused by inconsistencies between the target test data and the centralized / U-shield test information during the testing of the target test U-shield.

[0085] like Figure 2 and Figure 3 As shown, according to an embodiment of this disclosure, determining the current occupancy status of the target test data based on the centralized U-shield test information includes:

[0086] When the current test data corresponding to the target test data in the centralized U-shield test information is in an idle state, then the current occupancy state of the target test data is idle; or

[0087] When the current test data corresponding to the target test data in the centralized U-shield test information is in a test state, the current occupancy status of the target test data is occupied.

[0088] like Figure 3 As shown, in operation S341, the corresponding target test data is matched in the retrieved centralized U-shield test information. It is then queried whether there is business test data consistent with the target test data. Simultaneously, the test occupancy information of the business test data at the current moment in the centralized U-shield test process is determined as the current occupancy status. If the current status of the business test data corresponding to the target test data in the centralized U-shield test information is "occupied," then the business test data is in the test execution state during the current centralized U-shield test process. In other words, the current occupancy status of the corresponding target test data is "occupied" or "unavailable," and thus the operation of binding the target test data with the target test U-shield cannot be achieved. However, if the current status of the business test data corresponding to the target test data in the centralized U-shield test information is "idle," then the business test data is not in the test execution state during the current centralized U-shield test process. In other words, the current occupancy status of the corresponding target test data is "idle" or "available," and thus the operation of binding the target test data with the target test U-shield can be achieved, thereby enabling the test execution of the target test U-shield.

[0089] In other words, corresponding to the target test data, the user interface of the U-shield device can send the target test data to the database or cloud database to request its use. If the use is successful, a success message will be sent, and the target test data will be updated in the database or cloud database, marking it as currently used. If the use fails, the user will be notified of the failure and prompted to select a new target test data.

[0090] Therefore, compared to the data interference caused by insufficient testing equipment in the existing centralized U-shield testing management process, which results in data interference from different testers, this method can unify the target test data in the auxiliary testing process with the business test data in the centralized U-shield testing process. This prevents data interference such as dirty data and abnormal data from mutual influence after multiple uses of business test data during the simultaneous U-shield testing process. This greatly improves the reliability of test results, enhances the quality of test data preparation, and ensures the efficiency of U-shield testing and usage. As a result, it significantly improves the testing efficiency of U-shield business applications and the level of U-shield testing management.

[0091] like Figure 2 and Figure 3 As shown, according to an embodiment of this disclosure, in operation S203, which involves performing a test on the target test U-shield corresponding to the target test data based on the current occupancy state, the following steps are included:

[0092] Based on the current occupancy status, a digital certificate matching the target test data is invoked and injected into the target test USB shield;

[0093] Perform a test click operation on the target test U-shield that has completed the digital certificate infusion.

[0094] As mentioned above, if the current state of the business test data corresponding to the target test data in the centralized U-shield test information is idle at the current moment, then the business test data is not in the test execution state during the centralized U-shield test at the current moment. In other words, the current occupation state of the corresponding target test data is idle or available. At this time, the operation of binding the target test data with the target test U-shield can be realized, thereby enabling the test execution of the target test U-shield.

[0095] like Figure 3As shown, in operations S342, S343, and S307, if the business test data in the centralized U-shield test information corresponding to the target test data is in an idle state, then no test is performed on the business test data during the centralized U-shield test process. This means the target test data can be bound to the target test U-shield for the next U-shield test process. First, a digital certificate can be invoked based on the target test data. If no corresponding digital certificate exists, the corresponding digital certificate can be generated using the U-shield certificate infusion module, as in operation S342. Based on this, in operation S343, the corresponding digital certificate is invoked again. The corresponding digital certificate is infused into the target test U-shield through the U-shield certificate infusion operation, realizing the infusion and binding process. This ensures the binding operation between the digital certificate and the target test U-shield, establishing a correspondence between the corresponding U-shield digital certificate and the target test U-shield, as shown in Table 2 below.

[0096]

[0097]

[0098] Table 2

[0099] As shown in Table 2, the certificate code 4CBSY03020802.c.0200 of the U-shield digital certificate is matched with the U-shield number 5300016804 of the target test U-shield. This allows for the binding of the two, ensuring that the test click operation on the U-shield device corresponds to the business test content of the corresponding target test data.

[0100] For each target test USB key device, each USB key device can have multiple buttons and a display screen. Clicking these buttons according to the content displayed on the display screen can realize the test click operation of the target test USB key, that is, complete the test execution of the corresponding USB key device.

[0101] Therefore, based on the current occupancy status of the target test data, the target test U-shield can be synchronized with the centralized U-test process, ensuring that the test processes of the two do not interfere with each other. This avoids data interference caused by dirty or abnormal data due to the occupancy of business test data, greatly improving the reliability of test results, enhancing the quality of test data preparation, and ensuring the efficiency of U-shield testing. Consequently, it significantly improves the testing efficiency of U-shield business applications and the level of U-shield test management.

[0102] It should be noted that in operation S305, for the user console of the U-shield device, it can update the current status of the corresponding business test data based on the binding of the target test U-shield and the digital certificate corresponding to the target test data. This includes displaying the text "The corresponding target test U-shield has been bound to a digital certificate" or directly pushing a green display box indicating "The corresponding target test U-shield has been bound to a digital certificate" to the tester, and updating and storing this information. Furthermore, before performing the click test, in operation S306, the U-shield display information acquisition module can collect the display content of the target test U-shield to be clicked, thereby ensuring that the display content of the target test U-shield's screen can be automatically acquired before and after each click stage during the click test.

[0103] Figure 4A This schematically illustrates a display of the target test U-shield in a U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure; Figure 4B This schematically illustrates another display diagram of the target test U-shield in the U-shield testing method for assisted centralized U-shield testing management according to an embodiment of the present disclosure.

[0104] Among them, such as Figures 4A-4B As shown, the target test U-shield of this embodiment may include four main function buttons 430, namely C cancel button, ∧ page turn button, ∨ page turn button and OK confirm button, and also has a display screen that can display the display area 420. The display area 420 and the function buttons 430 are mainly composed of the housing 410 to form the overall composition of the U-shield device.

[0105] like Figures 2-4B As shown, according to an embodiment of this disclosure, the step of performing a test click operation on the target test U-shield after the digital certificate has been infused includes:

[0106] In response to the received click control command, the target test U-shield is clicked according to the preset click position correspondence;

[0107] Obtain the click feedback information generated when the target test U-shield is clicked.

[0108] like Figures 3-4BAs shown, in operation S307, after the digital certificate of the target test U-shield is installed, click testing of the target test U-shield can be realized. Specifically, the click control command is a control command generated based on the operation of the tester at the U-shield device user console, which can be used to control the click operation corresponding to the target test U-shield when executed. The preset click position correspondence is the set correspondence between at least one clicker and each function button 430 of the corresponding target test U-shield, thereby ensuring the accurate click of each function button 430. Multiple clickers can be used, each clicker corresponding to one function button of the target test U-shield, thus ensuring accurate click operation for each target test U-shield. Alternatively, a single clicker can click each function button of the target test U-shield according to a set click movement trajectory, thereby saving the number of clickers and improving the level of automated click testing.

[0109] During the click test operation, for each click of a function button on the target test U-shield, the target test U-shield should display different corresponding text or graphic content in the display area 420 as click feedback information. Specifically, this click feedback information could be the first click of the OK function button, such as... Figure 4A The display area 420 shows the content of "Product Name: Industrial and Commercial Bank of China 'Weekly Dividend' Ultra-Short-Term Corporate RMB Wealth Management Product"; and the click feedback information can be displayed when the OK button is clicked again, such as... Figure 4B The display area 420 shows the message "Operation Successful". Therefore, based on the set click operation rules, after detecting the click feedback information after each click operation, the system can either perform the next click operation on a specific function key or stop the click test operation based on this feedback information. Specifically, this click feedback information can be collected and detected by the U-shield display information acquisition module. Alternatively, the above click operation process can also be performed by the tester manually controlling the corresponding clicker to control the click operation of multiple function keys based on the display content of the target test U-shield through the user control panel of the U-shield device.

[0110] In operation S351, all operation information before and after the aforementioned click test operation, as well as the click feedback information and other display information of the target test U-shield, can be fed back to the U-shield device operation log recording module for recording usage information. Specifically, the tester can click the confirmation button of the U-shield under test (which actually corresponds to the OK button on the target test U-shield) on the U-shield device control panel. At the same time, the U-shield device control panel recognizes the target test U-shield as a portable U-shield device. Based on the U-shield's internal U-shield position and the relationship between the U-shield and the clicker, it first calls the collector in the portable U-shield to collect the display content of the current U-shield's information display area. Then, it calls the clicker inside the portable U-shield device to click the OK button on the U-shield. After the click is completed, the collector inside the portable U-shield device collects the display content of the U-shield's transaction information display area again, displays it on the U-shield device control panel, and records the corresponding log.

[0111] This allows for the simultaneous testing of other testers' target U-shields during centralized U-shield testing, ultimately ensuring that centralized U-shield testing can be used to simultaneously test more other U-shield devices. While ensuring that test data does not interfere with each other, it significantly improves testing efficiency and provides testers with a highly efficient and scalable auxiliary testing solution based on centralized U-shield testing.

[0112] Furthermore, by collecting automatic control and display information from the U-shield click test, it can support automatic clicking of the physical buttons on the U-shield and automatic capture of the information displayed on the U-shield screen after clicking, facilitating unified operation and viewing by testers. It can also automatically capture testers' records of U-shield button operations and the information displayed on the U-shield device screen after button operations, and upload them to the management platform for centralized management, eliminating the workload of each tester recording the test execution process log through text, screenshots, photos, etc.

[0113] like Figures 2-4B As shown, according to an embodiment of this disclosure, after operation S203 performs a test on the target test U-shield corresponding to the target test data based on the current occupancy state, the method further includes:

[0114] In response to the execution test of the target test U-shield, a data release command is generated;

[0115] In response to the data release command, a release operation is performed on the target test data of the target test U-shield that has completed the test, so as to update the centralized U-shield test information.

[0116] The data release command is a control command generated in response to the completion of the execution test of the target test U-shield. It is designed to control the unbinding between the target test U-shield and its corresponding target test data after the test execution is completed, that is, to release the target test data relative to the target test U-shield.

[0117] like Figure 3 As shown, in operations S308-S343, in response to the execution of the data release command, the target test USB key that has completed the test execution can be released, that is, the association between the target test USB key and the target test data is broken. In this way, the target test data achieves an idle state relative to the centralized USB key testing process, and can be used as business test data for subsequent centralized USB key tests or auxiliary tests of other target test USB keys. For example, in operation S308, after the tester finishes the test, they can choose to click "Data Release" to release the use of the business test data. The data extraction module can issue a data release command, setting the corresponding business test data status to idle in the centralized USB key test information. At the same time, the USB key certificate injection module removes the association between the digital certificate and the USB key.

[0118] This ensures the storage and updating of corresponding business test data for centralized U-shield test information in databases or cloud databases, effectively guaranteeing the steady progress of subsequent testing.

[0119] In operation S351, the log recording module can be used to record the target test data and the usage of the corresponding target test U-shield during the entire auxiliary U-shield test process. Specifically, the U-shield device operation log recording module can record the operation records of the target test U-shield and the display information of the target test U-shield's display area to generate log data, and transmit the corresponding log data to a database or cloud database for unified storage and management, so that testers can use it for problem tracing and review.

[0120] In summary, the U-shield testing method disclosed above, which assists in centralized U-shield testing management, provides a portable U-shield click testing assistance solution. It can automatically interact with the test U-shield cloud device management platform (such as a cloud database) deployed in centralized U-shield testing. When testers need new test data, they can call the centralized and unified data preparation rules to extract data, create a digital certificate after extraction, and inject it into the U-shield device for binding. This avoids data duplication or dirty data caused by inconsistent extraction standards, and prevents problems such as reduced credibility of test results.

[0121] Meanwhile, by automatically controlling and collecting information from the U-shield click test, it can support the automatic clicking of the physical buttons on the U-shield and the automatic capture of the information displayed on the U-shield screen after the click, making it convenient for testers to perform unified operation and viewing. It can also automatically capture the testers' records of U-shield button operations and the information displayed on the U-shield device screen after the button operation, and upload them to the management platform for centralized management. This eliminates the workload of each tester recording the test execution process log through text, screenshots, photos, etc., and greatly saves manpower costs in the U-shield testing process.

[0122] Clearly, the USB token testing method described in the above-described embodiments of this disclosure can solve the problem that "in the existing centralized testing mode for USB token devices, when centralized USB token testing resources are insufficient, testers use their own reserved USB token devices for testing. This is because the query rules and methods used by different testers during data extraction are inconsistent, and repeated use by different testers leads to mutual interference, resulting in dirty and abnormal data, which reduces the reliability of the test results and significantly reduces testing efficiency." Simultaneously, this USB token testing method provides a convenient operating interface based on the USB token device's user console, enabling automatic clicking of the USB token's physical buttons and automatic capture of the information displayed on the USB token screen after clicking. This facilitates unified operation and viewing by testers, eliminating the workload of manually viewing USB token information and clicking buttons. Furthermore, it simultaneously supports the recording of testers' USB token button operations and the automatic capture of information displayed on the USB token device screen after button operations, uploading this data to a management platform for centralized management, eliminating the workload of each tester recording the test execution process log through text, screenshots, photos, etc.

[0123] To better demonstrate the beneficial effects of the U-shield testing method for centralized U-shield testing management as described in the embodiments of this disclosure, specific implementation examples of centralized U-shield testing are provided below:

[0124] First, the tester logs into the U-shield device user console, clicks the U-shield device connection management module, connects the current portable test U-shield device to the centralized U-shield cloud device, and obtains the current U-shield status information, including the digital certificate and the corresponding test data, through the communication connection module.

[0125] Secondly, testers use the U-Shield device's user console to select the required test data category (e.g., personal online banking, corporate wealth management, pension wealth management, etc.). The selected test data category interacts with the centralized U-Shield cloud device to obtain the corresponding data extraction rules and test data occupancy status, forming a data list for testers to choose from. Specifically, when a tester clicks on a target data item, the U-Shield device's user console sends that data to the centralized U-Shield cloud device to request its use. If the use is successful, a success message is sent, the data is stored, and the corresponding digital certificate is injected using the U-Shield certificate injection module. Simultaneously, the data status is marked as occupied. If the use fails, the user is notified of an attempt to reselect a new target test data item.

[0126] Afterwards, the testers selected the available target test data and clicked "U-Shield Certificate Injection." The U-Shield Certificate Injection module then created a digital certificate and injected it into the currently tested U-Shield. The centralized U-Shield cloud device recorded the correspondence between the U-Shield digital certificate and the target U-Shield.

[0127] Then, the tester selects the desired button on the USB token and submits the click operation. The USB token click operation module in the portable USB token executes the corresponding button click instruction, and the USB token display information acquisition module executes the corresponding screen acquisition results, feeding them back to the user console of the USB token device. Simultaneously, it also feeds back the corresponding information to the USB token device operation log recording module. For example, if the user clicks the confirmation button (corresponding to the OK button on the USB token) on the USB token device console, and the console recognizes the USB token as a portable USB token device, then based on the USB token's internal location and the relationship between the USB token and the clicker, it first calls the collector in the portable USB token to collect information from the current USB token's display area. Then, it calls the clicker inside the portable USB token device to click the OK button on the USB token. After the click is completed, the collector inside the portable USB token device again collects the content of the USB token transaction information display area, displays it on the USB token device console, and records the corresponding log.

[0128] In addition, the U-shield device operation log recording module can record the operation records and U-shield display information, and transmit the corresponding logs to the backend U-shield cloud device for unified data storage and management, so that testers can use it to trace and review problems.

[0129] Finally, after the tester finishes the test, they click "Data Release" to release the test data. The data extraction module and the backend U-Shield cloud device send a data release command, setting the corresponding test data status to idle. Simultaneously, the U-Shield certificate module disconnects the digital certificate from the U-Shield. The log recording module records the usage of this data and the U-Shield.

[0130] Those skilled in the art should understand that although the above implementation examples involve the operation of corresponding test personnel, the U-shield testing method of this disclosure is not limited to human operation, but focuses on the response control of automated operations, ultimately achieving a significant improvement in the automation, intelligence, and accuracy of the auxiliary testing implementation examples. In other words, the U-shield testing method of this disclosure can fully realize highly automated test execution, which will not be elaborated further here.

[0131] Therefore, in conjunction with the above implementation examples, the U-shield testing method of this disclosure effectively solves the problem that in the existing model where enterprises use a backend U-shield cloud device to test U-shield devices, when the resources of the backend U-shield cloud device are insufficient and testers use their own reserved U-shield devices for testing, the inconsistent query rules and methods used by each tester during data extraction, and the mutual interference caused by multiple uses by different testers, result in dirty and abnormal data, leading to a decrease in the reliability of the test results and a significant reduction in testing efficiency. Furthermore, by providing a convenient operation display interface and automatic clicking of the U-shield physical buttons, and automatic capture of the information displayed on the U-shield screen after clicking, it facilitates unified operation and viewing for testers, eliminating the workload of manually viewing U-shield information and clicking buttons. In addition, it supports the recording of testers' U-shield button operations and the automatic capture of the information displayed on the U-shield device screen after button operations, and uploads it to the management platform for centralized management, eliminating the workload of each tester recording the test execution process log through text, screenshots, photos, etc., and allowing batch viewing of the collected results to verify the correctness of the test.

[0132] Based on the aforementioned U-shield testing method for centralized U-shield testing management, this disclosure also provides a U-shield testing device for centralized U-shield testing management. The following will be combined with... Figure 5 The device is described in detail.

[0133] Figure 5 A schematic block diagram of a U-shield testing device for assisted centralized U-shield testing management according to an embodiment of the present disclosure is shown.

[0134] like Figure 5 As shown, the U-shield testing device 500 for centralized U-shield testing management in this embodiment includes an information acquisition module 510, a status determination module 520, and a test execution module 530.

[0135] The information acquisition module 510 is used to acquire test data information that matches the business test category of the target test U-shield. In one embodiment, the information acquisition module 510 can be used to perform the operation S201 described above, which will not be repeated here.

[0136] The status determination module 520 is used to determine the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management. In one embodiment, the status determination module 520 can be used to execute the operation S202 described above, which will not be repeated here.

[0137] The test execution module 530 is used to perform a test on the target test U-shield corresponding to the target test data based on the current occupancy status. In one embodiment, the test execution module 530 can be used to perform the operation S203 described above, which will not be repeated here.

[0138] According to embodiments of this disclosure, any plurality of modules among the information acquisition module 510, the status determination module 520, and the test execution module 530 may be combined into one module, or any one of these modules may be split into multiple modules. Alternatively, at least a portion of the functionality of one or more of these modules may be combined with at least a portion of the functionality of other modules and implemented in one module. According to embodiments of this disclosure, at least one of the information acquisition module 510, the status determination module 520, and the test execution module 530 may be at least partially implemented as hardware circuitry, such as a field-programmable gate array (FPGA), a programmable logic array (PLA), a system-on-a-chip, a system-on-a-substrate, a system-on-package, an application-specific integrated circuit (ASIC), or implemented in hardware or firmware by any other reasonable means of integrating or packaging circuitry, or implemented in any one of software, hardware, and firmware methods, or in a suitable combination of any of these. Alternatively, at least one of the information acquisition module 510, the status determination module 520, and the test execution module 530 may be at least partially implemented as a computer program module, which, when run, can perform corresponding functions.

[0139] A third aspect of this disclosure provides an electronic device, comprising: one or more processors; and a memory for storing one or more programs, wherein when the one or more programs are executed by the one or more processors, the one or more processors perform the aforementioned U-shield testing method for assisted centralized U-shield testing management.

[0140] Figure 6 A block diagram of an electronic device suitable for implementing a U-shield testing method for assisted centralized U-shield testing management, according to an embodiment of the present disclosure, is shown schematically.

[0141] like Figure 6As shown, an electronic device 600 according to an embodiment of this disclosure includes a processor 601, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 602 or a program loaded from a storage portion 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or an associated chipset and / or a special-purpose microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of this disclosure.

[0142] RAM 603 stores various programs and data required for the operation of electronic device 600. Processor 601, ROM 602, and RAM 603 are interconnected via bus 604. Processor 601 performs various operations of the method flow according to embodiments of the present disclosure by executing programs in ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than ROM 602 and RAM 603. Processor 601 may also perform various operations of the method flow according to embodiments of the present disclosure by executing programs stored in said one or more memories.

[0143] According to embodiments of this disclosure, the electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to a bus 604. The electronic device 600 may also include one or more of the following components connected to the I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 608 including a hard disk, etc.; and a communication section 609 including a network interface card such as a LAN card, modem, etc. The communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to the I / O interface 605 as needed. A removable medium 611, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on the drive 610 as needed so that computer programs read from it can be installed into the storage section 608 as needed.

[0144] A fourth aspect of this disclosure also provides a computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the aforementioned U-shield testing method for assisted centralized U-shield testing management.

[0145] This disclosure also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments; or it may exist independently and not assembled into the device / apparatus / system. The computer-readable storage medium carries one or more programs that, when executed, implement the method according to the embodiments of this disclosure.

[0146] According to embodiments of this disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, such as including, but not limited to: portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof. In this disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to embodiments of this disclosure, the computer-readable storage medium may include ROM 602 and / or RAM 603 and / or one or more memories other than ROM 602 and RAM 603 described above.

[0147] The fifth aspect of this disclosure also provides a computer program product, including a computer program that, when executed by a processor, implements the aforementioned U-shield testing method for assisted centralized U-shield testing management.

[0148] Embodiments of this disclosure also include a computer program product comprising a computer program containing program code for performing the methods shown in the flowchart. When the computer program product is run on a computer system, the program code is used to cause the computer system to implement the methods provided in the embodiments of this disclosure.

[0149] When the computer program is executed by the processor 601, it performs the functions defined in the system / apparatus of this disclosure embodiments. According to embodiments of this disclosure, the systems, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0150] In one embodiment, the computer program may rely on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may also be transmitted and distributed in the form of signals over a network medium, and downloaded and installed via the communication section 609, and / or installed from the removable medium 611. The program code contained in the computer program can be transmitted using any suitable network medium, including but not limited to: wireless, wired, etc., or any suitable combination thereof.

[0151] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from the removable medium 611. When the computer program is executed by the processor 601, it performs the functions defined in the system of this disclosure embodiment. According to embodiments of this disclosure, the systems, devices, apparatuses, modules, units, etc., described above can be implemented by computer program modules.

[0152] According to embodiments of this disclosure, program code for executing the computer programs provided in embodiments of this disclosure can be written in any combination of one or more programming languages. Specifically, these computational programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages ​​include, but are not limited to, languages ​​such as Java, C++, Python, "C", or similar programming languages. The program code can execute entirely on the user's computing device, partially on the user's device, partially on a remote computing device, or entirely on a remote computing device or server. In cases involving remote computing devices, the remote computing device can be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0153] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0154] Those skilled in the art will understand that the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways, even if such combinations or combinations are not explicitly described in this disclosure. In particular, the features described in the various embodiments and / or claims of this disclosure can be combined or combined in various ways without departing from the spirit and teachings of this disclosure. All such combinations and / or combinations fall within the scope of this disclosure.

[0155] The embodiments of this disclosure have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of this disclosure. Although various embodiments have been described above, this does not mean that the measures in the various embodiments cannot be used advantageously in combination. The scope of this disclosure is defined by the appended claims and their equivalents. Various substitutions and modifications can be made by those skilled in the art without departing from the scope of this disclosure, and all such substitutions and modifications should fall within the scope of this disclosure.

Claims

1. A U-shield testing method to assist in centralized U-shield testing management, wherein, include: Obtain test data information that matches the business test category of the target test USB key; Based on the centralized U-shield test information corresponding to the centralized U-shield test management, determine the current occupancy status of the target test data corresponding to the test data information; as well as Based on the current occupancy status, a test is performed on the target test U-shield corresponding to the target test data; The step of determining the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management includes: Query the target test data in the test data information; In response to a received data retrieval command corresponding to the target test data, the centralized USB key test information is retrieved; and Based on the centralized U-shield test information, determine the current occupancy status of the target test data; The step of determining the current occupancy status of the target test data based on the centralized U-shield test information includes: When the current test data corresponding to the target test data in the centralized U-shield test information is in an idle state, then the current occupancy state of the target test data is idle; or When the current test data corresponding to the target test data in the centralized U-shield test information is in a test state, the current occupancy status of the target test data is occupied.

2. The method according to claim 1, wherein, Before obtaining test data information that matches the business test category of the target test U-shield, the following steps are also included: Obtain the current status information of the target test U-shield; Based on the current status information, preprocessing is performed on the target test U-shield.

3. The method according to claim 1, wherein, The test data information obtained that matches the business test category of the target test U-shield includes: According to the preset data extraction rules, business test data corresponding to the business test category is extracted to form the test data information.

4. The method according to claim 1, wherein, The process of performing a test on the target test U-shield corresponding to the target test data based on the current occupancy status includes: Based on the current occupancy status, a digital certificate matching the target test data is invoked and injected into the target test USB shield; Perform a test click operation on the target test U-shield that has completed the digital certificate infusion.

5. The method according to claim 4, wherein, The process of performing a test click operation on the target test U-shield after completing the digital certificate infusion includes: In response to the received click control command, the target test U-shield is clicked according to the preset click position correspondence; Obtain the click feedback information generated when the target test U-shield is clicked.

6. The method according to claim 1, wherein, After performing a test on the target test U-shield corresponding to the target test data based on the current occupancy status, the process further includes: In response to the execution test of the target test U-shield, a data release command is generated; In response to the data release command, a release operation is performed on the target test data of the target test U-shield that has completed the test, so as to update the centralized U-shield test information.

7. A U-shield testing device for assisting centralized U-shield testing management, wherein, include: The information acquisition module is used to acquire test data information that matches the business test category of the target test U-shield; The status determination module is used to determine the current occupancy status of the target test data corresponding to the test data information based on the centralized U-shield test information corresponding to the centralized U-shield test management. The step of determining the current occupancy status of the target test data corresponding to the centralized U-shield test information based on the centralized U-shield test management includes: querying the target test data in the test data information; retrieving the centralized U-shield test information in response to a received data retrieval instruction corresponding to the target test data; and determining the current occupancy status of the target test data based on the centralized U-shield test information. The step of determining the current occupancy status of the target test data based on the centralized U-shield test information includes: if the current test data corresponding to the target test data in the centralized U-shield test information is in an idle state, then the current occupancy status of the target test data is idle; or if the current test data corresponding to the target test data in the centralized U-shield test information is in a test state, then the current occupancy status of the target test data is occupied. The test execution module is used to perform tests on the target test U-shield corresponding to the target test data based on the current occupancy status.

8. An electronic device, comprising: One or more processors; Storage device for storing one or more programs. Wherein, when the one or more programs are executed by the one or more processors, the one or more processors perform the method according to any one of claims 1 to 6.

9. A computer-readable storage medium having executable instructions stored thereon, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 6.

10. A computer program product comprising a computer program that, when executed by a processor, implements the method according to any one of claims 1 to 6.

Images