A multi-mode mobile terminal data isolation automatic testing method

Abstract

The application relates to the technical field of data processing, in particular to a kind of automatic test method based on multi-mode mobile terminal data isolation, which comprises: installing test program in each mode environment of the mobile terminal to be tested;According to the execution time length of the test program in the execution process and the occupancy rate of hardware in the method execution process, the blocking parameter of the method is determined;Based on the blocking parameter of each method in the test operation of the mobile terminal to be tested, the operation effectiveness of the test operation in the execution process is determined;According to the operation effectiveness of each test operation, the effective operation segment is determined, the effective operation segment includes at least one test operation, and each mode environment is tested based on the effective operation segment. The application improves the accuracy of the test result of multi-mode mobile terminal data isolation.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and more specifically to an automated testing method for data isolation of multi-mode mobile terminals. Background Technology

[0002] With the deep penetration of mobile terminals in sensitive fields such as finance, government affairs, and healthcare, data isolation has become a core technical support for ensuring information security. Currently, industry testing practices for mobile terminal data isolation still largely rely on manual testing methods, which have significant shortcomings in terms of technical implementation and team adaptation. In terms of technical barriers, testers need to be proficient in cross-process data tracing, test environment setup, and even have basic programming skills to handle complex test data. In terms of process efficiency, test preparation involves tedious steps such as device environment configuration and test dataset construction, and requires repeated adaptation for different terminal models, resulting in lengthy testing cycles. Furthermore, in fields with stringent information security requirements such as finance and defense, customized mobile devices have achieved dual-mode or multi-mode deployment ("work-life"), using system-level partitioning technology to achieve physical isolation between sensitive office data and personal data. The testing requirements for such devices have upgraded from data isolation verification within a single mode to cross-isolation testing between multiple modes, with the core focus on verifying data boundary security in scenarios such as mode switching, process communication, and external interface calls.

[0003] In some scenarios, the traditional approach involves scanning process data in different modes and using feature matching to determine data leakage. This involves pre-setting sensitive data signatures; if the same signature data is detected in an unauthorized mode, isolation is deemed invalid. While this approach improves detection efficiency, it still falls short in terms of the completeness of functional logic coverage. This is because multi-mode isolation in mobile terminals relies on complex process scheduling, permission verification, and resource allocation logic, and the sequence of different functions directly affects the completeness of event generation. Existing technologies lack dynamic control over the timing of function calls. For example, in a continuous operation of "mode switching - file transfer - background cleanup," deviations in the timing of test steps can easily lead to omissions in detecting implicit data transfer between processes, resulting in low accuracy of multi-mode mobile terminal data isolation test results. Summary of the Invention

[0004] To address the technical problem of low accuracy in test results for multi-mode mobile terminal data isolation, the present invention aims to provide an automated testing method based on multi-mode mobile terminal data isolation.

[0005] To solve the above technical problems, the specific technical solution adopted is as follows:

[0006] In a first aspect, embodiments of the present invention provide an automated testing method for data isolation of a multi-mode mobile terminal, comprising: installing a test program in each mode environment of the mobile terminal under test; determining blocking parameters of the method based on the execution time of the test program and the hardware occupancy rate during the method execution; determining the operational validity of the test operation during the execution process based on the blocking parameters of each method in the test operation of the mobile terminal under test; determining effective operation segments based on the operational validity of each test operation, wherein each effective operation segment includes at least one test operation, and performing data isolation testing on each mode environment based on the effective operation segments.

[0007] Optionally, based on the execution duration of the test program and the hardware utilization rate during method execution, the blocking parameters of the method are determined, including: determining the execution duration of the test program and the historical average execution duration, the hardware utilization rate during method execution, the minimum hardware utilization rate, and the number of usable hardware devices in the mobile terminal under test; and determining the blocking parameters based on the execution duration, historical average execution duration, utilization rate, minimum utilization rate, and the number of usable hardware devices.

