Combination test method and device, storage medium and electronic equipment

Abstract

The invention discloses a combined test method and device, a storage medium and electronic equipment. The method is applied to a satellite internet system, and specifically comprises the following steps: firstly, acquiring at least two configuration parameters, a combined constraint condition and a target number for indicating parameter dimensions in the satellite internet system, and further generating a combined test case based on the configuration parameters, the combined constraint condition and the target number; by analyzing the coverage rate of the combined test case and the full test case to optimize and update the combined test case, the test accuracy of the satellite internet system is effectively improved, so that the technical problem that the generation accuracy of the combined test case is relatively low is solved.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a combined testing method and apparatus, a storage medium, and an electronic device. Background Technology

[0002] Currently, when testing satellite internet systems, fixed algorithms are often used to generate test cases. However, existing algorithms struggle to ensure high-precision test case coverage when dealing with diverse parameter combinations and complex constraints. For example, for high-coverage testing requirements, a fixed number and pattern of generated test cases often lead to the omission of important test scenarios, affecting the comprehensiveness and effectiveness of the test. In other words, traditional test case generation methods fail to achieve ideal coverage, further limiting the accuracy and reliability of satellite internet system testing.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a combined testing method and apparatus, storage medium and electronic device to at least solve the technical problem of low accuracy in generating combined test cases.

[0005] According to one aspect of the embodiments of this application, a combined testing method is provided, applied to a satellite internet system, comprising: acquiring at least two configuration parameters, combined constraints, and a target quantity in the satellite internet system, wherein the configuration parameters include at least one parameter value, the combined constraints are used to indicate the constraint relationship between different configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases; performing a test case generation operation on the configuration parameters using the target quantity and the combined constraints to generate at least one combined test case; determining a coverage analysis result based on the coverage of the combined test cases relative to the full set of test cases, wherein the number of combined test cases is less than or equal to the number of full set of test cases, and the coverage analysis result is used to update the combined test cases.

[0006] According to another aspect of the embodiments of this application, a combined testing apparatus is also provided, applied to a satellite internet system, comprising: a first acquisition module, configured to acquire at least two configuration parameters, combined constraints, and a target quantity in the satellite internet system, wherein the configuration parameters include at least one parameter value, the combined constraints are used to indicate the constraint relationship between different configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases to be generated; a first generation module, configured to perform a test case generation operation on the configuration parameters using the target quantity and the combined constraints to generate at least one combined test case; and a determination module, configured to determine a coverage analysis result based on the coverage of the combined test cases relative to the full set of test cases, wherein the number of combined test cases is less than or equal to the number of the full set of test cases, and the coverage analysis result is used to update the combined test cases.

[0007] According to another aspect of the embodiments of this application, a combined testing method is also provided, applied to a satellite internet system, comprising: obtaining combined test cases and a target number, wherein the target number is used to indicate the parameter dimension of the combined test cases; performing test case analysis operations on the combined test cases based on the target number to generate at least two configuration parameters and a coverage analysis result, wherein the coverage analysis result is used to indicate the coverage degree of the combined test cases relative to the full set of test cases, the number of combined test cases is less than or equal to the number of the full set of test cases, the configuration parameters include at least one parameter value, and the coverage analysis result is used to update the combined test cases.

[0008] According to another aspect of the embodiments of this application, a combined testing apparatus is also provided, applied to a satellite internet system, comprising: a second acquisition module, configured to acquire combined test cases and a target number, wherein the target number is used to indicate the parameter dimension of the combined test cases; and a second generation module, configured to perform test case analysis operations on the combined test cases based on the target number, generating at least two configuration parameters and a coverage analysis result, wherein the coverage analysis result is used to indicate the coverage degree of the combined test cases relative to the full set of test cases, the number of combined test cases is less than or equal to the number of full set of test cases, and the coverage analysis result is used to update the combined test cases.

[0009] In one exemplary embodiment, a combined testing system is also provided, applied to a satellite internet scenario, comprising: a data management unit, configured to determine at least two configuration parameters, combined constraints, and a target quantity, wherein each of the configuration parameters includes at least one parameter value, the combined constraints are used to indicate the constraint relationship between the configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases to be generated; a parsing unit, configured to parse the combined test cases to obtain at least two configuration parameters and the constraint relationship between the configuration parameters; a combined design unit, configured to perform test case analysis operations on the combined test cases based on the target quantity, generating at least one of the combined test cases and a coverage analysis result, wherein the coverage analysis result is used to indicate the coverage degree of the combined test cases relative to the full set of test cases, the number of combined test cases is less than or equal to the number of the full set of test cases, and the coverage analysis result is used to update the combined test cases; a combined analysis unit, configured to perform test case analysis operations on the combined test cases based on the target quantity, determining at least two configuration parameters and the coverage analysis result; and an output unit, configured to output at least one of the at least two configuration parameters, the combined test cases, and the coverage analysis result.

[0010] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer program, and the computer program is configured to execute the above-described combined test method at runtime.

[0011] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the combined test method described above.

[0012] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the above-described combined test method through the computer program.

[0013] In this embodiment, at least two configuration parameters, combined constraints, and target quantities indicating parameter dimensions in the satellite internet system are first obtained. Then, combined test cases are generated based on the configuration parameters, constraints, and target quantities. The coverage of the combined test cases and the full set of test cases is analyzed to optimize and update the combined test cases. Through parameter combination and effective coverage analysis, the accuracy and efficiency of test case generation are improved, thereby achieving the technical effect of efficient, comprehensive, and targeted testing of the satellite internet system. This solves the technical problem of low accuracy in generating combined test cases. Attached Figure Description

[0014] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments of this application and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0015] Figure 1 This is a schematic diagram of an application environment for an optional combined testing method according to an embodiment of this application;

[0016] Figure 2 This is a flowchart illustrating an optional combined testing method according to an embodiment of this application;

[0017] Figure 3 This is a schematic diagram of an optional combined testing method according to an embodiment of this application;

[0018] Figure 4 This is a schematic diagram of an optional combined test case generation process according to an embodiment of this application;

[0019] Figure 5 This is a schematic diagram of another optional combined testing method according to an embodiment of this application;

[0020] Figure 6 This is a flowchart of an optional interactive combined testing method according to an embodiment of this application;

[0021] Figure 7 This is a flowchart illustrating an optional combination of constraints edited according to an embodiment of this application;

[0022] Figure 8 This is a schematic diagram of the system structure of an optional combined testing system according to an embodiment of this application;

[0023] Figure 9 This is a schematic diagram of the project management interface of an optional combined testing method according to an embodiment of this application;

[0024] Figure 10This is a schematic diagram of a combined data management interface for an optional combined testing method according to an embodiment of this application;

[0025] Figure 11 This is a schematic diagram of the script import interface for an optional combined testing method according to an embodiment of this application;

[0026] Figure 12 This is a schematic diagram of a combined data set editing interface for an optional combined test method according to an embodiment of this application;

[0027] Figure 13 This is a schematic diagram of a combined test case editing interface for an optional combined test method according to an embodiment of this application;

[0028] Figure 14 This is a schematic diagram of the combined constraint editing interface of an optional combined test method according to an embodiment of this application;

[0029] Figure 15 This is a schematic diagram of the combined design interface of an optional combined testing method according to an embodiment of this application;

[0030] Figure 16 This is a schematic diagram of a combination analysis interface for an optional combination test method according to an embodiment of this application;

[0031] Figure 17 This is a schematic diagram of the output interface of an optional combined testing method according to an embodiment of this application;

[0032] Figure 18 This is a schematic diagram of an optional combined testing device according to an embodiment of this application;

[0033] Figure 19 This is a schematic diagram of another optional combined testing device according to an embodiment of this application;

[0034] Figure 20 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

[0035] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0036] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0037] The present application will be described below with reference to embodiments:

[0038] According to one aspect of the embodiments of this application, a combined testing method is provided.

[0039] Optionally, in this embodiment, the above-described combined testing method can be applied to various software and system integration testing fields, and to testing scenarios involving multiple parameter configurations, multiple steps of operation, and multiple system interactions. Specifically, it can be applied to scenarios such as... Figure 1 The above-described combined test method is applied in the hardware environment consisting of server 101 and terminal device 103 shown.

[0040] Furthermore, combined Figure 1 As shown, the above-mentioned combined testing method can be implemented by the terminal device 103 or the server 101 respectively, or by the terminal device 103 and the server 101 together. This application embodiment does not limit this.

[0041] For example, in any test scenario, server 101 is responsible for receiving test requirements, configuration parameters, combined constraints, and other information transmitted from terminal device 103, executing the logic for generating and updating combined test cases, and performing coverage analysis. Terminal device 103 serves as the user interface, providing test personnel with access to input detailed information about test items, real-time monitoring of the combined test progress, and viewing and downloading test results. This can include, but is not limited to, desktop computers, laptops, tablets, or any other device with sufficient computing power and network connectivity. Through interaction with server 101, test personnel can easily control the test process, obtain timely feedback, thereby optimizing test strategies and improving the accuracy and efficiency of test case generation.

[0042] It should be noted that the test environment consisting of servers and terminal equipment described above is not only applicable to satellite internet systems, but also widely applicable to other scenarios involving a large number of parameter configurations and complex constraints, such as network communication systems and automated control systems.

[0043] It should also be noted that the aforementioned server 101 is connected to the terminal device 103 via a network and can be used to provide services to the terminal device or the application 107 installed on the terminal device to implement the aforementioned combined testing method. A database 105 can also be set up on or independently of server 101 to provide data storage services for implementing the aforementioned combined testing method. Specifically:

[0044] The aforementioned server 101 and terminal device 103 can be any node in a distributed system, such as a blockchain system. This blockchain system can be formed by connecting multiple nodes through network communication. The nodes can form any type of network, and any type of computing device, such as any electronic device, can become a node in this distributed system by joining the network formed between the nodes.

[0045] The aforementioned server 101 can be a single server, a server cluster consisting of multiple servers, or a cloud server.

[0046] The aforementioned networks may include, but are not limited to, wired networks and wireless networks. The wired networks include local area networks (LANs), metropolitan area networks (MANs), and wide area networks (WANs). The wireless networks include Bluetooth, Wi-Fi, and other networks that enable wireless communication.

