Test analysis method for localization transformation in credential scene

Abstract

The invention provides a test analysis method for localization transformation in a credential scene, and belongs to the technical field of data processing, and the method specifically comprises the steps: obtaining the composition data of target business processes in different business systems, and combining the historical call data of the different business systems to determine that the business systems do not belong to the target business systems; the method comprises the following steps: on the basis of operation coincidence data between target business processes in different business systems, determining an operation coincidence coefficient between the different business systems, determining a matched business system of the business systems based on the operation coincidence coefficient, and obtaining the operation coincidence data between the different target business processes, the test models of different target business processes are constructed in combination with the target business system and the target business processes of the matched business system corresponding to the target business processes, and the test models are used for test analysis of the information system, so that the accuracy of the test result is ensured.

Description

Technical Field

[0001] The present invention belongs to the field of data processing technology, and in particular relates to a testing and analysis method for domestic transformation in an information and communication technology innovation scenario. Background Art

[0002] In the scenario of information innovation, the security of information systems can be greatly improved through the localization of information systems. However, at the same time, compatibility issues will inevitably exist during the migration and transformation of information systems. This makes how to test and analyze the compatibility of information systems after localization a technical problem that needs to be solved urgently.

[0003] In order to test and analyze the information system after the domestic transformation, the invention patent application CN202410947185.0 "A method and system for testing the adaptability of a complete ICT system" obtains the test weight of each test item based on the test data, and adjusts the standard test results obtained by the automated test method based on the test weight, thereby improving the efficiency of the ICT system adaptability test. However, the following technical problems exist: After the localization transformation is completed, it is often necessary to first conduct test analysis of the information system based on the test results of the test case. During the operation of the information system, there may often be multiple business systems running at the same time, which means that a single test case often cannot accurately reflect the actual test results.

[0004] In response to the above-mentioned technical problems, the present invention provides a testing and analysis method for domestic transformation in the information and communication technology innovation scenario. Summary of the invention

[0005] To achieve the purpose of the present invention, the present invention adopts the following technical solutions: According to one aspect of the present invention, a test and analysis method for localization transformation in an information and communication technology innovation scenario is provided.

[0006] A test and analysis method for localization transformation in a trust innovation scenario, specifically including: S1 determines the historical call data corresponding to the business processes of different business systems, uses the historical call data to determine the running overlap data with other business processes, and determines the business processes that need to be tested based on the running overlap data; S2 takes the business process for which test cases need to be constructed as the target business process, obtains the constituent data of the target business process in different business systems, and combines the historical call data of different business systems to determine that the business system does not belong to the target business system, and then proceeds to the next step; S3 determines the operation overlap coefficients between different business systems based on the operation overlap data between target business processes in different business systems, and determines the matching business system of the business system based on the operation overlap coefficients; S4 obtains the operation overlap data between different target business processes, and constructs test models of different target business processes in combination with the target business system and the target business process corresponding to the target business process, and uses the test model to perform test analysis on the information system.

[0007] The beneficial effects of the present invention are: The target business system in the business system is determined based on the composition data and historical call data of the target business processes in different business systems, thereby realizing the screening of target business systems that are used frequently and run in parallel with other business processes based on the composition quantity of the target business processes in the business system and the number of calls of the target business processes. This also lays the foundation for the differentiated construction of target business processes in different business systems and improves the reliability of the test analysis results of the information system.

[0008] Based on the operation overlap data between different target business processes, the target business system and the target business process's corresponding matching business system, test models for different target business processes are constructed. This not only takes into account the operation overlap between the target business processes, but also takes into account the more frequently used target business systems and the matching business systems corresponding to the target business processes, thereby realizing the construction of test models from multiple angles and further ensuring the reliability and accuracy of the test analysis results of the information system.

[0009] A further technical solution is that the historical call data corresponding to the business process includes the historical call times of the business process and the call time periods corresponding to different historical call times.

[0010] A further technical solution is that the operation overlap data includes the number of operation overlaps with other business processes and the operation overlap durations of different operation overlap times.

[0011] A further technical solution is that the method for determining the business process that needs to construct a test case is: Obtaining operation overlap data between the business process and other business processes, and determining the number of operation overlaps between the business process and other business processes; Determine the overlapping business processes in other business processes based on the number of overlapping operations with other business processes; The number of overlapping business processes is used to determine whether the business process is a business process that requires test case construction.