[0008] Optionally, determining the execution duration of the test program includes: adding hidden probes in each method of the test program; and using the time difference between the activation time of the hidden probe corresponding to the method and the activation time of the next hidden probe as the execution duration of the test program.

[0009] Optionally, determining the operational validity of the test operation during execution based on the blocking parameters of each method in the test operation of the mobile terminal under test includes: determining the minimum blocking parameter among the blocking parameters of each method in the test operation of the mobile terminal under test and the standard deviation of the blocking parameters of all methods in the test operation; determining the first difference between the blocking parameters of each method in the test operation and the minimum blocking parameter, and determining the first ratio between the first difference and the standard deviation; and determining the operational validity based on the first difference and the first ratio.

[0010] Optionally, determining the effective operation segment based on the operational validity of each test operation includes: sorting the operational validity of each test operation in descending order to obtain a descending validity sequence; calculating the validity difference value between adjacent operational validitys in the descending validity sequence; extracting the maximum value from each validity difference value and determining the larger of the two operational validitys corresponding to the maximum value; determining the interval between the larger value and the maximum operational validity in the descending validity sequence as the high validity interval; and merging the consecutive test operations corresponding to the operational validitys in the high validity interval to obtain the effective operation segment.

[0011] Optionally, determining the interval between the larger value and the maximum operational validity in the descending validity sequence as the high validity interval includes: using the maximum operational validity as the left endpoint of the high validity interval and the larger value as the right endpoint of the high validity interval.

[0012] Optionally, calculating the validity difference value between adjacent operations in the validity descending sequence includes: calculating the difference between the validity of the next operation and the validity of the previous operation in the validity descending sequence; and using the difference as the validity difference value.

[0013] Optionally, data isolation testing of each mode environment based on valid operation segments includes: determining the test requirements of the terminal under test; selecting target valid operation segments based on the test requirements; and using the target valid operation segments to perform data isolation testing of each mode environment.

[0014] Optionally, after performing data isolation tests on each mode environment based on valid operation segments, the method further includes: statistically analyzing the data of the test program in different mode environments of the test terminal under test, and if there is non-isolated data in any mode environment, determining that the test program's data is not isolated in different mode environments.

[0015] Optionally, when statistically analyzing the data of the test program under different mode environments of the test terminal to be tested, if non-isolated data exists in any mode environment, after determining that the test program's data is not isolated in different mode environments, the method further includes: outputting a visual table, which includes the test program and test results.

[0016] The present invention has the following beneficial effects: By installing test programs in various modes of the mobile terminal under test, the embodiments of the present invention can more comprehensively cover the complex logic such as process scheduling, permission verification, and resource allocation that mobile terminal multi-mode isolation relies on, thus making up for the deficiencies of traditional solutions in the completeness of functional logic coverage. Furthermore, the solution determines the validity of test operations by calculating blocking parameters (combining execution time and hardware utilization), thereby selecting valid operation segments for testing. This mechanism can dynamically identify and capture the valid execution process in a coherent operation, avoiding the omission of implicit data transfer detection between processes due to timing deviations in test steps, effectively solving the problem of lack of timing control in traditional solutions. Moreover, data isolation testing based on valid operation segments ensures that the testing process focuses on real and valid operation sequences, reducing the interference of invalid operations on test results, thereby significantly improving the accuracy and reliability of multi-mode mobile terminal data isolation test results. In addition, while improving test completeness and accuracy, the selection of valid operation segments avoids redundant testing of invalid operations, maintaining high test efficiency while ensuring test quality. Attached Figure Description

[0017] To more clearly illustrate the technical solutions and advantages in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 A flowchart illustrating an automated testing method for data isolation of a multi-mode mobile terminal, provided as an embodiment of the present invention;

[0019] Figure 2 This is a schematic diagram of the structure of an automated testing system for data isolation of multi-mode mobile terminals provided in an embodiment of the present invention. Detailed Implementation