[0047] The aforementioned terminal device 103 may be a terminal configured with an application, and may include, but is not limited to, at least one of the following: laptop computer, tablet computer, handheld computer, MID (Mobile Internet Devices), PAD, desktop computer, intelligent voice interaction device, smart home appliance, vehicle terminal, aircraft, virtual reality (VR) terminal, augmented reality (AR) terminal, mixed reality (MR) terminal, and other computer devices.

[0048] Specifically, in the testing environment of a satellite internet system, the aforementioned combined testing methods may be executed by a central test server, responsible for core tasks such as test case generation, updating, and coverage analysis. When testing begins, test engineers input the project details, configuration parameter set, combined constraints between parameters, and desired coverage intensity (i.e., the aforementioned target quantity) through an intuitive user interface on a terminal device (such as a laptop). This information is then transmitted to the central test server. Upon receiving the information, the server uses algorithms to parse the configuration parameters and combined constraints, generates combined test cases based on the specified coverage intensity, and analyzes and provides feedback on the test case coverage in real time.

[0049] Understandably, during the testing process, the server can dynamically adjust test cases based on the coverage analysis results, ensuring that even with numerous parameter configurations and complex constraints, it can efficiently cover most test scenarios, thereby significantly improving the accuracy of test case generation and the efficiency of the entire testing process.

[0050] For example, with Figure 2 For example, the above combined testing method is used in the test environment of a satellite internet system, including but not limited to the following steps:

[0051] S1, define test items on the terminal device, including parameter configuration, constraints and target coverage intensity (i.e. the number of targets mentioned above).

[0052] S2, the terminal device sends the test item information defined in S1 to the server, and the server generates combined test cases and coverage analysis results based on this information. The server further updates the combined test cases based on the coverage analysis results until the coverage analysis results meet the requirements and obtains the determined combined test cases. For example, the coverage of the generated combined test cases relative to the full number of test cases is greater than or equal to the preset coverage threshold.

[0053] S3: The server sends the combined test cases generated by the server in S2 to the satellite via a satellite link or terrestrial network for actual testing, and provides real-time or periodic feedback on the test progress to the server or at least one of the terminal devices, which can be viewed by testers on at least one of the display interfaces of the server or terminal device.

[0054] S4. After the satellite performs the test, it sends the test results back to at least one of the servers or terminal devices, allowing testers to view the test results on at least one of the display interfaces on the server or terminal device.

[0055] It should be noted that the test results obtained can be used to further adjust the test strategy and update the combined test cases.

[0056] Alternatively, as an alternative implementation method, such as Figure 3 As shown, the above combined test method includes:

[0057] S302, Obtain at least two configuration parameters, combined constraints, and target quantity in the satellite internet system, wherein the configuration parameters include at least one parameter value, the combined constraints are used to indicate the constraint relationship between different configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test case;

[0058] Optionally, in this embodiment, acquiring at least two configuration parameters, combined constraints, and target quantity in the satellite internet system refers to collecting set values ​​of internal or external factors of the system, such as relay stations, satellite links, and ground network facilities, including but not limited to satellite model, orbital altitude, frequency configuration, coding protocol, and power control parameters. The values ​​of these configuration parameters can cover all reasonable operating states and parameter ranges to ensure the comprehensiveness and systematic nature of the test.

[0059] Optionally, in this embodiment, combined constraints refer to the interactions or restrictions between different configuration parameters during the operation of a satellite internet system, including but not limited to signal synchronization rules between satellites and ground equipment, priority arrangements during multi-band sharing, and adaptability requirements between data transmission rates and coding protocols. Combined constraints reflect the logical dependencies or conflicts in parameter configurations during the actual operation of the satellite internet system.

[0060] Optionally, in the embodiments of this application, the target number refers to the parameter dimension of the combined test cases, which can be understood as "t" in the t-way combined testing strategy. It can be any positive integer value, determined according to the depth and breadth of the test, such as 2-way, 3-way, or even higher t-way, to meet the testing needs of different levels of system behavior details.

[0061] It's important to note that t-way combinatorial testing is a method used in software or system testing. It refers to designing test cases that consider coverage of any number of t parameter combinations. For example, a 2-way strategy means test cases will cover all combinations of parameter pairs, while a 3-way strategy considers coverage of all ternary combinations of parameters, and so on. T-way combinatorial testing effectively detects system defects caused by interactions between parameters. In scenarios with a large number of parameters and complex interactions, it significantly improves the comprehensiveness and efficiency of testing, while avoiding the problem of explosive growth in the number of test cases that occurs in traditional exhaustive testing methods.

[0062] Furthermore, in this embodiment, the selection and application of the target number are flexibly determined based on the actual situation of the test objectives and resources. It is not limited to conventional 2-way or 3-way methods, but can be extended to higher combination dimensions, such as 4-way, 5-way, and even more complex combinations, to meet specific requirements for test depth and breadth. By flexibly adjusting the t-way strategy, this embodiment can optimize the number of test cases while ensuring test coverage quality.

[0063] It should be noted that the specific details of the configuration parameters, combined constraints, and target quantity in the satellite internet system will vary depending on the test objective, system architecture, and application scenario.

[0064] For example, when testing satellite communication protocols, configuration parameters need to consider factors such as channel conditions and signal delay; while when testing network management software, configuration parameters need to consider factors such as flow control and network topology.

[0065] Furthermore, the selection of the aforementioned target number will also affect the number and coverage of test cases. Choosing a larger target number indicates a finer test granularity and more comprehensive coverage, which is not limited in this application.

[0066] Furthermore, after obtaining the target quantity, combined constraints, and at least two configuration parameters, it is possible to continue executing S204 to generate combined test cases, including but not limited to:

[0067] S304, Perform test case generation operation on the configuration parameters based on the target quantity and combined constraints to generate at least one combined test case;

[0068] Optionally, in this embodiment of the application, the above-mentioned test case generation operation covers multiple steps such as algorithm selection, parameter value combination, and constraint condition checking, to ensure that the generated test cases can effectively test the behavior of the satellite Internet system under various configurations, including but not limited to fault detection, performance evaluation, compatibility testing, etc.

[0069] Optionally, in the embodiments of this application, the above-mentioned combined test cases can be understood as test cases generated according to a specific t-way strategy.

[0070] It should be noted that the specific methods for generating test cases can be diverse, such as using greedy algorithms, genetic algorithms, or probability-based combination strategies. Furthermore, the number and coverage of generated test cases will vary depending on the size of the target number (t-way). The embodiments of this application can dynamically adjust parameter dimensions and algorithm selection according to actual conditions to balance the comprehensiveness and efficiency of testing, and are applicable to satellite internet systems in multi-parameter environments, but are not limited to this scenario. They are also applicable to testing needs for other multi-element combinations such as network communication and automated control. This application does not impose any limitations on this.

[0071] Furthermore, after obtaining the above combined test cases, it is possible to continue executing S206 to determine the coverage analysis results, specifically:

[0072] S306, determine the coverage analysis result based on the coverage of the combined test cases relative to the full set of test cases, wherein the number of combined test cases is less than or equal to the number of full set of test cases, and the coverage analysis result is used to update the combined test cases.

[0073] Optionally, in this embodiment, the full set of test cases is a complete exhaustive combination based on all parameter values. The coverage analysis results can reflect the coverage breadth of the combined test cases, i.e., the combined coverage of at least t parameters, and may also include coverage analysis of other dimensions, such as the independent coverage of parameters, coverage under specific constraints, etc.

[0074] It should be noted that the selection and generation of combined test cases in the embodiments of this application are not static, but can be dynamically adjusted according to the coverage analysis results.

[0075] For example, if the initial coverage analysis indicates that certain parameter combinations are missing, the system can automatically generate additional test cases to fill these gaps, or optimize the test case generation algorithm in subsequent test iterations to improve the coverage of specific parameter combinations.

[0076] Furthermore, the calculation method for coverage and the presentation format of the analysis results can be customized according to specific needs, such as providing the percentage of coverage, a list of uncovered parameter combinations, and correlation analysis between parameters, to support more refined test management and decision-making. This application does not impose any limitations on this.

[0077] For example, in satellite internet system testing, efficient and targeted combined test case generation and analysis can be achieved by defining at least two configuration parameters, combined constraints, and a target number. Configuration parameters cover the values ​​of various variable elements in the system, such as satellite communication frequency, antenna angle, and coding mode; combined constraints clarify the interrelationships and dependencies between these parameters, ensuring that the generated test cases conform to the logic of actual system operation; the target number indicates the parameter dimension (t-way) of the combined testing strategy, determining the depth and breadth of test case coverage. Furthermore, by efficiently generating test cases covering specific parameter combinations while ensuring that the total number of these test cases does not exceed the range of the full number of test cases, and by guiding the dynamic optimization and updating of test cases through coverage analysis results, the goal of reducing testing workload while ensuring test quality is achieved.

[0078] In one exemplary embodiment, a combined test of satellite network management software is used as an example:

[0079] S1 identifies and records key configuration parameters in the satellite network management software, such as communication protocol version, data packet size, and network latency threshold. Each parameter defines its possible value range, meaning that each parameter can have more than one value.

[0080] S2 specifies the constraints on the combination of these configuration parameters. For example, when the communication protocol version is V1, the data packet size cannot exceed 1KB.

[0081] S3. Determine the target number, which is the combined coverage strategy adopted in this test. Assuming that a 2-way strategy is selected, it means that the test cases will cover all binary combinations of configuration parameters.

[0082] S4. Using the above information, the system begins to execute the test case generation operation, generating combined test cases that satisfy the constraints and fully cover the parameter combinations.

[0083] S5 analyzes the generated combined test cases, compares them with all theoretically possible combinations of binary parameters, and calculates the actual coverage rate, i.e., what proportion of combined scenarios the current test case set covers.

[0084] S6. If the coverage analysis results show that some parameter combinations are not covered, or the coverage is lower than expected, additional combined test cases will be automatically generated based on the analysis results, or the current test case generation strategy will be optimized to make up for the coverage gaps, and finally form a set of test cases that have been iteratively optimized to ensure the comprehensiveness and efficiency of testing.

[0085] Specifically, assume the following configuration parameters are identified and recorded: communication protocol version (possible values ​​include V1, V2, V3), packet size (possible values ​​include 512 bytes, 1KB, 2KB), and network latency threshold (possible values ​​include 50ms, 100ms, 200ms). Next, the system defines the combined constraints between these configuration parameters. For example, constraint 1: when the communication protocol version is V1, the packet size cannot exceed 1KB; constraint 2: when the communication protocol version is V2, the network latency threshold cannot be 50ms.