[0012] A further technical solution is that, when the number of overlapping business processes is greater than the preset number of processes, the business process is determined to be a business process that requires test case construction.

[0013] A further technical solution is that the method for constructing the test model of the target business process is: Determine the operation overlap duration between the target business process and other target business processes using the operation overlap data between different target business processes; Based on the overlapping duration of the operation, the overlapping business processes in other target business processes are determined, and the test model of the target business process is determined based on the overlapping business process, the target business process of the target business system, and the target business process of the matching business system corresponding to the target business process, and combined with the target business process.

[0014] Other features and advantages will be described in the following description, and partly become apparent from the description, or understood by practicing the invention. The purpose and other advantages of the invention are realized and obtained by the structures particularly pointed out in the description and the drawings.

[0015] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, preferred embodiments are given below and described in detail with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The above and other features and advantages of the present invention will become more apparent by describing in detail exemplary embodiments thereof with reference to the attached drawings.

[0017] Figure 1 It is a flow chart of the test and analysis method for localization transformation in the scenario of information innovation; Figure 2 It is a flowchart of the method of determining the business process that requires test case construction; Figure 3 It is a flow chart to determine that the business system does not belong to the target business system; Figure 4 It is a flow chart of a method for determining the operation overlap coefficient between business systems. DETAILED DESCRIPTION

[0018] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that the present invention will be comprehensive and complete and fully convey the concepts of the example embodiments to those skilled in the art. The same reference numerals in the figures represent the same or similar structures, and thus their detailed description will be omitted.

[0019] The terms "a", "an", "the", and "said" are used to indicate the presence of one or more elements / components / etc.; the terms "comprising" and "having" are used to express an open-ended inclusive meaning and mean that additional elements / components / etc. may be present in addition to the listed elements / components / etc.

[0020] To solve the above problems, according to one aspect of the present invention, Figure 1 According to one aspect of the present invention, a test and analysis method for localization transformation in a trust innovation scenario is provided, specifically comprising: S1 determines the historical call data corresponding to the business processes of different business systems, uses the historical call data to determine the running overlap data with other business processes, and determines the business processes that need to be tested based on the running overlap data; S2 takes the business process for which test cases need to be constructed as the target business process, obtains the constituent data of the target business process in different business systems, and combines the historical call data of different business systems to determine that the business system does not belong to the target business system, and then proceeds to the next step; S3 determines the operation overlap coefficients between different business systems based on the operation overlap data between target business processes in different business systems, and determines the matching business system of the business system based on the operation overlap coefficients; S4 obtains the operation overlap data between different target business processes, and constructs test models of different target business processes in combination with the target business system and the target business process corresponding to the target business process, and uses the test model to perform test analysis on the information system.

[0021] Furthermore, the historical call data corresponding to the business process includes the historical call times of the business process and the call time periods corresponding to different historical call times.

[0022] Optionally, the operation overlap data includes the number of operation overlaps with other business processes and the operation overlap durations of different operation overlap times.

[0023] Specifically, Figure 2As shown, the method for determining the business process that needs to construct a test case is: Obtaining operation overlap data between the business process and other business processes, and determining the number of operation overlaps between the business process and other business processes; Determine the overlapping business processes in other business processes based on the number of overlapping operations with other business processes; The number of overlapping business processes is used to determine whether the business process is a business process that requires test case construction.

[0024] Further, when the number of the overlapping business processes is greater than the preset number of processes, the business process is determined to be a business process that requires test case construction.

[0025] Optionally, the method for determining the business process that requires test case construction is: S11 determines the number of historical calls corresponding to the business process using the historical call data corresponding to the business process, and determines the operation frequency coefficient of the business process in combination with the call durations of different historical call times; S12: obtaining the operation overlap data of the business process and other business processes, determining the number of operation overlaps between the business process and other business processes, determining the operation overlap coefficient between the business process and other business processes according to the number of operation overlaps between the business process and other business processes and the operation overlap durations of different operation overlap times, and determining the comprehensive overlap coefficient of the business process using the operation overlap coefficient with other business processes; S13 determines the construction requirement coefficient of the business process based on the operation frequency coefficient and the comprehensive overlap coefficient of the business process, and uses the construction requirement coefficient to determine whether the business process is a business process that requires test case construction.