[0020] To further illustrate the technical means and effects adopted by the present invention to achieve its intended purpose, the following, in conjunction with the accompanying drawings and preferred embodiments, details the specific implementation, structure, features, and effects of an automated testing method for multi-mode mobile terminal data isolation proposed according to the present invention. In the following description, different "one embodiment" or "another embodiment" do not necessarily refer to the same embodiment. Furthermore, specific features, structures, or characteristics in one or more embodiments can be combined in any suitable form.

[0021] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains.

[0022] The following description, in conjunction with the accompanying drawings, details a specific scheme for an automated testing method for data isolation of multi-mode mobile terminals provided by the present invention.

[0023] Example 1:

[0024] Please see Figure 1 The flowchart illustrates an embodiment of the automated testing method for data isolation of multi-mode mobile terminals provided by the present invention, including:

[0025] Step S101: Install the test program in each mode environment of the mobile terminal under test.

[0026] Specifically, in this embodiment of the invention, the mobile terminal under test is first connected to a controller. Then, the packaged test program is installed in each mode environment within the mobile terminal under test, and each mode environment is initialized to obtain the mobile terminal under test. The mode environments include game mode environments, work mode environments, etc. The test program refers to the application under test, such as a video application or a chat application. The purpose of the test isolation in this embodiment of the invention is to detect whether there is data leakage in each mode environment of the mobile terminal under test, thereby verifying the file isolation capabilities of each mode environment in the mobile terminal under test, and evaluating the security parameters of each mode environment of the mobile terminal under test.

[0027] Furthermore, this embodiment of the invention utilizes the JaCoCo tool to determine the program execution progress during testing. Specifically, this embodiment adds stealth probes to each method of the test program: the stealth probe is essentially a counter. When the test program executes the current method, the counter is activated and returns a unique probe marker, thus marking the number of times the current method has been executed. For loop statements, the number of times the loop method's entry and exit points have been executed is used to determine the progress, thereby generating a log of the program execution progress. The log includes the current time and the method number being executed at the current time. Since the stealth probe execution process depends on the actual execution status of the method and does not depend on the source code logic, it ensures that it can be deployed and executed for different programs.

[0028] Step S102: Determine the blocking parameters of the method based on the execution time of the test program and the hardware occupancy rate during the method execution.

[0029] Specifically, this embodiment of the invention analyzes the stealth probes placed in the method of the test program to determine whether the method at the current position has been executed. A probe is placed at the code location; the probe is a string of code unrelated to the program, only changing the value of a dedicated array corresponding to the probe. Therefore, when the program executes to the current method position, the probe program takes effect and changes the value of the probe's dedicated array, thus determining that the program has been executed once at the current code position. Therefore, by analyzing the performance overhead during code execution and the array changes during targeted data usage, the current data reuse situation is assessed. Furthermore, the instability of the terminal's operating environment caused by the switching of the execution environment of the mobile terminal under test during the test operation is analyzed: a mobile terminal contains multiple environments, and the purpose of the test is to determine whether the program is stable during execution and whether it can accurately identify and quickly respond to different operations. Therefore, by analyzing the terminal device blocking situation during the execution of the generated instruction combination, high-blocking segments in the instruction combination are filtered out based on the terminal device blocking situation during the execution of a single instruction. Based on the degree of impact of the combined segments on the operational stability of different environments, combined with the affected method positions within the program, the vulnerability areas of the program's methods are extracted.

[0030] Furthermore, the execution of a single instruction may cause the terminal device to experience operational blockage, essentially reflecting the bottleneck effect of hardware resources or system calls (such as disk read / write being occupied, leading to I / O access blockage, or memory access latency caused by CacheMiss, forcing the processor to slow down). This demonstrates that the current instruction has successfully tested the system performance bottleneck of the terminal device in the current environment. Therefore, this embodiment of the invention determines the blocking parameters of the method by considering the abnormally prolonged execution time of the currently executing instruction and the current instruction's occupation of terminal resources. Therefore, as an optional embodiment of the invention, determining the blocking parameters of the method based on the execution duration of the test program and the hardware occupancy rate during method execution includes: determining the execution duration of the test program and its historical average execution duration, the hardware occupancy rate during method execution, the minimum hardware occupancy rate, and the number of usable hardware devices in the mobile terminal under test; and determining the blocking parameters based on the execution duration, historical average execution duration, occupancy rate, minimum occupancy rate, and the number of usable hardware devices.