[0086] Then, the target number of tests is determined to be a 2-way strategy, that is, the test cases will cover all binary combinations of configuration parameters, that is, consider the mutual influence between any two configuration parameters among communication protocol version, packet size and network latency threshold; further, an initial set of combined test cases is generated based on the 2-way strategy and combined constraints. For example, test case 1 includes the combination of communication protocol version V2 and packet size 1KB, to ensure that the generated test cases satisfy the constraints and cover the parameter combinations.

[0087] Further analysis of the initial combined test cases compares them with all theoretically possible combinations of binary parameters (the full set of test cases mentioned above) to calculate the actual coverage. Assuming there are theoretically 100 different combinations of binary parameters, and the initial combined test cases cover 80 of them, the actual coverage is 80%. Since this coverage is lower than the expected 90%, additional combined test cases will be automatically generated based on the analysis results. For example, after comparing all theoretically possible combinations of binary parameters with those covered by the initial combined test cases, it is determined that the current initial combined test cases do not include the combination test of communication protocol version V1 and network latency threshold of 200ms. Therefore, a combined test case of communication protocol version V1 and network latency threshold of 200ms can be added. In other words, updating combined test cases based on coverage analysis results can be understood as an iterative optimization mechanism. It aims to analyze the coverage of parameter combinations by the current set of test cases, identify uncovered or insufficiently covered parameter combinations, and automatically generate or adjust test cases to achieve higher test coverage.

[0088] This application's embodiments first obtain at least two configuration parameters, combined constraints, and a target quantity used to indicate parameter dimensions in a satellite internet system. Then, combined test cases are generated based on the configuration parameters, constraints, and target quantity. By analyzing the coverage of the combined test cases and the full set of test cases, the combined test cases are optimized and updated. Through parameter combination and effective coverage analysis, the accuracy and efficiency of test case generation are improved, thereby achieving the technical effect of efficient, comprehensive, and targeted testing of the satellite internet system. This solves the technical problem of low accuracy in generating combined test cases.

[0089] Furthermore, in step S304 above, the above combined test cases may be generated through steps including but not limited to the following:

[0090] As an optional approach, the above-mentioned test case generation operation, based on the target quantity and the combined constraints, performs a test case generation operation on at least two of the configuration parameters to generate at least one combined test case. This includes: parsing the combined constraints to obtain the constraint relationships between the configuration parameters, and parsing the at least two configuration parameters to obtain the values ​​corresponding to each configuration parameter; determining at least one parameter combination from the combined data set based on the target quantity, wherein one parameter combination includes the target quantity of configuration parameters; updating the parameter values ​​of the configuration parameters in the parameter combination based on the constraint relationships; and performing a test case generation operation on the parameter combination to generate the combined test case.

[0091] It should be noted that the values ​​of configuration parameters, the specific forms of combined constraints, and the selection of the number of targets can be flexibly defined according to different testing needs and scenarios. For example, in software functional testing, network configuration optimization, or algorithm verification, the parameter dimensions and constraint relationships can be dynamically adjusted according to the actual complexity and resource limitations. This application does not impose any restrictions on this.

[0092] For example, specific constraint relationships between configuration parameters are obtained by parsing the combined constraint conditions, and the possible values ​​of each parameter are obtained by parsing the configuration parameters. Then, based on the defined target quantity, parameter combinations that meet the coverage requirements are determined from the combined data set. Based on the parsed constraint relationships, the configuration parameter values ​​in the parameter combinations are dynamically updated to ensure that the generated test case set satisfies both the combined coverage strategy and the actual parameter constraints. Finally, test case generation is performed on the updated parameter combinations to generate combined test cases.

[0093] In one exemplary embodiment, such as Figure 4 As shown, the combined test of satellite orbit control software is taken as an example:

[0094] S401 identifies and records the configuration parameters of the satellite orbit control software, such as satellite attitude adjustment speed (values ​​include slow, standard, and fast), satellite orbit correction mode (values ​​include manual correction, semi-automatic correction, and fully automatic correction), and satellite energy status (values ​​include sufficient, warning, and emergency).

[0095] S402 specifies the combined constraints between configuration parameters. For example, when the satellite attitude adjustment speed is set to fast, the satellite orbit correction mode cannot be manually corrected; when the satellite energy status is in emergency, the satellite attitude adjustment speed is set to slow.

[0096] S403, which specifies the target number as a 4-way strategy, means that test cases will cover all quaternary combinations of configuration parameters.

[0097] S404, by analyzing the combined constraints, we obtain the constraint relationship between the satellite attitude adjustment speed and the satellite orbit correction mode and the satellite energy state;

[0098] S405, parse the configuration parameters to obtain the value of each parameter;

[0099] It should be noted that S404 and S405 can be executed synchronously or asynchronously, and this application does not limit the execution order of the two.

[0100] S406, based on the 4-way strategy, determines the quaternary parameter combination of satellite attitude adjustment speed and satellite orbit correction mode, and satellite attitude adjustment speed and satellite energy status from the combined data set.

[0101] S407, update the configuration parameter values ​​in the parameter combination based on the constraint relationship. For example, for the combination of satellite attitude adjustment speed and satellite orbit correction mode, if the attitude adjustment speed is set to fast, the orbit correction mode will automatically exclude the manual correction option to ensure that the generated test cases meet the constraint conditions.

[0102] S408 performs a test case generation operation on the updated parameter combination to generate combined test cases.

[0103] Through the embodiments of this application, a dynamic parsing and updating mechanism is adopted to generate test cases by combining the target number and combined constraints, thereby achieving the technical effect of reducing the number of test cases and improving testing efficiency while ensuring test coverage.

[0104] Furthermore, in step S304 above, the above combined test cases may be generated using, but is not limited to, the following test case generation algorithm:

[0105] As an optional approach, the above-mentioned test case generation operation on the above-mentioned parameter combination to generate the above-mentioned combined test cases includes at least one of the following: using a heuristic algorithm to perform the above-mentioned test case generation operation on the above-mentioned parameter combination to generate the above-mentioned combined test cases; using a greedy algorithm to perform the above-mentioned test case generation operation on the above-mentioned parameter combination to generate the above-mentioned combined test cases.

[0106] Optionally, in the embodiments of this application, the test case generation operation refers to the process of constructing test cases to cover a specified combination of parameters through a specific algorithm, including but not limited to using heuristic algorithms or greedy algorithms.

[0107] It should be noted that the selection of the above algorithms can be flexibly adjusted according to factors such as testing requirements, parameter characteristics, and resource constraints. For example, when resources are limited, greedy algorithms are preferred, while heuristic algorithms are preferred when pursuing more comprehensive coverage. This application does not impose any restrictions on this.

[0108] It should also be noted that interactive options for test case generation algorithms can be provided. During actual testing, a variety of different test case generation algorithms (including but not limited to heuristic algorithms and greedy algorithms) can be provided for testers to choose independently. The tester can select the test case generation algorithm when obtaining configuration parameters, combined constraints, and target quantity.

[0109] For example, embodiments of this application provide a technical solution for generating combined test cases using heuristic algorithms and greedy algorithms. Heuristic algorithms construct test cases through intelligent decision-making and experience guidance, which can effectively cover parameter combinations and easily find optimized solutions. Greedy algorithms, on the other hand, are a local optimum strategy that constructs test cases by selecting the optimal or most advantageous values ​​in parameter combinations one by one, ensuring the highest possible coverage under limited resource conditions. Both can be selected according to the characteristics and needs of the test scenario.

[0110] In one exemplary embodiment, software integration testing of satellite communication equipment is taken as an example:

[0111] S1, determine the combination of parameters to be tested from the combined data set, such as the combination of parameters such as satellite communication protocol, signal frequency, and transmission rate.

[0112] S2-1, Select to use a heuristic algorithm to perform the test case generation operation. This algorithm can intelligently consider the dependencies between historical data, test objectives and parameters to generate comprehensive and effective combined test cases.

[0113] S2-2, Choose to use a greedy algorithm to perform the test case generation operation. This algorithm selects the optimal value from the parameter combinations one by one to minimize the number of test cases while generating combined test cases with maximum coverage.

[0114] S4. After the algorithm runs, the generated test case set will be further analyzed and optimized to ensure that all key binary parameter combinations are effectively covered.

[0115] S5: For parameter combinations that do not achieve the expected coverage, the algorithm automatically adjusts and generates supplementary test cases until the preset coverage standard is reached.

[0116] It should be noted that steps S2-1 and S2-2 can be performed individually or simultaneously, and the combined test cases generated by S2-1 and S2-2 can be combined to obtain the required combined test cases. This application does not impose any restrictions on this. That is, for a test scenario or a test project, at least one test case generation algorithm can be used.

[0117] Through the embodiments of this application, a dynamically adaptive test case generation algorithm is adopted to achieve the technical effect of efficiently and accurately generating combined test cases covering any combination of parameters in the software testing of satellite communication equipment, thereby improving testing efficiency while reducing costs.

[0118] Furthermore, in step S302 above, the above combined constraint conditions may be obtained by means of steps including but not limited to the following:

[0119] As an optional approach, obtaining at least two configuration parameters, combined constraints, and target quantity in the satellite internet system includes: obtaining initial constraints, wherein the initial constraints are used to indicate the constraint relationship between at least two of the configuration parameters, and the constraint relationship is a mutual exclusion relationship or a dependency relationship; and updating the initial constraints in response to a condition update operation to obtain the combined constraints.

[0120] Optionally, in the embodiments of this application, the initial constraint condition refers to the rule that defines the mutual exclusion or dependency relationship between configuration parameters, including but not limited to the rule that parameter B cannot take the value y when parameter A takes the value x, or that parameter D must take the value a when parameter C takes the value z.

[0121] It should be noted that the initial constraints can be derived from the basic definition of the relationship between parameters during the design phase of the satellite internet system. Subsequent condition update operations can be manually adjusted by the user according to actual testing needs, or the result of automatic optimization by the satellite internet system through learning historical test results. This application does not limit this.

[0122] For example, the satellite internet system starts from the initial constraints and dynamically adjusts the constraint relationships between parameters according to the user's update operations to ensure that the generated test cases not only cover the necessary parameter combinations, but also follow the latest constraint relationships between the configuration parameters.

[0123] In one exemplary embodiment, the application scenario of satellite internet system software upgrade testing is taken as an example:

[0124] S1. Obtain initial constraints, which may be derived from the software specifications and indicate the basic constraint relationship between at least two configuration parameters. For example, when the network protocol type is IPv4, packets larger than 1500 bytes are not supported.

[0125] S2, in response to the condition update operation, updates the initial constraints mentioned above. For example, based on previous test results, it was found that in certain special scenarios, even if the network protocol type is IPv4, it can support the transmission of larger data packets. Therefore, the user or system automatically updates the constraints, relaxing the restrictions on data packet size.

[0126] S3, determine the target number, such as deciding to use a 5-way strategy for testing to cover all five combinations of configuration parameters.

[0127] S4 dynamically generates a set of test cases based on the updated combined constraints and target number, ensuring that the newly generated test cases not only cover the five-element combination of configuration parameters, but also follow the latest constraint relationships between configuration parameters.

[0128] Through the embodiments of this application, combined constraints can be dynamically updated, achieving the technical effect of generating combined test cases that meet coverage requirements and comply with the latest constraint relationships in satellite internet system testing, thereby improving the flexibility, accuracy and efficiency of testing.

[0129] Furthermore, the initial constraints described above can be obtained by means of, but not limited to, the following steps:

[0130] As an optional approach, obtaining the initial constraints as described above includes at least one of the following: obtaining the initial constraints from a constraint database, wherein the constraint database stores constraints related to the historical test types of the satellite internet system; or obtaining the initial constraints in response to a constraint generation operation.

[0131] Optionally, in this embodiment, the constraint database refers to a database that stores the constraint relationships of configuration parameters in historical test types, including but not limited to mutual exclusion relationships, dependency relationships, and other constraints. This data can be used to initialize the constraints of the current test, providing a test starting point based on historical information.

[0132] It should be noted that constraints can be obtained statically, by reading from a pre-established database, or dynamically, by creating them in real time through the user's constraint generation operation. The information in the constraint database can come from multiple test projects, including satellite internet systems of different versions or configurations; this application does not limit this.

[0133] For example, embodiments of this application include, but are not limited to, reading from historical test data or generating through user interaction, to ensure that the design of test cases can both draw on past testing experience and meet the specific needs of current testing.

[0134] In one exemplary embodiment, the application scenario of regression testing for satellite internet system software is taken as an example:

[0135] S1. Retrieve initial constraints from the constraint database. The database stores constraints related to the system's historical test types, such as the network protocol version must match the packet size to avoid transmission errors.

[0136] S2, in response to the constraint generation operation, allows users or the system to generate or adjust initial constraints based on new testing requirements or system changes. For example, a new network protocol version may require new constraints related to specific packet sizes or concurrent connection numbers.

[0137] S3, based on the acquired or updated initial constraints, initiates the test case generation process to ensure that the generated test cases reflect the latest system state and test requirements.

[0138] This application's embodiments employ a combination of reading from a constraint database and user-generated operations to obtain initial constraints. This achieves the technical effect of rapidly constructing test cases based on historical test data and flexibly adjusting them according to current specific test requirements in satellite internet system testing. This improves test preparation efficiency and ensures comprehensive and accurate test coverage.

[0139] Furthermore, the initial constraints described above can be updated using steps including, but not limited to, the following:

[0140] As an optional approach, the above-mentioned response to the condition update operation, updating the above-mentioned initial constraints to obtain the above-mentioned combined constraints, includes at least one of the following: adding a first constraint to the initial constraints to obtain the above-mentioned combined constraints; modifying a second constraint to the initial constraints to obtain the above-mentioned combined constraints; or deleting a third constraint from the initial constraints to obtain the above-mentioned combined constraints.

[0141] Optionally, in this embodiment, the condition update operation refers to the addition, deletion, or modification of the initial constraints based on current testing requirements or system changes, in order to obtain a combination of constraints that better reflects the actual situation. The first constraint, the second constraint, and the third constraint refer to the constraint instances added, modified, or deleted during the operation, respectively, and can be any type of parameter constraint, including but not limited to mutual exclusion, dependency, or compatibility constraints.

[0142] It should be noted that the updating of combined constraints can be done manually by the user through the interface, or it can be done automatically by the system based on the results of automated analysis. Alternatively, it can be a self-learning and optimization mechanism established during long-term testing to automatically adjust the initial constraints in order to cope with the changing needs of different testing scenarios. This application does not limit this.

[0143] For example, the embodiments of this application are not limited to simple addition, deletion, and modification. They can also use intelligent analysis to predict which constraints need to be added, which need to be adjusted, and which can be removed. This ensures test effectiveness while reducing unnecessary test cases and improving test efficiency and accuracy. For instance, machine learning algorithms can analyze past test data and fault records to identify which configuration parameter combinations have caused the most common problems or faults in the past. New constraints can then be automatically added to prevent these combinations from reappearing in future test cases, unless there is a specific need to verify their stability or security. Simultaneously, for configuration parameter combinations that have never caused problems and have performed stably in multiple iterations, it can be suggested to remove their associated constraints to reduce the number of test cases and avoid repeatedly testing already proven combinations. When adjusting constraints, intelligent analysis can also recommend optimal value ranges or parameter combinations to maximize test plan simplification and improve the overall efficiency and accuracy of the test process while ensuring test adequacy.

[0144] In one exemplary embodiment, the application scenario of satellite internet system software upgrade testing is taken as an example:

[0145] S1, Obtain the existing initial constraints, which may have been determined in previous test versions, such as network protocol version V1 not supporting the transmission of packets larger than 1KB.

[0146] S2, add a first constraint, for example, when the network protocol version is V2, the packet size cannot be less than 512 bytes, to reflect the minimum requirement for packet size in the new version.

[0147] S3. Modify the second constraint. For example, if the original network latency threshold was 100ms, the packet retransmission frequency could not exceed 10 times per second; but in this test, the threshold was relaxed to 200ms, and the upper limit of the packet retransmission frequency was adjusted to 20 times per second.

[0148] S4. Remove the third constraint. In earlier tests, it was stipulated that satellite communication functionality must be downgraded to the lowest level when the energy status was in a warning state. However, in this test, the energy management system was enhanced, and a higher level of communication functionality could be maintained even in a warning state. Therefore, this constraint was removed.

[0149] Through the embodiments of this application, the initial constraints are updated by adding, modifying, or deleting constraints. This enables flexible responses to scenarios such as system upgrades, functional changes, or test strategy adjustments in satellite internet system testing. By dynamically updating constraints, combined test cases that better meet current testing needs are generated, thereby improving the relevance of test cases, reducing testing costs, and enhancing testing efficiency.

[0150] Furthermore, in step S302 above, the above combined constraint conditions may be obtained by means of steps including but not limited to the following:

[0151] As an optional approach, obtaining at least two configuration parameters, combined constraints, and target quantity in the satellite internet system includes: determining a first value for a first configuration parameter and a second value for a second configuration parameter, wherein the first configuration parameter is any of the aforementioned configuration parameters, and the second configuration parameter is any of the aforementioned configuration parameters other than the first configuration parameter; determining a constraint identifier based on the current test type of the satellite internet system; and using the constraint identifier to associate the first configuration parameter and the second configuration parameter to obtain the combined constraints.

[0152] Optionally, in this embodiment, the first configuration parameter and the second configuration parameter refer to any two configuration parameters selected from the satellite internet system. These can be any adjustable settings within the system, including but not limited to network protocol version, packet size, and number of concurrent connections. The constraint identifier is used to indicate the constraint relationship between the first and second configuration parameters under a specific test type. It can vary depending on the test requirements, for example, identifying the compatibility requirements that must be met between the network protocol version and the packet size.

[0153] It should be noted that the determination of the constraint identifier can be based on the current testing type of the satellite internet system, such as functional testing, performance testing, or security testing. Each testing type may correspond to different constraint conditions. Furthermore, the selection of the first and second configuration parameters is not unique; they can be arbitrarily chosen from all configuration parameters, as long as they are not the same parameter. This application does not impose any restrictions on this.

[0154] For example, embodiments of this application include determining the values ​​of any two configuration parameters and using constraint identifiers corresponding to specific test types to associate these two parameters, thereby obtaining a set of combined constraint conditions. This ensures that the generation of test cases can follow the corresponding constraint relationships according to different test types, thereby improving the accuracy and effectiveness of testing.

[0155] In one exemplary embodiment, the application scenario of satellite internet system function upgrade testing is taken as an example:

[0156] S1, determine that the first configuration parameter is the network protocol version, and determine that its value is V1.

[0157] S2, determine the second configuration parameter as the data packet size, and determine its second value as 1KB.

[0158] S3, based on the system's current test type, namely functional upgrade testing, determines the constraint flag. Assume this flag means that under protocol version V1, the packet size cannot exceed 1KB.

[0159] S4. Use the constraint identifier to associate the first configuration parameter and the second configuration parameter to obtain the combined constraint condition: when the network protocol version is V1, the packet size cannot exceed 1KB.

[0160] Through the embodiments of this application, the values ​​of the first configuration parameter and the second configuration parameter are first determined, and the constraint identifier is determined in combination with the test type, thereby obtaining the combined constraint conditions. This enables the customization of constraint conditions in satellite internet system testing based on a specific test type and parameter combination, ensuring that test cases cover reasonable and necessary combined scenarios, and achieving the technical effect of improving test relevance and reducing invalid tests.

[0161] Furthermore, the constraint identifiers in the above combined constraint conditions may include, but are not limited to, the following:

[0162] As an optional approach, the above method further includes at least one of the following: associating the first configuration parameter and the second configuration parameter using a mutual exclusion constraint identifier to obtain the combined constraint condition, wherein the combined constraint condition indicates that when the parameter value of the first configuration parameter is the first value, the parameter value of the second configuration parameter is any parameter value other than the second value, and the constraint identifier includes the mutual exclusion constraint identifier; associating the first configuration parameter and the second configuration parameter using a dependency constraint identifier to obtain the combined constraint condition, wherein the combined constraint condition indicates that when the parameter value of the first configuration parameter is the first value, the parameter value of the second configuration parameter is the second value, and the constraint identifier includes the dependency constraint identifier.

[0163] Optionally, in the embodiments of this application, the mutual exclusion constraint identifier and the dependency constraint identifier refer to the markers used to identify the constraint relationship between configuration parameters. The mutual exclusion constraint identifier is used to indicate that the values ​​of two configuration parameters cannot appear at the same time, while the dependency constraint identifier is used to indicate that the value of one configuration parameter depends on a specific value of another configuration parameter.