[0026] Furthermore, the comprehensive overlap coefficient of the business process is determined based on the weighted sum of the operation overlap coefficients of the business process and other business processes.

[0027] Specifically, the construction requirement coefficient of the business process is determined according to the average value of the operation frequency coefficient and the comprehensive overlap coefficient of the business process.

[0028] Optionally, the above step S11 includes the following contents: S111 uses the historical call data corresponding to the business process to determine the historical call times corresponding to the business process. When the historical call times corresponding to the business process are less than the preset call times, the process proceeds to step S112. When the historical call times corresponding to the business process are not less than the preset call times, the process proceeds to step S113. S112 obtains the call duration of different historical call times. When there is a historical call time greater than the preset call time, go to step S113. When there is no historical call time greater than the preset call time, it is determined that the business process does not belong to a business process that requires test case construction.

[0029] S113 determines the operation frequency coefficient of the business process based on the number of historical calls corresponding to the business process and the call duration of different historical calls. When the operation frequency coefficient of the business process does not meet the requirements, it is determined that the business process does not belong to the business process that requires test case construction. When the operation frequency coefficient of the business process meets the requirements, proceed to step S12.

[0030] Optionally, the above step S12 includes the following contents: S121 obtains the operation overlap data of the business process and other business processes, determines the number of operation overlaps between the business process and other business processes, and when there are no other business processes whose operation overlap times are greater than the preset overlap times, determines that the business process does not belong to the business process that requires test case construction, and when there are other business processes whose operation overlap times are greater than the preset overlap times, proceeds to step S122; S122 determines the operation overlap coefficient between the business process and other business processes according to the number of operation overlaps between the business process and other business processes and the operation overlap durations of different operation overlap times. When there are other business processes whose operation overlap coefficients are greater than the preset overlap coefficients, the process proceeds to step S123. When there are no other business processes whose operation overlap coefficients are greater than the preset overlap coefficients, the process proceeds to step S124. S123: When the number of other business processes whose running overlap coefficient is greater than the preset overlap coefficient is greater than the preset number of business processes, it is determined that the business process belongs to a business process that requires test case construction; when the number of other business processes whose running overlap coefficient is not greater than the preset overlap coefficient is greater than the preset number of business processes, the process proceeds to step S125; S124: When the number of other business processes that overlap with the business process is less than the process quantity limit, it is determined that the business process does not belong to the business process that requires test case construction; when the number of other business processes that overlap with the business process is not less than the process quantity limit, the process proceeds to step S125; S125 uses the running overlap coefficient with other business processes to determine the comprehensive overlap coefficient of the business process. When the comprehensive overlap coefficient is greater than the preset overlap coefficient threshold, it is determined that the business process belongs to a business process that requires test case construction. When the comprehensive overlap coefficient is not greater than the preset overlap coefficient threshold, it goes to step S13.

[0031] Furthermore, the target business process composition data includes the composition quantity of the target business process in the business process.

[0032] Specifically, Figure 3 As shown, determining that the business system does not belong to the target business system specifically includes: Determining the number of target business processes in the business system based on the constituent data of the target business process in the business system; Determine the historical call times of the business system based on the historical call data in the business system; It is determined whether the business system belongs to the target business system according to the historical call times and the number of target business processes.

[0033] It should be noted that when the number of historical calls of the business system is greater than a preset number threshold and the number of target business processes is greater than a preset process number threshold, it is determined that the business system belongs to the target business system.

[0034] Optionally, determining that the business system does not belong to the target business system specifically includes: Determining the number of target business processes in the business system based on the constituent data of the target business process in the business system, and determining that the business system belongs to the target business system when the number of target business processes in the business system is greater than a set number threshold; When the number of target business processes in the business system is not greater than the set number threshold: When the number of target business processes in the business system is within a preset process number range: Determine the historical call times of the business system based on the historical call data in the business system, and when the historical call times of the business system is greater than a preset call times threshold, determine that the business system belongs to the target business system; When the historical call count of the business system is not greater than the preset call count threshold: Determine the total call processing time of different historical call times based on the call processing time of different historical call times of the business system, and when the total call processing time is greater than a preset time threshold, determine that the business system belongs to the target business system; When the total duration of the call processing is not greater than the preset duration threshold: Obtaining the number of historical calls whose call processing time is longer than the preset call time, and when the number of historical calls whose call processing time is longer than the preset call time is greater than the preset number limit value, determining that the business system belongs to the target business system; When the number of target business processes in the business system is not within the preset process number range or the call processing time is longer than the preset call time and the number of historical calls is not greater than the preset number limit: Determine the historical call times of the business system based on the historical call data in the business system, and determine the call frequency coefficient of the business system based on the call processing time of different historical call times; The system operation matching coefficient of the business system is determined according to the call frequency coefficient and the number of target business processes, and the system operation matching coefficient is used to determine whether the business system belongs to the target business system.