[0031] Specifically, the historical average execution time of the test program during its current execution can be the average of the historical execution times of the method over a past period. In determining the execution time, as an optional embodiment of the present invention, determining the execution time of the test program during its current execution includes: adding hidden probes to each method of the test program; and using the time difference between the activation time of the hidden probe corresponding to a method and the activation time of the next hidden probe as the execution time of the test program during its current execution.

[0032] Specifically, this embodiment of the invention takes method a in the test program as an example. It uses a stealth probe to determine the currently executing method a, and uses the time difference between the current stealth probe activation time and the next stealth probe activation time. The execution duration of the current method a is used as the execution time (if the current method is executing and the next probe has not been activated, the execution duration is the time difference between the current probe activation time and the current time). The execution duration of method a up to the current time is compared to determine if a timeout has occurred. Specifically, if the execution duration of method a exceeds a predetermined threshold, a timeout can be identified.

[0033] Furthermore, this embodiment of the invention extracts the occupancy status of each hardware resource during execution. Specifically, during the execution of current method a, if the occupancy rate of a certain hardware component remains at an extremely high level, while the occupancy rate of the remaining corresponding hardware components is relatively low (the occupancy rate refers only to the occupancy rate of current method a), it indicates that current method a has contributed to the high occupancy rate of a certain hardware component, demonstrating that current method a has blocked the operation of the mobile terminal device under test in the current environment. Therefore, this embodiment of the invention uses the following formula to calculate the blocking parameter of method a at the current time t:

[0034]

[0035] In the above formula, This represents the blocking parameter of method a in the test program at the current time t. This indicates the execution time of method a in the test program. This represents the historical average execution time of method a in the test program. This represents the utilization rate of the j-th hardware component used by method a. This represents the minimum utilization rate of the j-th hardware component. This indicates the amount of hardware required for method a. This indicates the number of usable hardware components in the mobile terminal under test.

[0036] in, This indicates the execution time of the current method a. Compared with the historical average execution time of this method ratio The difference from 1 indicates whether the execution time of method a has been abnormally prolonged during the current test. That is, since the hardware performance parameters of the mobile terminal under test cannot be changed during the current test, and the encapsulated method code has not been altered, the abnormally prolonged execution time of method a suggests that the extended response time exhibited during method a's execution may be due to hardware performance bottlenecks caused by the current method, resulting in an abnormally prolonged execution progress. This represents the utilization rate of the j-th hardware segment used by method a at time t. The minimum utilization rate of the j-th hardware currently running (Not necessarily 0; for example, the processor will perform system computational tasks even when it is not performing additional computational tasks, so there is always a load.) The difference, traversing all the hardware used by method a. The resulting cumulative occupancy rate is related to the number of usable hardware devices in the mobile terminal under test. The larger the ratio, the higher the hardware utilization rate of the current method a, and the larger the overall scale of the available hardware being occupied (i.e., the utilization rate and number of individual hardware are in the same range; for example, if only one hardware can be called and the method calls one hardware, the numerator is 100%-0% and the denominator is 1, reaching the maximum value of 1).

[0037] Thus, by extracting the occupancy rate of each hardware component in the mobile terminal under test at each time t, the controller can determine the blocking parameters of method a at each time t.

[0038] Step S103: Based on the blocking parameters of each method in the test operation of the mobile terminal under test, determine the operational validity of the test operation during execution.