[0164] For example, embodiments of this application can generate specific constraints based on mutual exclusion or dependency relationships, ensuring that test cases cover all reasonable parameter combinations while avoiding invalid or illegal test scenarios.

[0165] In one exemplary embodiment, taking the application scenario of satellite internet system functional testing as an example:

[0166] S1. Use a mutual exclusion constraint identifier to associate the first configuration parameter (network protocol version) and the second configuration parameter (packet size). For example, when the first configuration parameter is set to IPv6, the mutual exclusion constraint identifier indicates that the value of the second configuration parameter cannot be "more than 1.5KB", because under the IPv6 protocol, packets larger than 1.5KB may cause transmission errors or delays.

[0167] S2 uses a dependency constraint identifier to associate the first configuration parameter (network protocol version) with the second configuration parameter (packet size). For example, when the first configuration parameter is set to TCP, the dependency constraint identifier indicates that the second configuration parameter must be set to "1KB" because the optimal packet size under the TCP protocol is 1KB, and other sizes may affect transmission efficiency or stability.

[0168] It is understood that there is no specific order of execution between steps S1 and S2, and they can be executed synchronously or asynchronously. This application does not impose any restrictions on this.

[0169] This application's embodiments employ a method of associating configuration parameters using mutual exclusion and dependency constraint identifiers. This enables the generation of combined constraint conditions that better suit system characteristics and testing requirements based on the actual constraint relationships between parameters during satellite internet system testing, ensuring the rationality and effectiveness of test cases.

[0170] Furthermore, in step S302 above, the above configuration parameters may be obtained by means of, but not limited to, the following steps:

[0171] As an optional approach, the acquisition of at least two configuration parameters, combined constraints, and target quantity in the aforementioned satellite internet system includes: receiving a third configuration parameter and a fourth configuration parameter, wherein the third configuration parameter is determined based on a data import operation, and the fourth configuration parameter is pre-stored in a combined database; determining the configuration parameter based on the third configuration parameter and the fourth configuration parameter; and storing the configuration parameter in the combined database.

[0172] Optionally, in this embodiment, the third configuration parameter refers to the configuration parameter dynamically obtained through the data import operation, which can originate from test case scripts, configuration files, or data directly input by the user; while the fourth configuration parameter is the configuration parameter pre-stored in the combined database, which can be regarded as configuration items inherent to the system or commonly used in historical tests. The determination of the configuration parameters involves the analysis and integration of the imported data and the data stored in the database, ultimately forming the configuration parameters used for testing.

[0173] It should be noted that the process of obtaining configuration parameters is not limited to a single path. It can be a third configuration parameter obtained through a data import operation, a pre-stored fourth configuration parameter, or even a combination of both. Furthermore, the storage of configuration parameters can occur at any appropriate stage, and this application does not limit this.

[0174] For example, embodiments of this application provide a method for integrating data import and historical storage to determine the configuration parameters required for testing a satellite internet system. This includes, but is not limited to, receiving third configuration parameters imported from external data, combining them with existing fourth configuration parameters to form an updated parameter set, and storing it back in a combined database as the basis for generating subsequent test cases.

[0175] In one exemplary embodiment, the application scenario of network piping function testing for a satellite internet system is taken as an example:

[0176] S1 receives a third configuration parameter, which is obtained through a data import operation, for example, a new network latency threshold parameter is imported from a test script.

[0177] S2, the system reads the fourth configuration parameter from the combined database, such as packet size and number of concurrent connections, which have been identified as key configuration items in previous test cycles.

[0178] S3 compares the third configuration parameter with the fourth configuration parameter to determine if there is a conflict or if the existing set of configuration parameters needs to be updated.

[0179] S4. If the third configuration parameter does not conflict with the fourth configuration parameter, then merge them into the existing set of configuration parameters to form a complete and updated list of configuration parameters.

[0180] S5 stores the updated configuration parameter list in the composite database, providing accurate parameter information for subsequent test case generation and composite constraint setting.

[0181] The embodiments of this application employ a combination of data import and historical storage to determine configuration parameters. This enables flexible adaptation to changes in the testing environment and updated requirements during satellite internet system testing, ensuring that test cases are generated based on the most accurate and comprehensive configuration parameters. This, in turn, improves the reliability of test results and the completeness of system function verification.

[0182] Furthermore, during or after performing step S306 above, the coverage analysis results may be obtained using, but is not limited to, the following steps, and the combined test cases may be further updated:

[0183] As an optional approach, the method further includes: obtaining the full set of test cases, wherein the full set of test cases is determined by a full set of parameter combinations, the full set of parameter combinations includes any parameter combination, and one of the parameter combinations includes the target number of the configuration parameters; comparing the full set of test cases and the combined test cases to obtain the coverage analysis results; and updating the combined test cases based on the coverage analysis results.

[0184] Optionally, in the embodiments of this application, a full set of test cases refers to a set of test cases determined by a full set of parameter combinations of all configuration parameters. The full set of parameter combinations covers all possible combinations of parameter values, and the parameter combination refers to a set of configuration parameters selected according to test requirements. Any full set of test cases includes a target number of configuration parameters, that is, the number of configuration parameters included in each parameter combination is fixed at the target number.

[0185] Optionally, in this embodiment of the application, the full set of test cases can be obtained by iterating through all possible combinations of values ​​for all configuration parameters to ensure that every possible parameter configuration is taken into account.

[0186] It should be noted that there are various methods for obtaining a full set of test cases. These can be constructed by exhaustively listing all possible values ​​for configuration parameters, or generated based on historical test data or predictive models. Similarly, the comparison method between combined test cases and full set of test cases, as well as the calculation method for coverage analysis results, are not fixed and can be adjusted according to different testing strategies and metrics. This application does not impose any limitations on these methods.

[0187] For example, embodiments of this application include obtaining a full set of test cases, comparing combined test cases, analyzing coverage, and updating the combined test cases based on the analysis results to ensure that they cover key and necessary test scenarios.

[0188] In one exemplary embodiment, taking the application scenario of satellite internet system security testing as an example:

[0189] S1, obtain all test cases. These test cases cover all possible combinations of values ​​for all configuration parameters in the system, including but not limited to all combinations of parameters such as network protocol version, encryption algorithm, and communication frequency band.

[0190] S2 compares the full set of test cases with the current set of combined test cases, analyzes the coverage of the current set of combined test cases, and determines which parameter combinations have been covered and which have not.

[0191] S3, based on the coverage analysis results, identifies parameter combinations with low coverage. The system automatically or the user manually adjusts the test cases for these combinations. For example, it adds test cases that cover key parameter combinations to improve the overall test coverage.

[0192] S4, the updated set of combined test cases is compared and analyzed again until the preset coverage threshold is reached or specific test requirements are met.

[0193] Through the embodiments of this application, a full set of test cases is first obtained, and the coverage is compared and analyzed. Then, the combined test cases are updated based on the analysis results. This enables the quantitative evaluation of the coverage of test cases in satellite internet system testing, ensuring that the combined test case set covers all necessary test scenarios, thereby achieving the goal of optimizing test design and reducing test blind spots.

[0194] In yet another exemplary embodiment, this application also provides a combined testing method, such as... Figure 5 As shown, it is applied to satellite internet systems, including:

[0195] S502, obtain the combined test cases and the target number, where the target number is used to indicate the parameter dimension of the combined test cases;

[0196] S504, perform test case analysis on the combined test cases based on the target number, and generate at least two configuration parameters and coverage analysis results. The coverage analysis results are used to indicate the coverage of the combined test cases relative to the full number of test cases. The number of combined test cases is less than or equal to the number of full test cases. The configuration parameters include at least one parameter value. The coverage analysis results are used to update the combined test cases.

[0197] For example, in this embodiment of the application, the combined test cases and the target number are first obtained, and then the test cases are analyzed based on the target number to determine which combinations of configuration parameters have been covered, and the degree of coverage of the test case set over the full number of test cases. Finally, the combined test cases are optimized based on the analysis results to ensure the efficiency and sufficiency of the test.

[0198] In one exemplary embodiment, the application scenario of satellite internet system software functional testing is taken as an example:

[0199] S1, determine a set of combined test cases, which contains a selection of test cases based on a preset target number (e.g., 3-way) to cover specific combinations of configuration parameters in the system, such as combinations of network protocol version, encryption algorithm type, and data transmission rate.

[0200] S2 performs test case analysis on the combined test cases based on the target number (3-way), identifying which configuration parameter combinations have been covered, and the degree of coverage of the current combined test case set for all possible parameter combinations.

[0201] S3 analyzes the coverage analysis results and identifies configuration parameter combinations with low coverage. For example, certain network protocol versions and encryption algorithm types may not be fully covered.

[0202] S4. Based on the analysis results, update the combined test cases. For example, add additional test cases to cover those identified low-coverage combinations, or adjust the parameter values ​​of existing test cases to enhance the overall test coverage.

[0203] Through the embodiments of this application, the coverage of combined test cases is analyzed based on the target number, and the combined test cases are updated according to the analysis results. This enables dynamic adjustment of the selection of test cases in satellite internet system testing, ensuring coverage of as many parameter combinations as possible with limited test resources. This avoids resource waste and test blind spots in the testing process, and improves the accuracy and efficiency of testing.

[0204] In yet another exemplary embodiment, this application also provides a combined testing system applied to a satellite internet scenario, comprising:

[0205] The data management unit is used to determine at least two configuration parameters, combined constraints, and target quantity, wherein each of the above configuration parameters includes at least one parameter value, the combined constraints are used to indicate the constraint relationship between the above configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases to be generated.

[0206] The parsing unit is used to parse the above combined test cases to obtain at least two of the above configuration parameters and the above constraint relationships between the above configuration parameters;

[0207] The combined design unit is used to perform test case analysis operations on the combined test cases based on the target number, and generate at least one combined test case and coverage analysis result, wherein the coverage analysis result is used to indicate the coverage degree of the combined test cases relative to the full number of test cases, the number of combined test cases is less than or equal to the number of full test cases, and the coverage analysis result is used to update the combined test cases.

[0208] The combined analysis unit is used to perform test case analysis operations on the combined test cases based on the above target number, and determine at least two of the above configuration parameters and coverage analysis results.