[0035] Furthermore, when the system operation matching coefficient is greater than a preset matching coefficient threshold, the business system is determined to be a target business system.

[0036] Specifically, Figure 4 As shown, the method for determining the operation overlap coefficient between the business systems is: Using the operation overlap data between target business processes in the business system, determine the number of operation overlaps between the target business process of the business system and the target business processes of other business systems, and use the number of operation overlaps to determine the total number of operation overlaps between the target business process of the business system and other business systems; Determine the overlapping business processes between the target business process of the business system and other business systems according to the total number of overlapping operations; Based on the number of overlapping business processes in the business system, an operation overlap coefficient between the business system and other business systems is determined.

[0037] Furthermore, the overlapping business processes between the target business process of the business system and other business systems are target business processes whose total number of running overlaps is greater than a preset number of running overlaps.

[0038] It should also be noted that the operation overlap coefficient between the business system and other business systems is determined according to a preset overlap coefficient corresponding to the number of overlapping business processes in the business system.

[0039] Optionally, the operation overlap coefficient between the business system and other business systems ranges from 0 to 1. When the operation overlap coefficient between the business system and other business systems is greater than a preset coefficient threshold, the other business system is determined to be a matching business system for the business system.

[0040] Specifically, the method for determining the operation overlap coefficient between the business systems is: S21 determines the number of operation overlaps between the target business process of the business system and the target business process of other business systems based on the operation overlap data between the target business processes in the business system; S22 determines the system overlap coefficient between the target business process of the business system and the target business process of other business systems according to the number of operation overlaps between the target business process of the business system and the target business process of other business systems and the operation overlap durations of different operation overlap times; S23 determines the operation overlap coefficient between the business system and other business systems based on the system overlap coefficients of different target business processes in the business system and other business systems.

[0041] Furthermore, the method for constructing the test model of the target business process is: Determine the operation overlap duration between the target business process and other target business processes using the operation overlap data between different target business processes; Based on the overlapping duration of the operation, the overlapping business processes in other target business processes are determined, and the test model of the target business process is determined based on the overlapping business process, the target business process of the target business system, and the target business process of the matching business system corresponding to the target business process, and combined with the target business process.

[0042] Optionally, the above step S21 includes the following contents: S211 determines the number of operation overlaps between the target business process of the business system and the target business process of other business systems based on the operation overlap data between the target business processes in the business system. When the number of operation overlaps between the target business process of the business system and the target business processes of other business systems is less than the preset overlap number threshold, the process proceeds to step S212. When there is a target business process in the business system whose number of operation overlaps is not less than the preset overlap number threshold, the process proceeds to step S213. S212: when the number of target business processes of the business system is within the preset target process number range, it is determined that the other business system does not belong to the matching business system; when the number of target business processes of the business system is not within the preset target process number range, the process proceeds to step S213; S213 When the number of target business processes whose running overlap times is not less than the preset overlap times threshold is greater than the process quantity setting value, it is determined that the other business systems belong to the matching business systems. When the number of target business processes whose running overlap times is not less than the preset overlap times threshold is not greater than the process quantity setting value, proceed to step S22.