[0039] Specifically, the test operation sequence G, which performs test operations on the mobile terminal under test, contains multiple test operations. When a single test operation is executed on the mobile terminal under test, the mobile terminal under test will call multiple methods 'a' corresponding to the test operation to complete the test. Abnormal test operations refer to terminal freezing (unresponsive for a long time), timeout completion, etc. The essence of abnormal test operations is that excessive blocking of methods occurs during the execution of the operation. Therefore, the impact of test operation g on the mobile terminal is judged by the changes in the blocking status among the multiple methods 'a' corresponding to test operation g. Therefore, as an optional embodiment of the present invention, the determination of the operational validity of the test operation during the execution process based on the blocking parameters of each method in the test operation of the mobile terminal under test includes: determining the minimum blocking parameter and the standard deviation of the blocking parameters of all methods in the test operation of the mobile terminal under test; determining the first difference between the blocking parameters of each method in the test operation and the minimum blocking parameter, and determining the first ratio between the first difference and the standard deviation; and determining the operational validity based on the first difference and the first ratio.

[0040] Specifically, in this embodiment of the invention, the execution order of method a corresponding to the current test operation g is first determined, and the blocking parameters of each method a are placed. Then, the effectiveness of the operation in the current execution process is determined by the aggregation direction of the influence of the blocking parameters during execution. Taking test operation g as an example, this embodiment of the invention uses the following formula to calculate the effectiveness of test operation g during execution:

[0041]

[0042] In the above formula, This indicates the effectiveness of the test operation g during execution. This indicates that the test operation g is called during its execution. The blocking parameter of method a. This represents the minimum absolute value of the blocking parameters of each method during the execution of test operation g. This represents the standard deviation of the blocking parameters for all methods a in test operation g. This indicates the number of times test operation g calls method a.

[0043] in, During the execution of the current test operation g, the call to the first The blocking parameter of method a The minimum absolute value of the blocking parameters of each method in the current test operation g. The difference is the ratio of the blocking effect of any method in test operation g to the standard deviation of the blocking parameters for all methods a in test operation g. This formula compares the blocking effect of any method in test operation g with the blocking effect of the method with the least impact in test operation g, thereby accurately assessing the significance of the execution blocking effect among the methods in the current test process. It also compares the standard deviations of the blocking parameters to correctly assess the range of blocking significance (for example, if the blocking parameters themselves fluctuate greatly, the difference in the numerator is large, but the standard deviation is also large, indicating that the actual deviation is not significant, i.e., a fluctuating reference frame is set).

[0044] Furthermore, by transforming the numerical range of the cubic comparison value, the overall anomaly scale of the mobile terminal caused by the test operation is obtained by traversing all methods a corresponding to the current test operation g. Therefore, the anomaly metric of a single method is not obtained by averaging. The more methods a corresponding to the current test operation g, the more obvious the anomalies of each method are, indicating that the test results of the impact of the test operation g on the mobile terminal are more effective after traversing and superimposing.

[0045] It is worth noting that, in order to avoid A value of 0 causes the formula to fail to calculate. This invention can address this issue. +0.001. That is... .

[0046] Step S104: Based on the operational validity of each test operation, determine the valid operation segment. The valid operation segment includes at least one test operation, and perform data isolation testing on each mode environment based on the valid operation segment.

[0047] Specifically, by combining all the test operations g that have been executed so far, the effectiveness of each test operation is determined. The ability of each test operation to cause abnormal blocking of the mobile terminal is obtained during the test. Therefore, a set of test operations with high operational effectiveness is selected to obtain effective operation segments. The operation segments are adaptively selected according to different test requirements. As an optional embodiment of the present invention, determining effective operation segments based on the operational effectiveness of each test operation includes: sorting the operational effectiveness of each test operation in descending order to obtain a descending effectiveness sequence; calculating the effectiveness difference value between adjacent operational effectiveness in the descending effectiveness sequence; extracting the maximum value from each effectiveness difference value and determining the larger of the two operational effectiveness values ​​corresponding to the maximum value; determining the interval between the larger value and the maximum operational effectiveness in the descending effectiveness sequence as the high effectiveness interval; merging the consecutive test operations corresponding to the operational effectiveness in the high effectiveness interval to obtain effective operation segments.