[0209] The output unit is used to output at least one of the above two configuration parameters, the above combined test cases, and the above coverage analysis results.

[0210] Optionally, in this embodiment, the data management unit is responsible for determining the core elements in the testing process, including but not limited to at least two configuration parameters, combined constraints, and target quantity.

[0211] Optionally, in this embodiment of the application, the function of the parsing unit is to perform in-depth analysis of the combined test cases, extract the configuration parameters and their values, as well as the constraint relationships between the parameters, so as to provide accurate basic data for subsequent combination design and analysis.

[0212] Optionally, in this embodiment of the application, the combined design unit performs test case analysis operations based on the above-mentioned target number to generate combined test cases and coverage analysis results, which reflect the degree of coverage of the combined test cases over the full number of test cases.

[0213] Optionally, in this embodiment, the combined analysis unit also performs test case analysis operations based on the target number, evaluates and determines the generated combined test case set, and generates a result containing at least two configuration parameters and coverage analysis.

[0214] Optionally, in this embodiment, the output unit is used to provide necessary test data, including but not limited to configuration parameters, combined test cases, and coverage analysis results, to ensure that testing can be performed based on accurate test data.

[0215] For example, in a satellite internet scenario, the combined testing method implemented within the aforementioned combined testing system is as follows: Figure 6 As shown, this includes, but is not limited to, combined test design scenarios applied to satellite internet system operation testing, network piping testing, algorithm model testing, software function testing, and interface data testing. It is suitable for the design of combined test case sets for multi-system combinations, multi-element combinations, multi-step combinations, multi-branch combinations, and multi-value combinations.

[0216] Given that existing testing tools are only used to construct composite test case sets, independent of the composite test execution process, they lack the t-way composite coverage strength analysis required for interactive testing processes and cannot support execution rate and coverage analysis of test case execution results. Furthermore, test case sets using fixed 2-way composite testing strategies may miss 10% to 40% or even more potential defects. For critical or high-reliability testing scenarios such as satellite internet systems and satellite network systems, support for t-way composite testing strategies with variable coverage strength is required. Moreover, existing tools generate identical t-way test case sets each time, lacking flexibility during composite test execution, resulting in repetitive and fixed results; they also cannot perform group management and typical composite data management for t-way variable coverage composite test case sets.

[0217] Based on this, the combined testing method implemented through the above-mentioned combined testing system establishes a closed loop in the combined testing process, forming a mechanism for the continuous accumulation and reuse of typical combined data (the fourth configuration parameter mentioned above). By flexibly using t-way combined testing strategies, combined test case generation algorithms, and combined test case set analysis algorithms, it supports combined testing strategies with higher coverage intensity (more than 6-way), supports fixed or random combined test case generation algorithms, and also takes into account both scripted editing and interface editing, making the data editing process efficient and intuitive. While ensuring combined test coverage, it improves testing efficiency and reduces testing costs.

[0218] For example, such as Figure 6As shown, the process includes, but is not limited to: creating a combined test project and editing its basic information; selecting typical combined data (the fourth configuration parameter mentioned above); importing the combined data set (the third configuration parameter mentioned above) as a script file; editing the combined data set and combined constraints; parsing the formally described combined data and combined constraints; further selecting a combination strategy; constructing combined test cases using a combined test case generation algorithm; and outputting the constructed combined test case set and its combined coverage analysis results. The specific implementation steps are as follows:

[0219] S101-1, the basic information for creating a portfolio test project includes, but is not limited to: project creation time, project description, editors, whether it is public to other users, and whether the project belongs to the portfolio design type or portfolio analysis type.

[0220] S201-1, Selecting typical combined data may include, but is not limited to: the category to which the combined data belongs, the parameter name, and the variable values ​​that can be taken.