[0043] Optionally, the above step S22 includes the following contents: S221 determines the system overlap coefficient between the target business process of the business system and the target business processes of other business systems according to the number of operation overlaps between the target business process of the business system and the target business processes of other business systems and the operation overlap durations of different operation overlaps. When there is a target business process whose system overlap coefficient is greater than a preset overlap coefficient, the process proceeds to step S223. When there is no target business process whose system overlap coefficient is greater than the preset overlap coefficient, the process proceeds to step S222. S222: When the number of target business processes is within the preset target process number range, it is determined that the other business processes do not belong to the matching business system; when the number of target business processes is not within the preset target process number range, the process proceeds to step S23; S223: The target business process whose system overlap coefficient is greater than the preset overlap coefficient is regarded as the overlap business process. When the number of overlap business processes is greater than the preset overlap process number, it is determined that the other business processes belong to the matching business system. When the number of overlap business processes is not greater than the preset overlap process number, the process proceeds to step S224. S224 determines the screening system overlap coefficient with the system overlap coefficients of different overlapping business processes. When the screening system overlap coefficient is greater than the preset system overlap coefficient threshold, it is determined that the other business processes belong to the matching business system. When the screening system overlap coefficient is not greater than the preset system overlap coefficient threshold, step S23 is entered.

[0044] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, equipment, and non-volatile computer storage medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0045] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0046] The above description is only one or more embodiments of this specification and is not intended to limit this specification. For those skilled in the art, one or more embodiments of this specification may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of one or more embodiments of this specification shall be included in the scope of the claims of this specification.

Claims

1. A test and analysis method for localization transformation in a trust innovation scenario, characterized in that: Specifically include: Determine the historical call data corresponding to the business processes of different business systems, use the historical call data to determine the running overlap data with other business processes, and determine the business processes that need to be built with test cases based on the running overlap data; The business process for which the test case construction is required is taken as the target business process, the constituent data of the target business process in different business systems is obtained, and when it is determined that the business system does not belong to the target business system by combining the historical call data of different business systems, the next step is entered; Based on the operation overlap data between the target business processes in the different business systems, the operation overlap coefficients between the different business systems are determined, and the matching business system of the business system is determined based on the operation overlap coefficients; Obtain the operation overlap data between different target business processes, and build test models for different target business processes in combination with the target business system and the target business process corresponding to the matching business system, and use the test model to perform test analysis on the information system.

2. The test and analysis method for localization transformation in the information innovation scenario as described in claim 1 is characterized in that: The historical call data corresponding to the business process includes the historical call times of the business process and the call time periods corresponding to different historical call times.

3. The test and analysis method for localization transformation in the information innovation scenario as described in claim 1 is characterized in that: The operation overlap data includes the number of operation overlaps with other business processes and the operation overlap durations of different operation overlap times.

4. The test and analysis method for localization transformation in the information innovation scenario as described in claim 3 is characterized in that: The method for determining the business process that needs to be built with test cases is: Obtaining operation overlap data between the business process and other business processes, and determining the number of operation overlaps between the business process and other business processes; Determine the overlapping business processes in other business processes based on the number of overlapping operations with other business processes; The number of overlapping business processes is used to determine whether the business process is a business process that requires test case construction.

5. The test and analysis method for localization transformation in the information innovation scenario as described in claim 4 is characterized in that: When the number of the overlapping business processes is greater than the preset number of processes, the business process is determined to be a business process that requires test case construction.

6. The test and analysis method for localization transformation in the information innovation scenario as described in claim 1 is characterized in that: The target business process component data includes the component quantity of the target business process in the business process.

7. The test and analysis method for localization transformation in the information innovation scenario as described in claim 1 is characterized in that: Determining that the business system does not belong to the target business system includes: Determining the number of target business processes in the business system based on the constituent data of the target business process in the business system; Determine the historical call times of the business system based on the historical call data in the business system; It is determined whether the business system belongs to the target business system according to the historical call times and the number of target business processes.

8. The test and analysis method for localization transformation in the information innovation scenario as described in claim 7 is characterized in that: When the number of historical calls of the business system is greater than a preset number threshold and the number of target business processes is greater than a preset process number threshold, it is determined that the business system belongs to the target business system.

9. The test and analysis method for localization transformation in the information innovation scenario as described in claim 1 is characterized in that: The method for constructing the test model of the target business process is: Determine the operation overlap duration between the target business process and other target business processes using the operation overlap data between different target business processes; Based on the overlapping duration of the operation, the overlapping business processes in other target business processes are determined, and the test model of the target business process is determined based on the overlapping business process, the target business process of the target business system, and the target business process of the matching business system corresponding to the target business process, and combined with the target business process.

Images