[0048] Specifically, the embodiments of the present invention first combine the operational effectiveness of each test operation obtained. Arrange the operations in descending order to obtain a descending validity sequence. Then, calculate the difference between the validity of the next operation and the validity of the previous operation in the descending validity sequence; use this difference as the validity difference value. ,in, This indicates the difference in validity. This indicates the validity of the i-th operation. This represents the validity of the (i-1)th operation. Then, extract the validity from each validity difference value. and determine the The numerical values ​​of the validity of two adjacent operations are respectively , and then from Select the larger value from the list, and use the selected larger value as the largest value. For example, the operation with the highest validity is selected from the descending validity sequence. The maximum operational validity will be determined separately. As the left endpoint of the highly efficient interval, the larger value As the right endpoint of the highly efficient interval, we obtain the highly efficient interval [ , Finally, the highly effective interval [ , The positions of the valid operations in the sequence are mapped to the test operation sequence G. The consecutively marked test operations in the test operation sequence G are merged to obtain a valid operation segment.

[0049] Furthermore, after obtaining the valid operation segments, this embodiment of the invention stores a list of all valid operation segments and selects operation segments according to different testing requirements. As an optional embodiment of the invention, data isolation testing of each mode environment based on valid operation segments includes: determining the testing requirements of the terminal under test; selecting target valid operation segments based on the testing requirements; and using the target valid operation segments to perform data isolation testing of each mode environment.

[0050] Specifically, when determining the testing requirements of the terminal under test in this embodiment of the invention, the supported mode environment types, data interaction scenarios, and security compliance requirements are first clarified. The data storage scope, access rules, and potential risk points of each mode are then analyzed to form testing requirements covering core scenarios. Next, based on the testing requirements, target valid operation segments are selected, covering core operations such as data reading and writing, and state changes, including boundary and abnormal scenarios. The segments are guaranteed to be reproducible and atomic, forming a test case set covering single-mode and cross-mode interactions. Finally, when testing with the target valid operation segments, dedicated data storage is verified in a single mode, data inaccessibility is verified across modes, and data residue is checked in scenarios such as mode exit. Combined with quantitative evaluation using tools, this ensures effective data isolation across modes.

[0051] Furthermore, as an optional embodiment of the present invention, after performing data isolation tests on each mode environment based on effective operation segments, the method further includes: statistically analyzing the data of the test program in different mode environments of the test terminal under test, and if there is non-isolated data in any mode environment, determining that the test program's data is not isolated in different mode environments.

[0052] Specifically, this embodiment of the invention uses SMS data, contact data, call log data, and application q as examples for testing requirements. The control terminal sends a broadcast to the mobile terminal under test. Upon receiving the broadcast, the mobile terminal under test checks whether there is SMS data A, contact data A, and call log data A that are not marked as belonging to mode A under mode A, and records the result. Then, the control terminal checks the process ID of application q in mode A, compares it with the previously recorded process ID, determines whether it is the same as the process ID of application q in other modes, and records the result. Finally, the control terminal checks the files in other modes to determine whether there is a file r marked as current mode A, and records the result.

[0053] Furthermore, as an optional embodiment of the present invention, after statistically analyzing the test program under different mode environments of the test terminal under test, and determining that the test program's data is not isolated in different mode environments if non-isolated data exists in any mode environment, the method further includes: outputting a visual table, the visual table including the test program and the test results.

[0054] Specifically, in this embodiment of the invention, an Excel file can be output as a visual table, which includes the test program and the test results of the data isolation test.

[0055] This invention, by installing test programs in various modes of the mobile terminal under test, can more comprehensively cover the complex logic of process scheduling, permission verification, and resource allocation relied upon for multi-mode isolation of mobile terminals, thus overcoming the shortcomings of traditional solutions in terms of functional logic coverage. Furthermore, the solution determines the validity of test operations by calculating blocking parameters (combining execution time and hardware utilization), thereby selecting valid operation segments for testing. This mechanism can dynamically identify and capture valid execution processes in coherent operations, avoiding omissions in detecting implicit data transfer between processes due to timing deviations in test steps, effectively solving the problem of lack of timing control in traditional solutions. Moreover, data isolation testing based on valid operation segments ensures that the testing process focuses on real and valid operation sequences, reducing the interference of invalid operations on test results, thereby significantly improving the accuracy and reliability of multi-mode mobile terminal data isolation test results. In addition, while improving test completeness and accuracy, the selection of valid operation segments avoids redundant testing of invalid operations, maintaining high test efficiency while ensuring test quality.

[0056] Example 2:

[0057] Corresponding to the automated testing method for multi-mode mobile terminal data isolation provided in the above embodiments, based on the same technical concept, this embodiment of the invention also provides an automated testing system for multi-mode mobile terminal data isolation. This automated testing system for multi-mode mobile terminal data isolation is used to execute the above-described automated testing method for multi-mode mobile terminal data isolation. Figure 2 This is a schematic diagram of the structure of an automated testing system for data isolation of multi-mode mobile terminals provided in one embodiment of the present invention, as shown below. Figure 2 As shown. The automated testing system based on multi-mode mobile terminal data isolation can vary significantly due to differences in configuration or performance. It may include one or more processors 201 and memory 202. The memory 202 stores computer programs that can run on the processor 201. The processor 201 executes the programs stored in the memory 202 to implement the various steps in the embodiments of the automated testing method based on multi-mode mobile terminal data isolation described above. The memory 202 can be temporary or persistent storage. The application program stored in the memory 202 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions for the automated testing system based on multi-mode mobile terminal data isolation.

[0058] Furthermore, the processor 201 can be configured to communicate with the memory 202 and execute a series of computer-executable instructions in the memory 202 on the automated test system based on multi-mode mobile terminal data isolation. The automated test system based on multi-mode mobile terminal data isolation may also include one or more power supplies 203, one or more wired or wireless network interfaces 204, one or more input / output interfaces 205, and one or more keyboards 206.

[0059] Specifically, in this embodiment, the automated testing system for data isolation of multi-mode mobile terminals includes a processor, a communication interface, a memory, and a communication bus; wherein, the processor, communication interface, and memory communicate with each other via the bus; the memory is used to store computer programs; and the processor is used to execute the programs stored in the memory to achieve the above... Figure 1 The various steps in the method embodiments are the same as those in the above method embodiments, and have the same beneficial effects. To avoid repetition, the embodiments of the present invention will not be described again here.

[0060] It should be noted that the automated testing system based on multi-mode mobile terminal data isolation provided in this embodiment of the invention and the automated testing method based on multi-mode mobile terminal data isolation provided in this embodiment of the invention are based on the same application concept. Therefore, the specific implementation of this embodiment can refer to the implementation of the aforementioned automated testing method based on multi-mode mobile terminal data isolation, and has the same or similar beneficial effects. Repeated parts will not be described again.

[0061] It should be noted that the order of the above embodiments of the present invention is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. The processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired result. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0062] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on describing the differences from other embodiments.

[0063] This invention also proposes a computer-readable storage medium storing one or more programs, which, when executed by an automated testing system based on multi-mode mobile terminal data isolation that includes multiple applications, cause the automated testing system based on multi-mode mobile terminal data isolation to perform... Figure 1 The methods disclosed in the embodiments shown achieve the functions and beneficial effects of the methods in the preceding method embodiments, and will not be repeated here.

[0064] Computer-readable storage media include read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

Claims

1. A multi-mode mobile terminal data isolation automated testing method based on, characterized by, The method comprises the following steps: installing a test program in each mode environment of a mobile terminal to be tested; determining a blocking parameter of each method in the test operation of the mobile terminal to be tested according to an execution duration of the test program and an occupancy rate of hardware during execution of the method; determining operation effectiveness of the test operation in execution according to the operation effectiveness of each test operation; determining an effective operation segment comprising at least one test operation according to the operation effectiveness of each test operation, and performing data isolation testing on each mode environment based on the effective operation segment; determining the operation effectiveness of the test operation in execution comprises: determining a minimum blocking parameter in the blocking parameters of each method in the test operation of the mobile terminal to be tested and a standard deviation of the blocking parameters of all methods in the test operation; determining a first difference value between the blocking parameter of each method in the test operation and the minimum blocking parameter, and determining a first ratio value between the first difference value and the standard deviation; determining the operation effectiveness based on the first difference value and the first ratio value; determining the effective operation segment according to the operation effectiveness of each test operation comprises: sorting the operation effectiveness of each test operation in descending order to obtain a descending sequence of effectiveness; calculating an effectiveness difference value between adjacent operation effectiveness in the descending sequence of effectiveness; extracting a maximum value from each effectiveness difference value, and determining a larger value of the two operation effectiveness corresponding to the maximum value; determining an interval between the larger value and a maximum operation effectiveness in the descending sequence of effectiveness as a high effectiveness interval; merging continuous test operations corresponding to the operation effectiveness in the high effectiveness interval to obtain an effective operation segment.

2. The multi-mode mobile terminal data isolation automated testing method based on claim 1, wherein, determining the blocking parameter of the method comprises: determining an execution duration of the test program, a historical average execution duration, an occupancy rate of hardware occupied during execution of the method, a minimum occupancy rate of the occupied hardware, and a number of available hardware in the mobile terminal to be tested; determining the blocking parameter based on the execution duration, the historical average execution duration, the occupancy rate, the minimum occupancy rate, and the number of available hardware.

3. The multi-mode mobile terminal data isolation automated testing method based on claim 1, wherein, determining the execution duration of the test program in execution comprises: adding an invisible probe in each method of the test program; taking a time difference between a time when the invisible probe corresponding to the method is activated and a time when a next invisible probe is activated as the execution duration of the test program in execution.

4. The multi-mode mobile terminal data isolation automated testing method based on claim 1, wherein, determining the interval between the larger value and the maximum operation effectiveness in the descending sequence of effectiveness as a high effectiveness interval comprises: taking the maximum operation effectiveness as a left endpoint of the high effectiveness interval, and taking the larger value as a right endpoint of the high effectiveness interval.

5. The multi-mode mobile terminal data isolation automated testing method based on claim 1, wherein, calculating the effectiveness difference value between adjacent operation effectiveness in the descending sequence of effectiveness comprises: calculating a difference value between a next operation effectiveness and a previous operation effectiveness of adjacent operation effectiveness in the descending sequence of effectiveness; The difference value is taken as the validity difference value.

6. The multi-mode mobile terminal data isolation automated testing method based on claim 1, wherein, The data isolation test of each mode environment based on the effective operation fragment includes: determining the test requirement of the test terminal to be tested; selecting a target effective operation fragment based on the test requirement; performing data isolation test on each mode environment by using the target effective operation fragment.

7. The multi-mode mobile terminal data isolation automated testing method based on claim 1, wherein, After the data isolation test of each mode environment based on the effective operation fragment, the method further includes: statistically analyzing the data of the test program under different mode environments of the test terminal to be tested, and determining that the data of the test program under different mode environments is not isolated if there is non-isolated data under any mode environment.

8. The multi-mode mobile terminal data isolation automated testing method based on claim 7, wherein, After the statistical analysis of the data of the test program under different mode environments of the test terminal to be tested, and determining that the data of the test program under different mode environments is not isolated if there is non-isolated data under any mode environment, the method further includes: outputting a visual table, wherein the visual table includes the test program and the test result.

Images