[0221] S301-1, the script for importing combined datasets may include, but is not limited to: text format ( (.txt), each line is a combination of data or a combination of constraints.

[0222] S401-1, Editing a combined data set may include, but is not limited to: adding, modifying, and deleting combined data. Each combined data item specifically includes a parameter name and its possible variable values.

[0223] It should be noted that when importing the combined data set in S301-1, a portion of the combined data can be imported in the form of a script, and then a portion of typical combined data can be obtained by selecting typical combined data in S201-1. The two portions of the combined data set form a new combined data set, and then the required combined data set can be constructed by editing the combined data set in S401-1. Furthermore, the edited combined data can be saved as typical combined data to realize the accumulation and reuse of combined data.

[0224] S401-2, Editing combined constraints may include, but is not limited to: adding, modifying and deleting constraints. Each combined constraint may specifically include, but is not limited to: the variable values ​​of two parameters that have a mutual exclusion or dependency relationship, and a formal symbol that identifies the relationship between the two.

[0225] It should be noted that in the edit combination constraint condition S401-2, each combination constraint condition is not limited to the constraint relationship between the variable values ​​of two parameters, but can also be the constraint relationship between the variable values ​​of multiple parameters.

[0226] S501-1, combined data parsing may include, but is not limited to: parsing out the parameter name of each combined data item and its possible variable values.

[0227] S501-2, the analysis of combined constraint conditions may include, but is not limited to: analyzing the values ​​of multiple parameter variables involved in each constraint condition and the constraint relationships between them.

[0228] S601-1, the selected combination strategy may include, but is not limited to, t-way combination strategies, such as 1-way, 2-way, 3-way, 4-way, 5-way, 6-way, 7-way combination strategies, etc.

[0229] S601-2, the combined test case generation algorithm may include, but is not limited to: different algorithms such as heuristic algorithms and greedy algorithms, and the combined test case set constructed may be fixed or random.

[0230] S801-1 to S801-2 are constructed by the combined test case generation algorithm based on the selected combination strategy, and the combined coverage analysis results are generated.

[0231] For example, when editing combined constraints, including but not limited to, Figure 7 As shown:

[0232] S702, add a pair of combined constraint relationships;

[0233] S703, select the first parameter from the configuration parameters;

[0234] S704, select the second parameter from the configuration parameters;

[0235] S705, Select a variable value from the range of values ​​for the first parameter;

[0236] S706, Select a variable value from the range of values ​​for the second parameter;

[0237] S707, Select composition relationship based on mutual exclusion or dependency relationship;

[0238] S708, merge constraints to generate a combined constraint;

[0239] S707, determine whether it is necessary to add more combined constraints; if so, return to execute S702, otherwise execute S710.

[0240] S710, completes a combined constraint condition.

[0241] For example, to add a new combined constraint, first add a pair of combined constraint relationships. Select the variable values ​​A(i) and B(j) for the two parameters as needed. Select the first parameter A, then select the variable value i within that parameter. Next, select the second parameter B, then select the variable value j within that parameter. Then, select the combined relationship based on the mutual exclusion "<>" or dependency "==" relationship, and merge the constraints to generate a combined constraint condition. For example, the combined constraint condition A(i) == B(j) means that when parameter A is i, parameter B is equal to j; the combined constraint condition A(i) <> B(j) means that when parameter A is i, parameter B is not equal to j. If you continue to add combined constraint relationships, you return to adding a pair of combined constraint conditions, such as the combination A(i) == B(j) == C(k), which means that when parameter A is i, parameter B is equal to j, and parameter C is equal to k. If no more combined constraint relationships are added, a combined constraint condition is completed.

[0242] For example, such as Figure 6 As shown, the process includes, but is not limited to: importing a set of combined test cases as a script file, editing the set of combined test cases, parsing the combined test cases, selecting a combination strategy, analyzing the combined test cases using a combined test case analysis algorithm, and outputting the combined coverage analysis results and its combined data set (as configured above). The specific implementation steps are as follows:

[0243] S301-2, The script for importing a set of combined test cases may include, but is not limited to: file formats ( .xls or In the .xlsx file, each column in the first row is a parameter name, indicating that the variable value in that column belongs to that parameter. Each row after the first row is a combined test case, with each column containing the variable value of a parameter.

[0244] S401-3, Editing the combined test case set can include, but is not limited to: adding, modifying, and deleting test cases, and editing a new set based on the combined test case set imported in step S301-2.

[0245] S501-3, the parsing of combined test cases may include, but is not limited to: parsing out the parameter names in the test case set, as well as the variable values ​​of each parameter contained in each test case.

[0246] S701-1, the selection of combination strategies may include, but are not limited to: t-way combination strategies, such as 1-way, 2-way, 3-way, 4-way, 5-way, 6-way, 7-way combination strategies, etc.

[0247] S701-2, the combined test case analysis algorithm can be a variety of analysis algorithms, such as heuristic algorithms, greedy algorithms, etc.

[0248] S801-3 to S801-2, the combined test case analysis algorithm analyzes the combined coverage analysis results and combined data set according to the selected combined strategy.

[0249] For example, the system architecture of the above-mentioned combined testing system can be as follows: Figure 8 As shown, this combined testing system can generate combined test cases based on the target number, configuration parameters, and combined constraints set in the combined design unit to obtain a set of combined test cases with optimized coverage and coverage analysis results for the full set of test cases. It can also perform in-depth analysis on the existing set of combined test cases based on the target number set in the combined analysis unit to obtain configuration parameters and coverage analysis results. Specifically, it includes a project management unit 101-1, a combined data management unit 201-1, an import unit 301, an editing unit 401, a parsing unit 501, a combined design unit 601, a combined analysis unit 701, and an output unit 801.

[0250] The system comprises the following components: Project Management Unit 101-1 for creating projects and editing basic project information; Composite Data Management Unit 201-1 for managing and maintaining typical composite data; Import Unit 301 for importing composite data set scripts and composite test case set scripts; Editing Unit 401 for editing imported composite data sets, composite test case sets, and typical composite data selected from Composite Data Management Unit 201-1; Parsing Unit 501 for parsing composite data, composite constraints, and composite test cases; Composite Design Unit 601 for constructing composite test case sets based on composite strategies; Composite Analysis Unit 701 for analyzing composite test case sets based on composite strategies; and Output Unit 801 for outputting composite coverage analysis results, composite test case sets, and composite data sets.

[0251] For example, the project management unit 101-1 is specifically used to provide a project management interface to users, in which they can create projects and edit basic project information. The basic project information specifically includes: project creation time, project description, editors, whether it is public to other users, whether the project belongs to the composite design or composite analysis type, and the basic project information is saved.

[0252] For example, the combined data management unit 201-1 is specifically used to provide users with a typical combined data management interface, in which users can add, modify and delete typical combined data. Typical combined data may include, but is not limited to, a basic data set, a public data set and a private data set, and the typical combined data is saved.

[0253] For example, the import unit 301 is specifically used to provide a script import interface to the user, in which the script is imported in a file format ( Import the combined dataset script in .txt format ( .xls or Import the combined test case set script (.xlsx file) and save the imported script;

[0254] For example, the editing unit 401 is specifically used to provide an editing interface to the user, where the user can edit the combined data set, combined constraints, and combined test case set, select typical combined data in the combined data management unit 201-1, save the edited combined data as typical combined data, and save the editing results.

[0255] For example, the combination design unit 601 is specifically used to provide a combination design interface to the user, in which the user selects a t-way combination strategy, selects a combination test case generation algorithm, and saves the constructed combination test case set and combination coverage analysis results.

[0256] For example, the combinatorial analysis unit 701 is specifically used to provide a combinatorial analysis interface to the user, in which the user selects a t-way combinatorial strategy, selects a combinatorial test case analysis algorithm, and saves the combinatorial coverage analysis results and combinatorial data set obtained from the analysis.

[0257] For example, the output unit 801 is specifically used to provide an output interface to the user, displaying the output in a file format (…). Output the combined data set in .txt format, as a file ( .xls or Output a set of combined test cases in .xlsx format ( Output the combined coverage analysis results in a .txt file.

[0258] In other words, in the aforementioned composite testing system, the project management unit is used to create projects and edit basic project information; the composite data management unit is used to manage and maintain typical composite data; the import unit is used to import composite data set scripts and composite test case set scripts; the editing unit is used to edit imported composite data sets, composite test case sets, and typical composite data selected from the composite data management unit; the parsing unit is used to parse composite data, composite constraints, and composite test cases; the composite design unit is used to construct composite test case sets based on composite strategies; the composite analysis unit is used to analyze composite test case sets based on composite strategies; and the output unit is used to output composite coverage analysis results, composite test case sets, and composite data sets.

[0259] In addition, the combined testing system may also include an interactive interface to display the project execution data of the combined test. The interactive interface includes, but is not limited to: project management interface, combined data management interface, script import interface, editing interface, combined design interface, combined analysis interface, output interface, etc.

[0260] For example, a schematic diagram of the project management interface is as follows: Figure 9 As shown, edit the project creation time, project description, editors, whether to make it public to other users, whether the project belongs to the combination design type or combination analysis type, and click the "OK" button to complete the creation of the combination test project;

[0261] For example, a schematic diagram of the combined data management interface is shown below. Figure 10 As shown, typical combined data is divided into three types: basic data set, shared data set, and private data set. The basic data set is open to all users, the shared data set is provided by users and can be used by other users but not modified, and the private data set can only be viewed and used by the user themselves. The typical combined data set is displayed and edited in tabular form. Clicking the "Save" button saves the edited results.

[0262] For example, a schematic diagram of the script import interface is shown below. Figure 11 As shown, scripts can be imported in two ways: local upload and online creation. For local upload, you can set file filtering formats, select the script file in your local directory, and click the "Import Script" button to complete the import. For online creation, select the required combined data set from the combined data management interface, or select a pre-generated combined test case set file from the database, and click the "Import Script" button to complete the import.

[0263] For example, a schematic diagram of the combined data set editing interface is shown below. Figure 12 As shown, the combined data set is displayed and edited in tabular form. Clicking the "Save" button will save the edited results of the combined data set.

[0264] For example, a schematic diagram of the combined test case editing interface is shown below. Figure 13 As shown, the combined test case set is displayed and edited in a table format. Click the "Save" button to save the edited result of the combined test case set.

[0265] For example, a schematic diagram of the combined constraint editing interface is shown below. Figure 14 As shown, edit the combined constraint by selecting the configuration parameters and their possible variable values. Click the "OK" button to complete the editing of a combined constraint.

[0266] For example, a schematic diagram of the composite design interface is as follows: Figure 15 As shown, selecting a t-way combination strategy (that is, determining the target number mentioned above) can include 1-way, 2-way, 3-way, 4-way, 5-way, 6-way, 7-way combination strategies, etc. Clicking the "Combination Design" button will trigger the construction of the combination test case set.

[0267] For example, a schematic diagram of the combined analysis interface is shown below. Figure 16 As shown, select the t-way combination strategy, which includes 1-way, 2-way, 3-way, 4-way, 5-way, 6-way, and 7-way combination strategies. Click the "Combination Analysis" button to trigger the analysis of the combination coverage.

[0268] For example, a schematic diagram of the output interface is as follows: Figure 17 As shown, clicking the "Download" button triggers the output of a set of combined test cases or a set of combined test data.

[0269] In summary, the aforementioned combined testing system supports interaction in combined test design, combined test analysis, and combined test data management, establishing a closed loop for the entire combined testing process. It supports on-demand interactive generation of combined test cases and analysis of combined test case sets. It supports coverage analysis of combined test case sets, dynamically analyzing execution rate and coverage by combining test case execution and test result feedback. This meets the test coverage requirements of critical or high-reliability scenarios such as satellite internet system testing and satellite network system testing. Compared to traditional tools that only provide a single algorithm, this application's embodiments support the use of fixed or random combined test case generation algorithms, and the constructed combined test case sets can be fixed or random. It also allows for group management of t-way combined test case sets and management of typical combined data, supporting a mechanism for continuous accumulation and reuse of typical combined data. It supports both scripted and interface editing, making the data editing process efficient and intuitive.

[0270] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0271] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0272] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0273] Based on this understanding, the technical solution of this application, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0274] According to another aspect of the embodiments of this application, a combined testing apparatus for implementing the above-described combined testing method is also provided. This combined testing apparatus can be used to implement the combined testing method provided in the above embodiments, and details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that performs a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0275] Figure 18 This is a structural block diagram of an optional combined testing device according to an embodiment of this application, such as... Figure 18 As shown, the combined testing apparatus includes:

[0276] The first acquisition module 1802 is used to acquire at least two configuration parameters, combined constraints, and target quantity in the satellite internet system. The configuration parameters include at least one parameter value, the combined constraints are used to indicate the constraint relationship between different configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases to be generated.

[0277] The first generation module 1804 is used to perform a test case generation operation on the configuration parameters using the target quantity and combined constraints, and generate at least one combined test case.

[0278] The determination module 1806 is used to determine the coverage analysis results based on the coverage of the combined test cases relative to the full set of test cases, wherein the number of combined test cases is less than or equal to the number of full test cases, and the coverage analysis results are used to update the combined test cases.

[0279] As an optional approach, test case generation is performed on at least two configuration parameters based on the target quantity and combined constraints to generate at least one combined test case. This includes: parsing the combined constraints to obtain the constraint relationship between the configuration parameters, and parsing at least two configuration parameters to obtain the values ​​corresponding to each configuration parameter; determining at least one parameter combination from the combined data set based on the target quantity, wherein one parameter combination includes the configuration parameters of the target quantity; updating the parameter values ​​of the configuration parameters in the parameter combination based on the constraint relationship; and performing test case generation on the parameter combination to generate combined test cases.

[0280] As an optional approach, a test case generation operation is performed on the parameter combination to generate combined test cases, including at least one of the following: using a heuristic algorithm to perform a test case generation operation on the parameter combination to generate combined test cases; or using a greedy algorithm to perform a test case generation operation on the parameter combination to generate combined test cases.

[0281] As an optional approach, obtaining at least two configuration parameters, combined constraints, and target quantity in a satellite internet system includes: obtaining initial constraints, wherein the initial constraints are used to indicate the constraint relationship between at least two configuration parameters, and the constraint relationship is a mutual exclusion relationship or a dependency relationship; and updating the initial constraints to obtain combined constraints in response to a condition update operation.

[0282] As an optional approach, obtaining initial constraints may include at least one of the following: obtaining initial constraints from a constraint database, wherein the constraint database stores constraints related to historical test types of the satellite internet system; or obtaining initial constraints in response to a constraint generation operation.

[0283] As an alternative approach, in response to a condition update operation, the initial constraints are updated to obtain combined constraints, including at least one of the following: adding a first constraint to the initial constraints to obtain combined constraints; modifying a second constraint to the initial constraints to obtain combined constraints; or deleting a third constraint from the initial constraints to obtain combined constraints.

[0284] As an optional approach, obtaining at least two configuration parameters, combined constraints, and target quantity in the satellite internet system includes: determining a first value for a first configuration parameter and a second value for a second configuration parameter, wherein the first configuration parameter is any configuration parameter and the second configuration parameter is any configuration parameter other than the first configuration parameter; determining a constraint identifier based on the current test type of the satellite internet system; and using the constraint identifier to associate the first configuration parameter and the second configuration parameter to obtain the combined constraints.

[0285] As an optional approach, the method further includes at least one of the following: associating the first configuration parameter and the second configuration parameter with a mutual exclusion constraint identifier to obtain a combined constraint condition, wherein the combined constraint condition indicates that when the parameter value of the first configuration parameter is a first value, the parameter value of the second configuration parameter is any parameter value other than a second value, and the constraint identifier includes a mutual exclusion constraint identifier; associating the first configuration parameter and the second configuration parameter with a dependency constraint identifier to obtain a combined constraint condition, wherein the combined constraint condition indicates that when the parameter value of the first configuration parameter is a first value, the parameter value of the second configuration parameter is a second value, and the constraint identifier includes a dependency constraint identifier.

[0286] As an optional approach, obtaining at least two configuration parameters, combined constraints, and target quantity in a satellite internet system includes: receiving a third configuration parameter and a fourth configuration parameter, wherein the third configuration parameter is determined based on a data import operation, and the fourth configuration parameter is pre-stored in a combined database; determining configuration parameters based on the third and fourth configuration parameters; and storing the configuration parameters in the combined database.

[0287] As an optional approach, the method further includes: obtaining a full set of test cases, wherein the full set of test cases is determined by a full set of parameter combinations, the full set of parameter combinations includes any parameter combination, and a parameter combination includes a target number of configuration parameters; comparing the full set of test cases and the combined test cases to obtain coverage analysis results; and updating the combined test cases based on the coverage analysis results.

[0288] Figure 19 This is a structural block diagram of an optional combined testing device according to an embodiment of this application, such as... Figure 19 As shown, the combined testing apparatus includes:

[0289] The second acquisition module 1902 is used to acquire the combined test cases and the target number, wherein the target number is used to indicate the parameter dimension of the combined test cases;

[0290] The second generation module 1904 is used to perform test case analysis operations on the combined test cases based on the target number, and generate at least two configuration parameters and coverage analysis results. The coverage analysis results are used to indicate the coverage of the combined test cases relative to the full set of test cases. The number of combined test cases is less than or equal to the number of full test cases. The coverage analysis results are used to update the combined test cases.

[0291] Regarding the apparatus in the embodiments, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit. The specific manner in which the various modules perform their operations has been described in detail in the embodiments relating to the method, and will not be elaborated upon here.

[0292] According to another aspect of the embodiments of this application, an electronic device is provided.

[0293] The electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor is configured to perform the steps in any of the above method embodiments via the computer program. In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor. Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0294] According to one aspect of this application, a computer program product is also provided, which includes a computer program.

