WO2019084861A1 - 测试软件的方法和装置 - Google Patents
测试软件的方法和装置 Download PDFInfo
- Publication number
- WO2019084861A1 WO2019084861A1 PCT/CN2017/109062 CN2017109062W WO2019084861A1 WO 2019084861 A1 WO2019084861 A1 WO 2019084861A1 CN 2017109062 W CN2017109062 W CN 2017109062W WO 2019084861 A1 WO2019084861 A1 WO 2019084861A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- functional component
- functional
- combination
- software
- performance information
- Prior art date
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
Definitions
- the present application relates to the field of software testing and, more particularly, to a method and apparatus for testing software.
- Testing software products is an important means of quality control. Integration testing is a kind of software testing. By verifying the aggregated form of each component of the software product, it identifies defects and deficiencies that are globally unrecognizable.
- test results of the integration test are usually based on the achievement of the function and whether a comprehensive performance parameter is within the required range. As a result, some performance deviations, accumulated errors, etc. may be left in the software product, and the software product may be discovered later.
- the function output or performance parameters are not up to standard, the problem analysis backtracking and modification and re-verification are carried out, which lengthens the development cycle and reduces the development efficiency.
- the embodiment of the present application provides a method and device for testing software, which can shorten the development cycle and improve the development efficiency.
- a method of testing software comprising:
- Each functional component of the plurality of functional components included in the software to be tested is separately operated in sequence, and reference performance information of each functional component is determined, and reference performance information of each functional component is when the functional component is operated.
- Software status information, wherein the plurality of functional components include a first functional component;
- each of the plurality of functional component combinations of the software to be tested to determine integrated performance information of each functional component combination is Software status information when the functional components are combined, each of the functional components being combined into a combination of at least two of the plurality of functional components, wherein the plurality of functional component combinations include the first functional component combination ;
- the method for testing software in the embodiment of the present application may separately run software state information of each functional component as reference performance information corresponding to each functional component, and then cross-combine test multiple functional components of the software to be tested. Obtaining integration performance information of each functional component combination, and further determining whether the integration test affects performance of the software to be tested according to the integration performance information of each functional component combination and the reference performance information of the corresponding functional component of each functional component combination. Therefore, problems that may occur during software integration testing can be discovered in advance, and then analysis and modification and re-verification of functional components that may have problems can be performed, thereby avoiding introducing potential problems into the software integration testing phase.
- the operating each of the plurality of functional components included in the software to be tested is separately executed in sequence, and the reference performance information of each functional component is determined, including :
- the first functional component is run multiple times, and the reference performance information of the first functional component is determined according to software state information when the first functional component is run multiple times.
- the first functional component when the first functional component is separately operated, the first functional component is enabled while enabling other functions of the plurality of functional components Component.
- the functional component combination of the plurality of functional component combinations of the software to be tested are sequentially executed to determine an integration performance of each functional component combination Information, including:
- the first functional component combination is run multiple times, and the integrated performance information of the first functional component combination is determined according to the software state information when the first functional component combination is run multiple times.
- the first functional component combination when the first functional component combination is run, enabling the at least two functional components corresponding to the first functional component combination to enable the multiple Other functional components of the functional components other than the first functional component combination.
- the integration performance information according to the combination of each functional component and reference performance information of at least two functional components corresponding to each functional component combination Determining the performance of the software to be tested, including:
- the first functional component combination does not cause a degradation in the performance of the software to be tested.
- a difference between an average of the integrated performance information of the first functional component combination and an average of the reference performance information of each of the at least two functional components is less than or equal to a first threshold
- the first function a difference between a maximum value of the integrated performance information of the component combination and a maximum value of the reference performance information of each of the at least two functional components is less than or equal to a second threshold
- the integration of the first functional component combination The difference between the minimum value of the performance information and the minimum value of the reference performance information of each of the at least two functional components is less than or equal to a third threshold.
- the software status information includes at least one of a central processor CPU usage, a memory usage, and a running time.
- the method further comprises:
- a list of integrated test combinations is determined, the list of integrated test combinations including the plurality of functional component combinations.
- the determining the integrated test combination list comprises:
- an apparatus for testing software comprising functional modules for performing the method of any of the first aspect or the first aspect of the first aspect.
- a chip comprising an input and output interface, at least one processor, at least one memory and a bus, the at least one memory for storing instructions, the at least one processor for calling the at least one memory An instruction to perform the method of the first aspect or any of the possible implementations of the first aspect.
- a computer readable medium for storing a computer program, the computer program comprising instructions for performing the first aspect or any of the possible implementations of the first aspect.
- a computer program product comprising instructions for operating when the computer is The computer program implements the method of testing software in any of the possible implementations of the first aspect or the first aspect described above.
- FIG. 1 is a schematic flowchart of a method of testing software according to an embodiment of the present application.
- FIG. 2 is a flow chart of a method of testing software in accordance with another embodiment of the present application.
- FIG. 3 is a schematic block diagram of an apparatus for testing software in accordance with an embodiment of the present application.
- FIG. 4 is a schematic block diagram of an apparatus for testing software in accordance with another embodiment of the present application.
- the method 100 includes:
- Each functional component of the plurality of functional components included in the software to be tested is separately operated in sequence, and reference performance information of each functional component is determined, and reference performance information of each functional component is to run each of the functional components.
- the software to be tested may include multiple functional components, or the software to be tested is a combination of multiple functional components.
- each functional component may be separately operated in sequence, and each of the individual components is determined to be run separately.
- Software status information when functional components For example, when each functional component is run separately, the software status information when running each functional component separately, such as CPU usage, memory usage, and running time, can be obtained through system monitoring.
- the plurality of functional components include the first functional component
- the first functional component needs to be separately operated, enabling the first functional component while disabling the multiple functional functions Other functional components in the component, and then running the first functional component separately, obtaining software state information for separately running the first functional component.
- software state information when each of the functional components is separately operated may be used as reference performance information (or may also be referred to as a reference level value) of each functional component, and each functional component is When one or more other functional components are tested for integration, the software state information during the integration test and the reference performance information of the functional component can be compared to determine whether the integration test of the functional component and other functional components causes the performance of the software to be tested. Fall, or say, that Whether the combination of functional components and other functional components affects the performance of the software to be tested.
- the software to be tested is a fingerprint module testing software
- the fingerprint module testing software may include a module working mode current detecting component, a module static power consumption current detecting component, a module pin open short state detecting component, and a module. Group thickness detection component.
- the above four functional components may be sequentially operated to determine software state information when each functional component is separately operated, and software state information when each functional component is separately operated is used as reference performance information of each functional component.
- the reference performance information of each functional component may include at least one of a CPU usage, a memory usage, and a running time when the each functional component is separately operated.
- S110 may specifically include:
- the first functional component is run multiple times, and the reference performance information of the first functional component is determined according to software state information when the first functional component is run multiple times.
- each of the plurality of functional components may be run multiple times, and the reference performance information of each functional component is determined according to software state information when the functional components are repeatedly run.
- the acquired software status information of the first function component may be processed for multiple times, for example, the abnormal value may be removed, and further, the software that runs the first functional component may be acquired multiple times.
- An average value, a maximum value, or a minimum value in the state information, and the obtained average value, maximum value, or minimum value in the software state information obtained by running the first function component for multiple times is determined as the first functional component.
- the reference performance information of the first functional component may include at least one of an average value, a maximum value, and a minimum value in the software state information obtained by running the first soft component multiple times, such that The reference performance information of the first functional component is statistically significant performance information.
- the reference performance information of the first functional component may include a reference corresponding to the CPU usage when the first functional component is separately operated.
- the reference level value corresponding to the CPU usage may include at least one of an average value, a maximum value, and a minimum value of CPU usage obtained by running the first function component multiple times, for memory usage and running. The reference level values corresponding to the time consumption are similar and will not be described here.
- determining, according to software state information of each functional component, whether the performance of each functional component is up to standard for example, each functional component may correspond to corresponding
- the performance range can determine the performance of each functional component when the software state information of each functional component is within the corresponding performance range. Otherwise, the performance of the functional component is not up to standard, and if the performance of the functional component is not up to standard , the problem component needs to be analyzed, modified and retested until the performance of the functional component is up to standard.
- function output information of each functional component may also be determined, and the function output information of each functional component may be used to determine a function achievement of each functional component.
- the reference performance information of each functional component is the performance compliance of the functional component and the software state information in the case of the functional compliance. If the performance and/or function of a functional component is not up to standard, The function component needs to be analyzed, modified and retested until the performance and function of the functional component meets the standard, and the software state information obtained under the function and performance of the functional component can be used as a reference for the functional component. Performance information. That is to say, in the case that the functions and performances of each of the functional components are up to standard, the subsequent processes of S120 and S130 are further performed, otherwise problem analysis and modification of the non-compliant functional components are required to avoid introducing potential problems into integration. testing.
- a plurality of functional component combinations may be obtained according to the plurality of functional components included in the software to be tested, each functional component being combined into a combination of at least two functional components of the multiple functional components, or Said that each functional component combination corresponds to at least two functional components.
- the multiple functional components may be combined to obtain the multiple functional component combinations by using a combination of two or two, or a three-three combination, or an orthogonal design method, or a uniform design method, and the embodiment of the present application is The manner in which the plurality of functional components are combined is not limited.
- each of the plurality of functional component combinations may be sequentially executed to obtain integrated performance information (or may also be referred to as an integration level value) for running each functional component combination.
- running a certain functional component combination refers to simultaneously running at least two functional components corresponding to the functional component combination. Specifically, when it is required to run the first functional component combination of the plurality of functional component combinations, enabling the at least two functional components corresponding to the first functional component combination to disable the multiple functions Other functions in the component other than the first functional component combination And then running the at least two functional components corresponding to the first functional component combination, and acquiring software state information when the first functional component combination is run, and using the integrated performance information as the first functional component combination, That is, the first functional component is combined into software state information when the at least two functional components corresponding to the first functional component combination are simultaneously run.
- S120 may specifically include:
- the first functional component combination is run multiple times, and the integrated performance information of the first functional component combination is determined according to the software state information when the first functional component combination is run multiple times.
- each of the plurality of functional component combinations can be run multiple times, and the integration of each functional component combination is determined according to software state information when the functional component combination is run multiple times.
- Performance information Specifically, the obtained software status information of the first functional component combination may be processed for multiple times, for example, the abnormal value may be removed, and further, the first functional component combination may be acquired multiple times.
- the average value, the maximum value, or the minimum value in the software state information of the software, and the obtained average value, the maximum value, or the minimum value in the software state information obtained by combining the first function components are determined as the first Integrated performance information for functional component combinations.
- the integrated performance information of the first functional component combination may include at least one of an average value, a maximum value, and a minimum value in the software state information of the first soft component combination being run multiple times, such that the The integrated performance information of a functional component combination is statistically significant performance information.
- the integrated performance information of the first functional component combination may include CPU usage when the first functional component combination is run.
- the integration level value corresponding to the CPU usage may be at least one of an average value, a maximum value, and a minimum value in the software state information obtained by running the first functional component combination multiple times, and similarly, for the memory. The same is true for the usage level and the integration level value corresponding to the running time, and will not be described here.
- each functional component may be determined according to the integrated performance information of each functional component combination and the reference performance information of the at least two functional components corresponding to each functional component combination. , that is, integration testing of functional components (or Said, combined test) will affect the performance of the software to be tested.
- each function may be determined according to a difference between the reference performance information of each of the at least two functional components of each functional component combination and the integrated performance information of each functional component combination. Whether the combination of components causes a drop in the performance of the software to be tested.
- the integration test does not cause a degradation in the performance of the software to be tested when the difference between the reference performance information of each functional component and the integrated performance information of each of the functional component combinations is below a certain threshold. That is to say, if the performance parameter when the functional component is run separately and the performance parameter of the functional component and the other functional component are running at the same time, the function component and the integration test are tested separately. There is little difference in software state between components and other functional components, and it can be determined that the integration test does not cause a degradation in the performance of the software to be tested.
- the functional component combination does not cause a decrease in the performance of the software to be tested, and the performance of the functional component combination can be considered to be up to standard. Otherwise, the functional component combination is considered to be out of compliance. If the performance of some functional component combinations in a plurality of functional component combinations is up to standard, the performance of other functional component combinations may not be up to standard, and in S130, the analysis and traceability of the problem may be performed in advance according to the combination of the functional components that meet the standard and not meet the standard.
- a difference between an average of the integrated performance information of the first functional component combination and an average of the reference performance information of each of the at least two functional components is less than or equal to a first threshold
- the first function a difference between a maximum value of the integrated performance information of the component combination and a maximum value of the reference performance information of each of the at least two functional components is less than or equal to a second threshold
- the integration of the first functional component combination The difference between the minimum value of the performance information and the minimum value of the reference performance information of each of the at least two functional components is less than or equal to a third threshold.
- the first threshold, the second threshold, and the third threshold may be set according to engineering experience or user requirements.
- the integration test of each functional component combination does not cause a decrease in the performance of the software to be tested
- determining that the software integration test does not cause the soft to be tested The performance of the component is decreased, and the first threshold, the second threshold, and the third threshold corresponding to each function component combination for determining whether to cause the performance of the software to be tested to be degraded may be the same or different, that is, different functional components.
- the combination can correspond to the corresponding performance range, that is, different functional component combinations can correspond to different performance ranges, and can also correspond to the same performance range.
- the different reference performance information may also correspond to the corresponding performance range, or different reference performance information may correspond to corresponding thresholds, for example, CPU usage, memory usage, and operation time consumption may correspond to corresponding threshold ranges, for example, The threshold corresponding to the CPU usage may be 50%, the threshold corresponding to the memory usage may be 1M, and the threshold corresponding to the running time may be 10 minutes.
- the method for testing software in the embodiment of the present application may separately run software state information of each functional component as reference performance information corresponding to each functional component, and then cross-combine test multiple functional components of the software to be tested. Obtaining integration performance information of each functional component combination, and further determining whether the integration test affects performance of the software to be tested according to the integration performance information of each functional component combination and the reference performance information of the corresponding functional component of each functional component combination. Therefore, problems that may occur during software integration testing can be discovered in advance, and then analysis and modification and re-verification of functional components that may have problems can be performed, thereby avoiding introducing potential problems into the software integration testing phase.
- the separate operation may be acquired.
- Reference performance information of the first functional component and reference performance information of the second functional component separately may be software status information obtained by separately running the first functional component
- the average value, the maximum value, or the minimum value, and the reference performance information of the second functional component may be an average value, a maximum value, or a minimum value of software state information obtained by separately running the second functional component.
- the first functional component and the second functional component (other functional components except the first functional component and the second functional component are in a de-enabled state) can be simultaneously run, and the integrated performance when the first functional component combination is run is obtained.
- the information, the integrated performance information of the first functional component combination may be an average value, a maximum value, or a minimum value in the software state information obtained when the first functional component combination is run multiple times.
- the first preset threshold and the second preset threshold may be equal or not
- the method 20 includes the following contents:
- the software to be tested is a fingerprint module testing software
- the fingerprint module testing software may include a module working mode current detecting component (referred to as component A), a module static power consumption current detecting component (recorded as component B), and a mode.
- the above four functional components may be sequentially operated in the order of the A component, the B component, the C component, and the D component. Specifically, when the A component is run, the A component is enabled, and the B component and the C component are enabled. D component.
- the enabled functional component is run, and the performance parameter (corresponding to the software state information above) for running the functional component is obtained, and the performance parameter is used as a reference performance parameter corresponding to the functional component (corresponding to The reference performance information above), ie the reference level value.
- the integrated test combination list may include a plurality of functional component combinations, for example, may be combined by a two-two combination, a three-three combination, an orthogonal design method, or a uniform design method, etc., to obtain the integrated test combination list.
- the integrated test combination list includes the following combinations: A component + B component, A component + C component, A component + D component, B component + C component, B Component + D component, C component + D component.
- the orthogonal test design method is used to determine the integrated test combination list corresponding to the fingerprint module test software, firstly, according to the number of functional components included in the fingerprint module test software, the orthogonal table L 8 (2 7 ) is determined. ,As shown in Table 1.
- a list of integrated test combinations including the fingerprint module test component can be obtained, so that the cross-combination test of the functional components can be performed according to the integrated test combination list.
- the A component + B component when the A component + B component needs to be run, the A component + B component is enabled, that is, both the A component and the B component are enabled, and the C component and the D component are enabled.
- the enabled functional component combination is run, and the integrated performance parameter, that is, the integration level value, when the functional component combination is run is obtained.
- the integration level value and the reference level value of the A component and the reference level value of the B component may be compared to determine the integration level value and the A component.
- the difference between the reference level values, and the level of integration The difference between the reference level values of the B component.
- the reference level value may be an average value, a maximum value, or a minimum value of performance parameters when the single function component is run multiple times.
- the difference between the integration level value and the reference level value of the A component may be The difference between the integrated level value and the average of the performance parameters when the A component is run multiple times, or the difference between the integration level value and the reference level value of the A component may also be an integrated level value and multiple runs.
- the difference between the maximum values of the performance parameters of the A component, or the difference between the integration level value and the reference level value of the A component may also be the integration level value and the performance parameter when the A component is run multiple times.
- the performance of the software to be tested is determined based on the difference between the integrated level value and the reference level value acquired in S26.
- the functional component combination affects performance of the software to be tested, That is to say, the combined test of the functional components in the functional component combination may affect the performance of the software to be tested.
- the test results may be analyzed to further determine the root cause of the problem.
- the root cause of the performance of the software to be tested may also be determined by combining the comparison results of the functional components in the functional software combination in other functional component combinations.
- the average value of the integration level value and the average value of the reference level value may be made the difference, and the integration level value may be the largest.
- the difference between the value and the reference level value is made worse, and the minimum value of the integrated level value and the minimum value of the reference level value are made worse.
- the method for testing software in the embodiment of the present application can perform cross-combination testing between multiple functional components of the software to be tested before performing the overall integration test of the software to be tested. It is determined before which combination of functional components may run the performance of the software to be tested, so that the analysis and traceability of the problem can be performed in advance, and the re-verification can be modified, thereby shortening the software development cycle and speeding up the software development process.
- the method for testing software in the embodiment of the present application can perform problem analysis and traceability when the performance of a certain functional component combination is not up to standard, compared to when the overall integration test performance of the software to be tested is not up to standard, The analysis and traceability of the problem greatly reduces the difficulty of troubleshooting and the time for troubleshooting.
- the embodiment of the method of the present application is described in detail below with reference to FIG. 1 and FIG. 2 .
- the device embodiment of the present application is described in detail below with reference to FIG. 3 and FIG. 4 . It should be understood that the device embodiment and the method embodiment correspond to each other. The description of the method can be referred to the method embodiment.
- FIG. 3 is a schematic block diagram of an apparatus 300 for testing software according to an embodiment of the present application. As shown in FIG. 3, the apparatus 300 includes:
- a determining module 310 configured to sequentially run each of the plurality of functional components included in the software to be tested, and determine reference performance information of each functional component, where the reference performance information of each functional component is an operation Software status information when each functional component is described, wherein the plurality of functional components include a first functional component; each functional component combination of the plurality of functional component combinations of the software to be tested is sequentially executed, and the Integrated performance information of each functional component combination, the integrated performance information of each functional component combination being software state information when running each of the functional component combinations, the each functional component being combined into the multiple functional components a combination of at least two functional components, wherein the plurality of functional component combinations include a first functional component combination; and integrated performance information according to the combination of each functional component and a corresponding one of each functional component combination Determining performance of the software to be tested by reference performance information of at least two functional components.
- the determining module 310 is specifically configured to:
- the first functional component is run multiple times, and the reference performance information of the first functional component is determined according to software state information when the first functional component is run multiple times.
- the first functional component when the first functional component is separately operated, the first functional component is enabled while the other functional components of the plurality of functional components are disabled.
- the determining module 310 is specifically configured to:
- the first functional component combination is run multiple times, and the integrated performance information of the first functional component combination is determined according to the software state information when the first functional component combination is run multiple times.
- the first functional component combination when the first functional component combination is run, enabling the at least two functional components corresponding to the first functional component combination to disable the multiple functional components Other functional components than the first functional component combination.
- the determining module 310 is specifically configured to:
- the first functional component combination does not cause a degradation in the performance of the software to be tested.
- a difference between an average of the integrated performance information of the first functional component combination and an average of the reference performance information of each of the at least two functional components is less than or equal to a first threshold
- the first function a difference between a maximum value of the integrated performance information of the component combination and a maximum value of the reference performance information of each of the at least two functional components is less than or equal to a second threshold
- the integration of the first functional component combination The difference between the minimum value of the performance information and the minimum value of the reference performance information of each of the at least two functional components is less than or equal to a third threshold.
- the software status information includes at least one of a central processor CPU usage, a memory usage, and a running time.
- the determining module 310 is further configured to:
- a list of integrated test combinations is determined, the list of integrated test combinations including the plurality of functional component combinations.
- the determining module 310 is specifically configured to:
- the embodiment of the present application further provides a device 400 for testing software, which can be used as the device 300 of the test software shown in FIG. 3, which can be used to perform with FIG. 1 or FIG.
- the specific content of the method includes a processor 410.
- the processor 410 of the embodiment of the present application may be an integrated circuit chip with signal processing capability.
- each step of the foregoing method embodiment may pass through a processor.
- the integrated logic of the hardware or the instructions in software form are completed.
- the processor may be a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), or the like. Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
- the methods, steps, and logical block diagrams disclosed in the embodiments of the present application can be implemented or executed.
- the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
- the steps of the method disclosed in the embodiments of the present application may be directly implemented by the hardware decoding processor, or may be performed by a combination of hardware and software modules in the decoding processor.
- the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
- the storage medium is located in the memory, and the processor reads the information in the memory and combines the hardware to complete the steps of the above method.
- the apparatus 400 of the embodiments of the present application may further include a memory, which may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
- the non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory.
- the volatile memory can be a Random Access Memory (RAM) that acts as an external cache.
- RAM random access memory
- SRAM static random access memory
- DRAM dynamic random access memory
- Synchronous DRAM synchronous dynamic random access memory
- SDRAM Double Data Rate SDRAM
- DDR SDRAM Double Data Rate SDRAM
- ESDRAM Enhanced Synchronous Dynamic Random Access Memory
- SLDRAM Synchronous Connection Dynamic Random Access Memory
- DR RAM direct memory bus random access memory
- the embodiment of the present application further provides a computer readable storage medium storing one or more programs, the one or more programs including instructions, when the portable electronic device is included in a plurality of applications When executed, the portable electronic device can be caused to perform the method of the embodiment shown in FIG. 1 or 2.
- the embodiment of the present application also proposes a computer program comprising instructions which, when executed by a computer, cause the computer to perform the method of the embodiment shown in FIG. 1 or 2.
- the embodiment of the present application further provides a chip, the chip includes an input and output interface, at least one processor, at least one memory, and a bus, the at least one memory is configured to store an instruction, and the at least one processor is configured to invoke the at least one memory
- the instructions are executed to perform the method of the embodiment shown in FIG. 1 or 2.
- the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
- the implementation process constitutes any limitation.
- the disclosed systems, devices, and methods may be implemented in other manners.
- the device embodiments described above are merely illustrative.
- the division of the unit is only a logical function division.
- there may be another division manner for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed.
- the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.
- the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.
- each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated in one unit. In the unit.
- the functions may be stored in a computer readable storage medium if implemented in the form of a software functional unit and sold or used as a standalone product. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, or a part of the technical solution, may be embodied in the form of a software product stored in a storage medium. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in various embodiments of the present application.
- the foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .
Abstract
一种测试软件的方法和装置，该方法包括：依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，所述每个功能组件的参考性能信息为运行所述每个功能组件时的软件状态信息，其中，所述多个功能组件中包括第一功能组件（S110）；依次运行多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，所述每个功能组件组合的集成性能信息为运行所述每个功能组件组合时的软件状态信息，所述每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，其中，所述多个功能组件组合中包括第一功能组件组合（S120）；根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能（S130）。
Description
本申请涉及软件测试领域，并且更具体地，涉及一种测试软件的方法和装置。
随着软件产业的发展，软件产品的质量逐渐成为各企业和用户关注的焦点，对软件产品进行测试是质量控制的一个重要手段。集成测试是软件测试的一种，通过对软件产品的各个组件的聚合形式进行验证，从而识别局部反映不出来而在全局上存在的缺陷和不足。
集成测试的测试结果通常是以功能达成情况和某个综合性能参数是否在要求范围内作为评判依据，这样，可能导致一些性能偏离、累计误差等问题遗留在软件产品中，在后期发现软件产品的功能输出或性能参数不达标时，再进行问题分析回溯和修改再验证，拉长了开发周期，降低了开发效率。
发明内容
本申请实施例提供了一种测试软件的方法和装置，能够缩短开发周期，提升开发效率。
第一方面，提供了一种测试软件的方法，包括：
依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，所述每个功能组件的参考性能信息为运行所述每个功能组件时的软件状态信息，其中，所述多个功能组件中包括第一功能组件；
依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，所述每个功能组件组合的集成性能信息为运行所述每个功能组件组合时的软件状态信息，所述每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，其中，所述多个功能组件组合中包括第一功能组件组合；
根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能。
因此，本申请实施例的测试软件的方法，可以将单独运行每个功能组件的软件状态信息作为每个功能组件对应的参考性能信息，然后将待测试软件的多个功能组件进行交叉组合测试，得到每个功能组件组合的集成性能信息，进一步可以根据每个功能组件组合的集成性能信息和该每个功能组件组合对应的功能组件的参考性能信息，确定集成测试是否影响待测试软件的性能，从而能够提前发现软件集成测试时可能出现的问题，进而可以对可能存在问题的功能组件进行分析修改和再验证，有利于避免将潜在问题引入到软件集成测试阶段。
结合第一方面，在第一方面的某些实现方式中，所述依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，包括：
多次运行所述第一功能组件，根据多次运行所述第一功能组件时的软件状态信息，确定所述第一功能组件的参考性能信息。
结合第一方面，在第一方面的某些实现方式中，当单独运行所述第一功能组件时，使能所述第一功能组件，同时去使能所述多个功能组件中的其他功能组件。
结合第一方面，在第一方面的某些实现方式中，所述依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，包括：
多次运行所述第一功能组件组合，根据多次运行所述第一功能组件组合时的软件状态信息，确定所述第一功能组件组合的集成性能信息。
结合第一方面，在第一方面的某些实现方式中，当运行所述第一功能组件组合时，使能所述第一功能组件组合对应的至少两个功能组件，去使能所述多个功能组件中除所述第一功能组件组合以外的其他功能组件。
结合第一方面，在第一方面的某些实现方式中，所述根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能，包括：
若所述第一功能组件组合的集成性能信息和所述第一功能组件组合对应的至少两个功能组件中的每个功能组件的参考性能信息的差值均低于对应的阈值，确定所述第一功能组件组合未引起所述待测试软件性能的下降。
结合第一方面，在第一方面的某些实现方式中，在满足以下条件时，确
定所述第一功能组件组合未引起所述待测试软件性能的下降：
所述第一功能组件组合的集成性能信息的平均值和所述至少两个功能组件中的每个功能组件的参考性能信息的平均值的差值小于或等于第一阈值，所述第一功能组件组合的集成性能信息的最大值和所述至少两个功能组件中的每个功能组件的参考性能信息的最大值的差值小于或等于第二阈值，并且所述第一功能组件组合的集成性能信息的最小值和所述至少两个功能组件中的每个功能组件的参考性能信息的最小值的差值小于或等于第三阈值。
结合第一方面，在第一方面的某些实现方式中，所述软件状态信息包括中央处理器CPU占用率、内存使用量和运行耗时中的至少一项。
结合第一方面，在第一方面的某些实现方式中，所述方法还包括：
确定集成测试组合列表，所述集成测试组合列表包括所述多个功能组件组合。
结合第一方面，在第一方面的某些实现方式中，所述确定集成测试组合列表，包括：
将所述多个功能组件中的任意两个组件进行组合得到所述集成测试组合列表；
或将所述多个功能组件中的任意三个组件进行组合得到所述集成测试组合列表；
或采用正交设计法将所述多个功能组件进行组合得到所述集成测试组合列表。
第二方面，提供了一种测试软件的装置，所述装置包括用于执行上述第一方面或第一方面的任一可能的实现方式中的方法的功能模块。
第三方面，提供了一种芯片，该芯片包括输入输出接口、至少一个处理器、至少一个存储器和总线，该至少一个存储器用于存储指令，该至少一个处理器用于调用该至少一个存储器中的指令，以执行第一方面或第一方面的任一可能的实现方式中的方法。
第四方面，提供了一种计算机可读介质，用于存储计算机程序，所述计算机程序包括用于执行上述第一方面或第一方面的任一可能的实现方式中的指令。
第五方面，提供了一种包括指令的计算机程序产品，当计算机运行所述
计算机程序产品的所述指时，所述计算机执行上述第一方面或第一方面的任一可能的实现方式中的测试软件的方法。
图1是根据本申请一实施例的测试软件的方法的示意性流程图。
图2是根据本申请另一实施例的测试软件的方法的流程图。
图3是根据本申请实施例的测试软件的装置的示意性框图。
图4是根据本申请另一实施例的测试软件的装置的示意性框图。
下面将结合附图，对本申请实施例中的技术方案进行描述。
图1是根据本申请实施例的测试软件的方法的示意性流程图，如图1所示，该方法100包括：
S110，依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，所述每个功能组件的参考性能信息为运行所述每个功能组件时的软件状态信息，其中，所述多个功能组件中包括第一功能组件。
具体地，待测试软件可以包括多个功能组件，或者说，所述待测试软件是多个功能组件的组合，在本申请实施例中，可以依次单独运行每个功能组件，确定单独运行每个功能组件时的软件状态信息。例如，在单独运行每个功能组件时，可以通过系统监控的方式获取单独运行每个功能组件时的软件状态信息，例如，CPU使用率、内存使用量和运行耗时等信息。
可选地，若所述多个功能组件包括第一功能组件，在需要单独运行所述第一功能组件时，使能所述第一功能组件，同时去使能(disable)所述多个功能组件中的其他功能组件，然后单独运行该第一功能组件，获取单独运行所述第一功能组件的软件状态信息。
在本申请实施例中，单独运行所述每个功能组件时的软件状态信息可以作为所述每个功能组件的参考性能信息(或者也可以称为参考水平值)，在将每个功能组件与其他一个或多个功能组件进行集成测试时，可以将集成测试时的软件状态信息和该功能组件的参考性能信息进行对比，确定该功能组件与其他功能组件的集成测试是否引起待测试软件性能的下降，或者说，该
功能组件与其他功能组件的组合是否影响待测试软件的性能。
例如，该待测试软件为指纹模组测试软件，所述指纹模组测试软件可以包括模组工作模式电流检测组件、模组静态耗电电流检测组件、模组引脚开短路状态检测组件和模组厚度检测组件。在S110中，可以依次运行上述四个功能组件，确定单独运行每个功能组件时的软件状态信息，将单独运行每个功能组件时的软件状态信息作为所述每个功能组件的参考性能信息。可选地，每个功能组件的参考性能信息可以包括单独运行所述每个功能组件时的CPU占用率、内存使用量和运行耗时中的至少一项。
可选地，作为一个实施例，若所述多个功能组件包括第一功能组件，S110可以具体包括：
多次运行所述第一功能组件，根据多次运行所述第一功能组件时的软件状态信息，确定所述第一功能组件的参考性能信息。
也就是说，可以多次运行所述多个功能组件中的每个功能组件，根据多次运行所述每个功能组件时的软件状态信息，确定所述每个功能组件的参考性能信息。具体地，可以对获取的多次运行所述第一功能组件的软件状态信息进行数据处理，例如，可以去除其中的异常值，进一步地，还可以获取多次运行所述第一功能组件的软件状态信息中的平均值、最大值或最小值，将获取的多次运行所述第一功能组件得到的软件状态信息中的平均值、最大值或最小值，确定为所述第一功能组件的参考性能信息，也就是说，第一功能组件的参考性能信息可以包括多次运行所述第一软组件得到的软件状态信息中的平均值、最大值和最小值中的至少一项，这样，所述第一功能组件的参考性能信息为具有统计意义的性能信息。
可选地，若所述软件状态信息包括CPU占用率、内存使用量和运行耗时，所述第一功能组件的参考性能信息可以包括单独运行所述第一功能组件时CPU占用率对应的参考水平值、内存使用量对应的参考水平值和运行耗时对应的参考水平值。可选地，CPU占用率对应的参考水平值可以包括多次运行所述第一功能组件得到的CPU占用率中的平均值、最大值和最小值中的至少一项，对于内存使用量和运行耗时对应的参考水平值类似，这里不再赘述。
可选地，在S110中，还可以根据所述每个功能组件的软件状态信息，确定所述每个功能组件的性能是否达标，例如，每个功能组件可以对应相应
的性能范围，可以在每个功能组件的软件状态信息在对应的性能范围内时，确定所述每个功能组件的性能达标，否则，确定功能组件的性能不达标，若功能组件的性能不达标，则需要对该功能组件进行问题分析、修改和再测试，直到该功能组件的性能达标。
可选地，在S110中，还可以确定每个功能组件的功能输出信息，所述每个功能组件的功能输出信息可以用于确定所述每个功能组件的功能达成情况。应理解，在本申请实施例中，每个功能组件的参考性能信息是该功能组件的性能达标以及功能达标的情况下的软件状态信息，若某个功能组件的性能和/或功能不达标，则需要对该功能组件进行问题分析、修改和再测试，直至该功能组件的性能和功能达标，在该功能组件的功能和性能达标的情况下获取的软件状态信息才可以作为该功能组件的参考性能信息。也就是说，在所述每个功能组件的功能和性能都达标的情况下，进一步执行S120和S130的后续流程，否则需要对不达标的功能组件进行问题分析和修改，以免将潜在问题引入集成测试中。
S120，依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，所述每个功能组件组合的集成性能信息为运行所述每个功能组件组合时的软件状态信息，所述每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，其中，所述多个功能组件组合中包括第一功能组件组合。
在本申请实施例中，可以根据所述待测试软件包括的多个功能组件得到多个功能组件组合，每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，或者说，每个功能组件组合对应至少两个功能组件。可选地，可以采用两两组合，或三三组合，或正交设计法，或均匀设计法等方式将所述多个功能组件进行组合得到所述多个功能组件组合，本申请实施例对于所述多个功能组件的组合方式不作限定。确定所述多个功能组件组合之后，可以依次运行所述多个功能组件组合中的每个功能组件组合，获取运行每个功能组件组合的集成性能信息(或者也可以称为集成水平值)。
应理解，运行某个功能组件组合指的是同时运行该功能组件组合对应的至少两个功能组件。具体地，在需要运行所述多个功能组件组合中的第一功能组件组合时，使能所述第一功能组件组合对应的至少两个功能组件，去使能(disable)所述多个功能组件中除所述第一功能组件组合以外的其他功能
组件，然后运行所述第一功能组件组合对应的至少两个功能组件，获取运行所述第一功能组件组合时的软件状态信息，并将其作为所述第一功能组件组合的集成性能信息，即该第一功能组件组合为同时运行所述第一功能组件组合对应的至少两个功能组件时的软件状态信息。
可选地，在一个实施例中，S120可以具体包括：
多次运行所述第一功能组件组合，根据多次运行所述第一功能组件组合时的软件状态信息，确定所述第一功能组件组合的集成性能信息。
也就是说，可以多次运行所述多个功能组件组合中的每个功能组件组合，根据多次运行所述每个功能组件组合时的软件状态信息，确定所述每个功能组件组合的集成性能信息。具体地，可以对获取的多次运行所述第一功能组件组合的软件状态信息进行数据处理，例如，可以去除其中的异常值，进一步地，可以获取多次运行所述第一功能组件组合得到的软件状态信息中的平均值、最大值或最小值，将获取的多次运行所述第一功能组件组合得到的软件状态信息中的平均值、最大值或最小值，确定为所述第一功能组件组合的集成性能信息。也就是说，第一功能组件组合的集成性能信息可以包括多次运行所述第一软组件组合的软件状态信息中的平均值、最大值和最小值中的至少一项，这样，所述第一功能组件组合的集成性能信息为具有统计意义的性能信息。
跟前述实施例类似，若所述软件状态信息包括CPU占用率、内存使用量和运行耗时，所述第一功能组件组合的集成性能信息可以包括运行所述第一功能组件组合时CPU占用率对应的集成水平值、内存使用量对应的集成水平值和运行耗时对应的集成水平值。例如，CPU占用率对应的集成水平值可以为多次运行所述第一功能组件组合得到的软件状态信息中的平均值、最大值和最小值中的至少一项，同样地，对于所述内存使用量和运行耗时对应的集成水平值亦是如此，这里不再赘述。
S130，根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能。
具体地，可以根据每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述每个功能组件组合是否引起待测试软件性能的下降，也就是说，功能组件的集成测试(或者
说，组合测试)是否会影响待测试软件的性能。可选地，可以根据每个功能组件组合对应的至少两个功能组件中的每个功能组件的参考性能信息和所述每个功能组件组合的集成性能信息的差值，确定所述每个功能组件组合是否引起待测试软件的性能的下降。例如，可以在每个功能组件的参考性能信息和所述每个功能组件组合的集成性能信息的差值均低于特定阈值时，确定集成测试未引起待测试软件性能的下降。也就是说，若单独运行功能组件时的性能参数和该功能组件与其他一个或多个功能组件同时运行时的性能参数的差异不大，或者说，若单独测试该功能组件和集成测试该功能组件和其他功能组件时的软件状态的差异不大，可以确定集成测试未引起待测试软件性能的下降。
应理解，功能组件组合未引起待测试软件的性能的下降可以认为该功能组件组合的性能达标，否则，认为该功能组件组合不达标。若多个功能组件组合中的部分功能组件组合的性能达标，其他功能组件组合的性能不达标，在S130中，还可以根据达标和不达标的功能组件的组合情况，提前进行问题的分析追溯以及修改再验证，确定有可能导致集成测试不达标的功能组件，即可能存在问题的功能组件，从而可以提前发现问题，以免将问题带入到整个待测试软件的集成测试阶段，增加问题排查的难度和时间，导致开发周期的拉长。
可选地，在本申请实施例中，可以在满足以下条件时，确定所述第一功能组件组合未引起所述待测试软件性能的下降：
所述第一功能组件组合的集成性能信息的平均值和所述至少两个功能组件中的每个功能组件的参考性能信息的平均值的差值小于或等于第一阈值，所述第一功能组件组合的集成性能信息的最大值和所述至少两个功能组件中的每个功能组件的参考性能信息的最大值的差值小于或等于第二阈值，并且所述第一功能组件组合的集成性能信息的最小值和所述至少两个功能组件中的每个功能组件的参考性能信息的最小值的差值小于或等于第三阈值。
其中，所述第一阈值、第二阈值和第三阈值可以根据工程经验或用户需求等进行设置。
可选地，在本申请实施例中，可以在每个功能组件组合的集成测试都未引起待测试软件的性能的下降的情况下，确定软件集成测试未引起待测试软
件的性能的下降，每个功能组件组合对应的用于确定是否引起待测试软件性能下降的第一阈值、第二阈值和第三阈值可以相同，也可以不同，也就是说，不同的功能组件组合可以对应相应的性能范围，即不同的功能组件组合可以对应不同的性能范围，也可以对应相同的性能范围。不同的参考性能信息也可以对应相应的性能范围，或者说，不同的参考性能信息可以对应相应的阈值，例如，CPU占用率、内存使用量和运行耗时等都可以对应相应的阈值范围，例如，CPU占用率对应的阈值可以为50％，内存使用量对应的阈值可以为1M，运行耗时对应的阈值可以为10min。
因此，本申请实施例的测试软件的方法，可以将单独运行每个功能组件的软件状态信息作为每个功能组件对应的参考性能信息，然后将待测试软件的多个功能组件进行交叉组合测试，得到每个功能组件组合的集成性能信息，进一步可以根据每个功能组件组合的集成性能信息和该每个功能组件组合对应的功能组件的参考性能信息，确定集成测试是否影响待测试软件的性能，从而能够提前发现软件集成测试时可能出现的问题，进而可以对可能存在问题的功能组件进行分析修改和再验证，有利于避免将潜在问题引入到软件集成测试阶段。
例如，若第一功能组件组合为所述第一功能组件和第二功能组件的组合，即第一功能组件组合对应第一功能组件和第二功能组件，在S110中，可以获取单独运行所述第一功能组件的参考性能信息和单独运行所述第二功能组件的参考性能信息，所述第一功能组件的参考性能信息可以为多次单独运行所述第一功能组件得到的软件状态信息的平均值、最大值或最小值，所述第二功能组件的参考性能信息可以为多次单独运行所述第二功能组件得到的软件状态信息的平均值、最大值或最小值。
在S120中，可以同时运行第一功能组件和第二功能组件(除第一功能组件和第二功能组件以外的其他功能组件处于去使能状态)，获取运行第一功能组件组合时的集成性能信息，该第一功能组件组合的集成性能信息可以为多次运行所述第一功能组件组合时得到的软件状态信息中的平均值、最大值或最小值。
进一步地，在S130中，根据第一功能组件和第二功能组件的参考性能信息与所述第一功能组件组合的集成性能信息的差值，确定第一功能组合和所述第二功能组件的组合测试是否引起待测试软件性能的下降。例如，可以
在第一功能组件的参考性能信息和所述第一功能组件组合的集成性能信息的差值低于第一预设阈值，以及第二功能组件的参考性能信息和所述第一功能组件组合的集成性能信息的差值低于第二预设阈值的情况下，确定组合测试未引起待测试软件性能的下降，其中，第一预设阈值和所述第二预设阈值可以相等，也可以不相等，本申请实施例对此不作具体限定。
以下，结合图2所示的具体示例，详细说明根据本申请另一实施例的测试软件的方法，如图2所示，该方法20包括如下内容：
S21，使能单一功能组件。
例如，待测试软件为指纹模组测试软件，该指纹模组测试软件可以包括模组工作模式电流检测组件(记为A组件)、模组静态耗电电流检测组件(记为B组件)、模组引脚开短路状态检测组件(记为C组件)和模组厚度检测组件(记为D组件)。可选地，可以按照A组件、B组件、C组件和D组件的顺序依次运行上述四个功能组件，具体地，在运行A组件时，使能A组件，去使能B组件、C组件和D组件。
进一步地，在S22中，运行已使能的功能组件，获取运行该功能组件的性能参数(对应于上文的软件状态信息)，将该性能参数作为该功能组件对应的参考性能参数(对应于上文的参考性能信息)，即参考水平值。
在S23中，判断是否所有的功能组件都已遍历完毕，也就是说，每个功能组件是否都单独执行完毕，并获取到每个功能组件的参考水平值。
若未遍历完毕，流程进行到S21，否则，流程进行到S24。
在S24中，根据集成测试组合列表，使能集成测试组合列表中的功能组件组合。
具体地，集成测试组合列表可以包括多个功能组件组合，例如，可以采用两两组合、三三组合、正交设计法或均匀设计法等进行组合，得到所述集成测试组合列表。对于前述的指纹模组测试软件，以两两组合为例，该集成测试组合列表包括如下组合：A组件+B组件，A组件+C组件，A组件+D组件，B组件+C组件，B组件+D组件，C组件+D组件。
或者，若采用正交设计法确定所述指纹模组测试软件对应的集成测试组合列表，首先根据该指纹模组测试软件包括的功能组件的个数，确定选择正交表L8(27)，如表1所示。
表1
其中，1表示使能对应的功能组件，2表示去使能(disable)对应的功能组件。
对于指纹模组测试组件包括4个功能组件，可以将表1中的多余列删除得到表2，如下：
表2
根据表2可以得到包括该指纹模组测试组件对应的集成测试组合列表，从而可以根据该集成测试组合列表进行功能组件的交叉组合测试。
例如，在S24中，在需要运行A组件+B组件时，使能A组件+B组件，即同时使能A组件和B组件，去使能C组件和D组件。
进一步地，在S25中，运行已使能的功能组件组合，获取运行该功能组件组合时的集成性能参数，即集成水平值。
例如，在S24中，若同时使能了A组件和B组件，在S25中，获取运行A组件+B组件的功能组件组合时的集成性能参数。
在S26中，确定获取的功能组件组合的集成水平值和功能组件组合对应的功能组件的参考水平值之间的差异。
例如，对于A组件+B组件的功能组件组合的集成水平值，在S26中，可以对比该集成水平值和A组件的参考水平值以及B组件的参考水平值，确定该集成水平值与A组件的参考水平值之间的差异，以及该集成水平值与
B组件的参考水平值之间的差异。如上文所述，参考水平值可以为多次运行单一功能组件时的性能参数的平均值、最大值或最小值，可选地，集成水平值和A组件的参考水平值之间的差异可以为集成水平值和多次运行A组件时的性能参数的平均值之间的差值，或者，所述集成水平值和A组件的参考水平值之间的差异也可以为集成水平值和多次运行A组件时的性能参数的最大值之间的差值，或者，所述集成水平值和A组件的参考水平值之间的差异也可以为集成水平值和多次运行A组件时的性能参数的最小值之间的差值等。
在S27中，确定集成测试组合列表是否遍历完毕。
若是，则执行S28，否则，执行S24，直至集成测试软件集合列表中的每个功能组件组合都被执行完毕，并获取到每个功能组件组合的集成水平值。
在S28中，根据在S26中获取的集成水平值和参考水平值之间的差异，确定待测试软件的性能。
可选地，可以在某个功能组件组合的集成水平值和该功能组件组合对应的功能组件的参考水平值之间的差异大于预设阈值时，确定该功能组件组合影响待测试软件的性能，也就是说，该功能组件组合中的功能组件的组合测试可能会影响待测试软件的性能，这种情况下，可以根据测试结果进行分析，进一步确定问题的根源。可选地，还可以结合该功能软件组合中的功能组件在其他功能组件组合中的比较结果，判断影响待测试软件性能的根源。
具体地，若集成水平值是用平均值、最大值和最小值的方式表示的，在S26中，可以将集成水平值的平均值和参考水平值的平均值做差，将集成水平值的最大值和参考水平值的最大值做差，将集成水平值的最小值和参考水平值的最小值做差。进一步地，在S28中，判断集成水平值的平均值和参考水平值的平均值的差值的绝对值是否小于或等于第一阈值，判断集成水平值的最大值和参考水平值的最大值的差值的绝对值是否小于或等于第二阈值，以及判断集成水平值的最小值和参考水平值的最小值的差值的绝对值是否小于或等于第三阈值，在以上三项均满足的情况下，确定组合测试未带来软件性能的下降，即组合测试达标。
因此，本申请实施例的测试软件的方法，可以在进行待测试软件的整体集成测试之前，通过对待测试软件的多个功能组件之间的交叉组合测试，提
前确定哪些功能组件的组合可能运行待测试软件的性能，从而可以提前进行问题的分析追溯，以及修改再验证，进而能够缩短软件的开发周期，加快软件的开发进程。另一方面，本申请实施例的测试软件的方法，在某个功能组件组合的性能不达标时，即可进行问题的分析和追溯，相对于在待测试软件的整体集成测试性能不达标时，进行问题的分析和追溯，大大降低了问题的排查难度和排查时间。
上文结合图1和图2，详细描述了本申请的方法实施例，下文结合图3和图4，详细描述本申请的装置实施例，应理解，装置实施例与方法实施例相互对应，类似的描述可以参照方法实施例。
图3是根据本申请实施例的测试软件的装置300的示意性框图，如图3所示，该装置300包括：
确定模块310，用于依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，所述每个功能组件的参考性能信息为运行所述每个功能组件时的软件状态信息，其中，所述多个功能组件中包括第一功能组件；依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，所述每个功能组件组合的集成性能信息为运行所述每个功能组件组合时的软件状态信息，所述每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，其中，所述多个功能组件组合中包括第一功能组件组合；以及根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能。
可选地，在一些实施例中，所述确定模块310具体用于：
多次运行所述第一功能组件，根据多次运行所述第一功能组件时的软件状态信息，确定所述第一功能组件的参考性能信息。
可选地，在一些实施例中，当单独运行所述第一功能组件时，使能所述第一功能组件，同时去使能所述多个功能组件中的其他功能组件。
可选地，在一些实施例中，所述确定模块310具体用于：
多次运行所述第一功能组件组合，根据多次运行所述第一功能组件组合时的软件状态信息，确定所述第一功能组件组合的集成性能信息。
可选地，在一些实施例中，当运行所述第一功能组件组合时，使能所述第一功能组件组合对应的至少两个功能组件，去使能所述多个功能组件中除
所述第一功能组件组合以外的其他功能组件。
可选地，在一些实施例中，所述确定模块310具体用于：
若所述第一功能组件组合的集成性能信息和所述第一功能组件组合对应的至少两个功能组件中的每个功能组件的参考性能信息的差值均低于对应的阈值，确定所述第一功能组件组合未引起所述待测试软件性能的下降。
可选地，在一些实施例中，在满足以下条件时，确定所述第一功能组件组合未引起所述待测试软件性能的下降：
所述第一功能组件组合的集成性能信息的平均值和所述至少两个功能组件中的每个功能组件的参考性能信息的平均值的差值小于或等于第一阈值，所述第一功能组件组合的集成性能信息的最大值和所述至少两个功能组件中的每个功能组件的参考性能信息的最大值的差值小于或等于第二阈值，并且所述第一功能组件组合的集成性能信息的最小值和所述至少两个功能组件中的每个功能组件的参考性能信息的最小值的差值小于或等于第三阈值。
可选地，在一些实施例中，所述软件状态信息包括中央处理器CPU占用率、内存使用量和运行耗时中的至少一项。
可选地，在一些实施例中，所述确定模块310还用于：
确定集成测试组合列表，所述集成测试组合列表包括所述多个功能组件组合。
可选地，在一些实施例中，所述确定模块310具体用于：
将所述多个功能组件中的任意两个组件进行组合得到所述集成测试组合列表；或
将所述多个功能组件中的任意三个组件进行组合得到所述集成测试组合列表；
或采用正交设计法将所述多个功能组件进行组合得到所述集成测试组合列表。
如图4所示，本申请实施例还提供了一种测试软件的装置400，该装置400可以用作图3所示的测试软件的装置300，其能够用于执行与图1或图2中的方法的具体内容。具体地，该装置400包括：处理器410。
应理解，本申请实施例的处理器410可以是一种集成电路芯片，具有信号的处理能力。在实现过程中，上述方法实施例的各步骤可以通过处理器中
的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成，或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器读取存储器中的信息，结合其硬件完成上述方法的步骤。
可以理解，本申请实施例的装置400还可以包括存储器，存储器可以是易失性存储器或非易失性存储器，或可包括易失性和非易失性存储器两者。其中，非易失性存储器可以是只读存储器(Read-Only Memory，ROM)、可编程只读存储器(Programmable ROM，PROM)、可擦除可编程只读存储器(Erasable PROM，EPROM)、电可擦除可编程只读存储器(Electrically EPROM，EEPROM)或闪存。易失性存储器可以是随机存取存储器(Random Access Memory，RAM)，其用作外部高速缓存。通过示例性但不是限制性说明，许多形式的RAM可用，例如静态随机存取存储器(Static RAM，SRAM)、动态随机存取存储器(Dynamic RAM，DRAM)、同步动态随机存取存储器(Synchronous DRAM，SDRAM)、双倍数据速率同步动态随机存取存储器(Double Data Rate SDRAM，DDR SDRAM)、增强型同步动态随机存取存储器(Enhanced SDRAM，ESDRAM)、同步连接动态随机存取存储器(Synchlink DRAM，SLDRAM)和直接内存总线随机存取存储器(Direct Rambus RAM，DR RAM)。应注意，本文描述的系统和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
本申请实施例还提出了一种计算机可读存储介质，该计算机可读存储介质存储一个或多个程序，该一个或多个程序包括指令，该指令当被包括多个应用程序的便携式电子设备执行时，能够使该便携式电子设备执行图1或图2所示实施例的方法。
本申请实施例还提出了一种计算机程序，该计算机程序包括指令，当该计算机程序被计算机执行时，使得计算机可以执行图1或图2所示实施例的方法。
本申请实施例还提供了一种芯片，该芯片包括输入输出接口、至少一个处理器、至少一个存储器和总线，该至少一个存储器用于存储指令，该至少一个处理器用于调用该至少一个存储器中的指令，以执行图1或图2所示实施例的方法。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应所述理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一
个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者所述技术方案的部分可以以软件产品的形式体现出来，所述计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应所述以权利要求的保护范围为准。
Claims (20)
- 一种测试软件的方法，其特征在于，包括：依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，所述每个功能组件的参考性能信息为单独运行所述每个功能组件时的软件状态信息，其中，所述多个功能组件中包括第一功能组件；依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，所述每个功能组件组合的集成性能信息为运行所述每个功能组件组合时的软件状态信息，所述每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，其中，所述多个功能组件组合中包括第一功能组件组合；根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能。
- 根据权利要求1所述的方法，其特征在于，所述依次单独运行待测试软件包括的多个功能组件中的每个功能组件，确定所述每个功能组件的参考性能信息，包括：多次运行所述第一功能组件，根据多次运行所述第一功能组件时的软件状态信息，确定所述第一功能组件的参考性能信息。
- 根据权利要求1或2所述的方法，其特征在于，当单独运行所述第一功能组件时，使能所述第一功能组件，同时去使能所述多个功能组件中的其他功能组件。
- 根据权利要求1至3中任一项所述的方法，其特征在于，所述依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，包括：多次运行所述第一功能组件组合，根据多次运行所述第一功能组件组合时的软件状态信息，确定所述第一功能组件组合的集成性能信息。
- 根据权利要求1至4中任一项所述的方法，其特征在于，当运行所述第一功能组件组合时，使能所述第一功能组件组合对应的至少两个功能组件，去使能所述多个功能组件中除所述第一功能组件组合以外的其他功能组件。
- 根据权利要求1至5中任一项所述的方法，其特征在于，所述根据 所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能，包括：若所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件中的每个功能组件的参考性能信息的差值均低于对应的阈值，确定集成测试未引起所述待测试软件性能的下降。
- 根据权利要求6所述的方法，其特征在于，在满足以下条件时，确定所述第一功能组件组合未引起所述待测试软件性能的下降：所述第一功能组件组合的集成性能信息的平均值和所述至少两个功能组件中的每个功能组件的参考性能信息的平均值的差值小于或等于第一阈值，所述第一功能组件组合的集成性能信息的最大值和所述至少两个功能组件中的每个功能组件的参考性能信息的最大值的差值小于或等于第二阈值，并且所述第一功能组件组合的集成性能信息的最小值和所述至少两个功能组件中的每个功能组件的参考性能信息的最小值的差值小于或等于第三阈值。
- 根据权利要求1至7中任一项所述的方法，其特征在于，所述软件状态信息包括中央处理器CPU占用率、内存使用量和运行耗时中的至少一项。
- 根据权利要求1至8中任一项所述的方法，其特征在于，所述方法还包括：确定集成测试组合列表，所述集成测试组合列表包括所述多个功能组件组合。
- 根据权利要求9所述的方法，其特征在于，所述确定集成测试组合列表，包括：将所述多个功能组件中的任意两个组件进行组合得到所述集成测试组合列表；或将所述多个功能组件中的任意三个组件进行组合得到所述集成测试组合列表；或采用正交设计法将所述多个功能组件进行组合得到所述集成测试组合列表。
- 一种测试软件的装置，其特征在于，包括：确定模块，用于依次单独运行待测试软件包括的多个功能组件中的每个 功能组件，确定所述每个功能组件的参考性能信息，所述每个功能组件的参考性能信息为单独运行所述每个功能组件时的软件状态信息，其中，所述多个功能组件中包括第一功能组件；依次运行所述待测试软件的多个功能组件组合中的每个功能组件组合，确定所述每个功能组件组合的集成性能信息，所述每个功能组件组合的集成性能信息为运行所述每个功能组件组合时的软件状态信息，所述每个功能组件组合为所述多个功能组件中的至少两个功能组件的组合，其中，所述多个功能组件组合中包括第一功能组件组合；以及根据所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件的参考性能信息，确定所述待测试软件的性能。
- 根据权利要求11所述的装置，其特征在于，所述确定模块具体用于：多次运行所述第一功能组件，根据多次运行所述第一功能组件时的软件状态信息，确定所述第一功能组件的参考性能信息。
- 根据权利要求11或12所述的装置，其特征在于，当单独运行所述第一功能组件时，使能所述第一功能组件，同时去使能所述多个功能组件中的其他功能组件。
- 根据权利要求11至13中任一项所述的装置，其特征在于，所述确定模块具体用于：多次运行所述第一功能组件组合，根据多次运行所述第一功能组件组合时的软件状态信息，确定所述第一功能组件组合的集成性能信息。
- 根据权利要求11至14中任一项所述的装置，其特征在于，当运行所述第一功能组件组合时，使能所述第一功能组件组合对应的至少两个功能组件，去使能所述多个功能组件中除所述第一功能组件组合以外的其他功能组件。
- 根据权利要求11至15中任一项所述的装置，其特征在于，所述确定模块具体用于：若所述每个功能组件组合的集成性能信息和所述每个功能组件组合对应的至少两个功能组件中的每个功能组件的参考性能信息的差值均低于对应的阈值，确定集成测试未引起所述待测试软件性能的下降。
- 根据权利要求16所述的装置，其特征在于，在满足以下条件时，确定所述第一功能组件组合未引起所述待测试软件性能的下降：所述第一功能组件组合的集成性能信息的平均值和所述至少两个功能组件中的每个功能组件的参考性能信息的平均值的差值小于或等于第一阈值，所述第一功能组件组合的集成性能信息的最大值和所述至少两个功能组件中的每个功能组件的参考性能信息的最大值的差值小于或等于第二阈值，并且所述第一功能组件组合的集成性能信息的最小值和所述至少两个功能组件中的每个功能组件的参考性能信息的最小值的差值小于或等于第三阈值。
- 根据权利要求11至17中任一项所述的装置，其特征在于，所述软件状态信息包括中央处理器CPU占用率、内存使用量和运行耗时中的至少一项。
- 根据权利要求11至18中任一项所述的装置，其特征在于，所述确定模块还用于：确定集成测试组合列表，所述集成测试组合列表包括所述多个功能组件组合。
- 根据权利要求19所述的装置，其特征在于，所述确定模块还用于：将所述多个功能组件中的任意两个组件进行组合得到所述集成测试组合列表；或将所述多个功能组件中的任意三个组件进行组合得到所述集成测试组合列表；或采用正交设计法将所述多个功能组件进行组合得到所述集成测试组合列表。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201780001584.6A CN110023913A (zh) | 2017-11-02 | 2017-11-02 | 测试软件的方法和装置 |
| PCT/CN2017/109062 WO2019084861A1 (zh) | 2017-11-02 | 2017-11-02 | 测试软件的方法和装置 |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2017/109062 WO2019084861A1 (zh) | 2017-11-02 | 2017-11-02 | 测试软件的方法和装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2019084861A1 true WO2019084861A1 (zh) | 2019-05-09 |
Family
ID=66331112
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2017/109062 WO2019084861A1 (zh) | 2017-11-02 | 2017-11-02 | 测试软件的方法和装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN110023913A (zh) |
| WO (1) | WO2019084861A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112596815A (zh) * | 2020-12-25 | 2021-04-02 | 青岛海尔科技有限公司 | 功能组件的生成方法和装置、存储介质及电子装置 |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050096867A1 (en) * | 2003-11-03 | 2005-05-05 | Microsoft Corporation | Flexible variable and execution matrix |
| CN1744054A (zh) * | 2004-08-31 | 2006-03-08 | 中国银联股份有限公司 | 一种自动化测试辅助系统及相应的软件自动测试方法 |
| CN101645012A (zh) * | 2009-09-11 | 2010-02-10 | 兰雨晴 | 基础软件平台集成测试的组合选择方法 |
| CN104199779A (zh) * | 2014-09-24 | 2014-12-10 | 福建联迪商用设备有限公司 | 一种嵌入式模块组合测试的方法及系统 |
| CN105808427A (zh) * | 2016-03-02 | 2016-07-27 | 厦门美图移动科技有限公司 | 一种移动终端软件测试方法、装置和系统 |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR101008959B1 (ko) * | 2008-09-12 | 2011-01-17 | 성균관대학교산학협력단 | 로봇 소프트웨어 컴포넌트의 계층별 테스트방법 |
| CN103019900B (zh) * | 2012-12-04 | 2016-10-26 | 北京奇虎科技有限公司 | 终端性能的检测结果显示方法和装置 |
| CN103217556B (zh) * | 2013-04-22 | 2018-02-13 | 南京同尔电子科技有限公司 | 一种电子模块功能测试系统 |
-
2017
- 2017-11-02 CN CN201780001584.6A patent/CN110023913A/zh active Pending
- 2017-11-02 WO PCT/CN2017/109062 patent/WO2019084861A1/zh active Application Filing
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050096867A1 (en) * | 2003-11-03 | 2005-05-05 | Microsoft Corporation | Flexible variable and execution matrix |
| CN1744054A (zh) * | 2004-08-31 | 2006-03-08 | 中国银联股份有限公司 | 一种自动化测试辅助系统及相应的软件自动测试方法 |
| CN101645012A (zh) * | 2009-09-11 | 2010-02-10 | 兰雨晴 | 基础软件平台集成测试的组合选择方法 |
| CN104199779A (zh) * | 2014-09-24 | 2014-12-10 | 福建联迪商用设备有限公司 | 一种嵌入式模块组合测试的方法及系统 |
| CN105808427A (zh) * | 2016-03-02 | 2016-07-27 | 厦门美图移动科技有限公司 | 一种移动终端软件测试方法、装置和系统 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112596815A (zh) * | 2020-12-25 | 2021-04-02 | 青岛海尔科技有限公司 | 功能组件的生成方法和装置、存储介质及电子装置 |
| CN112596815B (zh) * | 2020-12-25 | 2023-02-03 | 青岛海尔科技有限公司 | 功能组件的生成方法和装置、存储介质及电子装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110023913A (zh) | 2019-07-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP6804668B2 (ja) | ブロックデータ検証方法および装置 | |
| TWI703455B (zh) | 確定資料異常的方法和裝置 | |
| WO2016106605A1 (zh) | 一种fpga功能模块仿真验证方法及其系统 | |
| US20180183577A1 (en) | Techniques for secure message authentication with unified hardware acceleration | |
| CN108388509B (zh) | 一种软件测试方法、计算机可读存储介质及终端设备 | |
| US11366757B2 (en) | File pre-fetch scheduling for cache memory to reduce latency | |
| US20200026427A1 (en) | System and method for handling data storage on storage devices | |
| WO2018149138A1 (zh) | 无线保真Wi-Fi连接方法及相关产品 | |
| CN110688168A (zh) | 提高应用程序启动速度方法、装置、设备及存储介质 | |
| CN111708931B (zh) | 基于移动互联网的大数据采集方法及人工智能云服务平台 | |
| CN104283736B (zh) | 一种基于改良自动状态机的网络通信五元组快速匹配算法 | |
| WO2019084861A1 (zh) | 测试软件的方法和装置 | |
| US20210250260A1 (en) | Detection device and detection method | |
| US20140359365A1 (en) | Integrated Configuration Management and Monitoring for Computer Systems | |
| US11582041B2 (en) | Electronic device and control method thereof | |
| US20220005004A1 (en) | Method and device for blockchain transaction tracing | |
| US9965374B2 (en) | Profile guided indirect function call check for control flow integrity | |
| WO2019091443A1 (zh) | 一种基于神经网络的调整方法、装置及设备 | |
| CN105740073A (zh) | 一种动态控制操作系统进程数量的方法及装置 | |
| CN113282476B (zh) | 接口性能测试方法、装置和电子设备 | |
| US11500825B2 (en) | Techniques for dynamic database access modes | |
| US10691249B2 (en) | Touch host controller | |
| CN112506565A (zh) | 处理器微体系结构事件的重要性确定方法、介质和设备 | |
| US8839159B2 (en) | Determining overall optimal yield point for a semiconductor wafer | |
| US11593318B2 (en) | Techniques for asynchronous snapshot invalidation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17930361 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 17930361 Country of ref document: EP Kind code of ref document: A1 |