[0295] The computer program product includes a computer program / instructions containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 2009, and / or installed from removable media 2011. When the computer program is executed by central processing unit 2001, it performs various functions provided in the embodiments of this application. The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0296] Figure 20 A schematic block diagram of a computer system architecture for implementing embodiments of the present application is shown. Figure 20As shown, the computer system 2000 includes a Central Processing Unit (CPU) 2001, which can perform various appropriate actions and processes based on programs stored in ROM 2002 or programs loaded into RAM 2003 from storage 2008. Random Access Memory 2003 also stores various programs and data required for system operation. The CPU 2001, ROM 2002, and RAM 2003 are interconnected via bus 2004. Input / Output (I / O) interface 2005 is also connected to bus 2004.

[0297] The following components are connected to I / O interface 2005: input section 2006 including keyboard, mouse, etc.; output section 2007 including cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; storage section 2008 including hard disk, etc.; and communication section 2009 including network interface card, modem, etc. Communication section 2009 performs communication processing via a network such as the Internet. Drive 2010 is also connected to I / O interface 2005 as needed. Removable media 2011, such as disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 2010 as needed so that computer programs read from them can be installed into storage section 2008 as needed.

[0298] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0299] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer programs / instructions. For example, embodiments of this application include a computer program / instruction comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication portion, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions defined in the system of this application. In such embodiments, the computer program / instruction can be downloaded and installed from a network via a communication portion, and / or installed from a removable medium. When the computer program / instruction is executed by a central processing unit, the above-described combined test method is performed.

[0300] According to one aspect of this application, a computer-readable storage medium is also provided.

[0301] The processor of the aforementioned electronic device can read the computer instructions from a computer-readable storage medium, and the processor executes the computer instructions to cause the electronic device to perform the combined test method provided in the various optional implementations of the combined test aspect.

[0302] Optionally, in this embodiment, the computer-readable storage medium described above may be configured to store methods for performing the embodiments of this application.

[0303] Optionally, in this embodiment, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0304] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0305] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more electronic devices to execute all or part of the steps of the methods described in the various embodiments of this application.

[0306] In the several embodiments provided in this application, it should be understood that the disclosed application can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0307] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0308] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0309] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A combined testing method, characterized in that, Applications in satellite internet systems include: Obtain at least two configuration parameters, combined constraints, and target quantity from the satellite internet system, wherein the configuration parameters include at least one parameter value, the combined constraints are used to indicate the constraint relationship between different configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test case; Using the target quantity and the combined constraints, perform a test case generation operation on the configuration parameters to generate at least one of the combined test cases; The coverage analysis result is determined based on the coverage of the combined test cases relative to the full set of test cases, wherein the number of combined test cases is less than or equal to the number of full set of test cases, and the coverage analysis result is used to update the combined test cases.

2. The method according to claim 1, characterized in that, The step of performing a test case generation operation on at least two of the configuration parameters based on the target quantity and the combined constraints, generating at least one of the combined test cases, includes: The combined constraint conditions are parsed to obtain the constraint relationship between the configuration parameters, and the at least two configuration parameters are parsed to obtain the values ​​corresponding to each configuration parameter. At least one parameter combination is determined from the combined data set based on the target quantity, wherein one parameter combination includes the configuration parameters for the target quantity; Update the parameter values ​​of the configuration parameters in the parameter combination based on the constraint relationship; Perform a test case generation operation on the parameter combination to generate the combined test cases.

3. The method according to claim 2, characterized in that, The step of performing a test case generation operation on the parameter combination to generate the combined test cases includes at least one of the following: The test case generation operation is performed on the parameter combination using a heuristic algorithm to generate the combined test cases; The test case generation operation is performed on the parameter combination using a greedy algorithm to generate the combined test cases.

4. The method according to claim 1, characterized in that, The acquisition of at least two configuration parameters, combined constraints, and target quantity in the satellite internet system includes: Obtain initial constraints, wherein the initial constraints are used to indicate the constraint relationship between at least two of the configuration parameters, and the constraint relationship is a mutual exclusion relationship or a dependency relationship; In response to the condition update operation, the initial constraints are updated to obtain the combined constraints.

5. The method according to claim 4, characterized in that, The initial constraint conditions are obtained, including at least one of the following: The initial constraints are obtained from the constraint database, which stores constraints related to the historical test types of the satellite internet system. In response to the constraint generation operation, the initial constraint conditions are obtained.

6. The method according to claim 4, characterized in that, The process of updating the initial constraints in response to a condition update operation to obtain the combined constraints includes at least one of the following: Add a first constraint to the initial constraints to obtain the combined constraints. Modify the second constraint in the initial constraint to obtain the combined constraint; The combined constraint conditions are obtained by deleting the third constraint condition from the initial constraint conditions.

7. The method according to claim 1, characterized in that, The acquisition of at least two configuration parameters, combined constraints, and target quantity in the satellite internet system includes: A first value of a first configuration parameter is determined, and a second value of a second configuration parameter is determined, wherein the first configuration parameter is any of the configuration parameters and the second configuration parameter is any of the configuration parameters other than the first configuration parameter; The constraint identifier is determined based on the current test type of the satellite internet system; The first configuration parameter and the second configuration parameter are associated with the constraint identifier to obtain the combined constraint condition.

8. The method according to claim 7, characterized in that, The method further includes at least one of the following: The first configuration parameter and the second configuration parameter are associated using a mutual exclusion constraint identifier to obtain the combined constraint condition, wherein the combined constraint condition indicates that when the parameter value of the first configuration parameter is the first value, the parameter value of the second configuration parameter is any parameter value other than the second value, and the constraint identifier includes the mutual exclusion constraint identifier; The first configuration parameter and the second configuration parameter are associated using a dependency constraint identifier to obtain the combined constraint condition, wherein the combined constraint condition indicates that when the parameter of the first configuration parameter is a first value, the parameter of the second configuration parameter is a second value, and the constraint identifier includes the dependency constraint identifier.

9. The method according to claim 1, characterized in that, The acquisition of at least two configuration parameters, combined constraints, and target quantity in the satellite internet system includes: Receive a third configuration parameter and a fourth configuration parameter, wherein the third configuration parameter is determined based on a data import operation, and the fourth configuration parameter is pre-stored in a combined database; The configuration parameters are determined based on the third configuration parameter and the fourth configuration parameter; The configuration parameters are stored in the combined database.

10. The method according to claim 1, characterized in that, The method further includes: Obtain the full set of test cases, wherein the full set of test cases is determined by a full set of parameter combinations, the full set of parameter combinations includes any parameter combination, and each parameter combination includes the target number of configuration parameters; The coverage analysis results are obtained by comparing the full set of test cases and the combined test cases. The combined test cases are updated based on the coverage analysis results.

11. A combined testing method, characterized in that, Applications in satellite internet systems include: Obtain the combined test cases and the target number, wherein the target number is used to indicate the parameter dimension of the combined test cases; Based on the target number, perform test case analysis on the combined test cases to determine at least two configuration parameters. The coverage analysis result is used to indicate the coverage of the combined test cases relative to the full set of test cases. The number of combined test cases is less than or equal to the number of full set of test cases. The configuration parameters include at least one parameter value. The coverage analysis result is used to update the combined test cases.

12. A combined testing system, characterized in that, Applications include: A data management unit is used to determine at least two configuration parameters, combined constraints, and a target quantity, wherein each of the configuration parameters includes at least one parameter value, the combined constraints are used to indicate the constraint relationship between the configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases to be generated. A parsing unit is used to parse the combined test cases to obtain at least two of the configuration parameters and the constraint relationships between the configuration parameters; A combined design unit is configured to perform test case analysis operations on the combined test cases based on the target number, and generate at least one combined test case and a coverage analysis result, wherein the coverage analysis result is used to indicate the coverage degree of the combined test cases relative to the full number of test cases, the number of combined test cases is less than or equal to the number of full test cases, and the coverage analysis result is used to update the combined test cases; The combined analysis unit is used to perform test case analysis operations on the combined test cases based on the target number, and determine at least two of the configuration parameters and coverage analysis results; The output unit is used to output at least one of the following: at least two of the configuration parameters, the combined test cases, and the coverage analysis results.

13. A combined testing device, characterized in that, Applications in satellite internet systems include: The first acquisition module is used to acquire at least two configuration parameters, combined constraints, and target quantity in the satellite internet system, wherein the configuration parameters include at least one parameter value, the combined constraints are used to indicate the constraint relationship between different configuration parameters, and the target quantity is used to indicate the parameter dimension of the combined test cases to be generated; The first generation module is used to perform a test case generation operation on the configuration parameters using the target quantity and the combined constraints, and generate at least one of the combined test cases. The determination module is used to determine the coverage analysis result based on the coverage of the combined test cases relative to the full set of test cases, wherein the number of combined test cases is less than or equal to the number of full set of test cases, and the coverage analysis result is used to update the combined test cases.

14. A combined testing device, characterized in that, Applications in satellite internet systems include: The second acquisition module is used to acquire the combined test cases and the target number, wherein the target number is used to indicate the parameter dimension of the combined test cases; The second generation module is used to perform test case analysis operations on the combined test cases based on the target number, and generate at least two configuration parameters and coverage analysis results, wherein the coverage analysis results are used to indicate the coverage degree of the combined test cases relative to the full number of test cases, the number of combined test cases is less than or equal to the number of full test cases, and the coverage analysis results are used to update the combined test cases.

15. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 10 or claim 11.

16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 10 or claim 11.

17. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 10 or claim 11.

Images