WO2019051714A1

WO2019051714A1 - Test method and test apparatus for application memory of smart device

Info

Publication number: WO2019051714A1
Application number: PCT/CN2017/101744
Authority: WO
Inventors: 刘银银
Original assignee: 深圳传音通讯有限公司
Priority date: 2017-09-14
Filing date: 2017-09-14
Publication date: 2019-03-21

Abstract

A test method for an application memory of a smart device. The test method comprises: writing, for an application of a smart device, a test scenario corresponding to the application, and configuring at least one test case based on the application according to the test scenario (101); configuring a test execution file based on the test case according to information of the test case (102); executing the test case according to the test execution file to obtain a memory output result of the test case (103); and comparing the memory output result with a memory expectation result to obtain a test result of the test case (104). The method simplifies the writing and maintenance of test cases.

Description

Test method and test device for application memory of smart device

Technical field

The present invention relates to the field of smart devices, and in particular, to a test method and a test device for an application memory of a smart device.

Background technique

Design the corresponding test scenario, simulate the user's habit design use case, execute the test, the whole test process is completely separated from the pc to make the mobile phone run independently, freely set the number of runs, save the information and capture screenshots for the functional problems generated during the operation.

The entire script design is written based on uiautomator. To facilitate script writing, the entire script is written using the sh script. Java is used to encapsulate the corresponding method, and the AndroidUiTool.jar package is built into the mobile phone. In the interface file: Uitool is implanted into the mobile phone, and the uiautomator encapsulation method is used to obtain the command: dumpsys meminfo+ package name, respectively, to obtain detailed information of the memory and The overall memory value, the memory table obtained from this value is convenient to visually check the memory change trend. For the functional problems generated during the operation, the corresponding screenshots can be obtained, and the corresponding mtklog provides a certain basis for solving the problem.

Uiautomator, as its name implies, is used for ui automation testing, mainly to simulate click, slide, input text and other operations without artificial manipulation. If a set of repeated operations is implemented with uiautomator, it will greatly improve efficiency. However, the scope of uiautomator is very limited. After learning, you will know that in uiautomator, each ui control is an object of UiObject, and does not provide an interface for obtaining the corresponding control class (android.widget.*) of the control. So in uiautomator, a Button and an ImageView are the same - both are UiObject objects.

Summary of the invention

In order to overcome the above technical drawbacks, it is an object of the present invention to provide a test method and test apparatus for an application memory of a smart device.

The invention discloses a test method for an application memory of a smart device, characterized in that the test method comprises:

Writing a test scenario corresponding to the application to an application of the smart device, and setting at least one test case based on the application according to the test scenario;

Configuring a test execution file based on the test case according to the information of the test case;

Performing the test case according to the test execution file to obtain a memory output result of the test case;

Comparing the memory output result with the expected result of the memory to obtain a test result of the test case.

Preferably, the test scenario corresponding to the application is written to the application of the smart device, and at least one test case based on the application is set according to the test scenario, including:

Writing each operation flow of the application into a test scenario for the application;

Acquiring the relationship of the test scenario according to the information about the test scenario of the application, and integrating the test scenario based on the relationship ranking to generate the test case.

Preferably, configuring the test execution file based on the test case according to the information of the test case comprises:

Obtaining information about the test case to obtain an association between the test cases, and configuring an execution manner of the test case according to the association;

The execution mode is recorded in the test execution file.

Preferably, executing the test case according to the test execution file to obtain a memory output result of the test case includes:

Setting a preset time interval threshold;

When the test case is executed according to the test execution file, the memory information of the smart device is recorded according to a preset time interval threshold and integrated into the memory output result.

Preferably, the memory output result is compared with the expected result of the memory, and the test result of the test case is obtained, including:

Pre-preserving a correspondence between the test case and the expected result of the memory based on the test case;

Comparing the information of the memory output result with the information of the expected result of the memory, and analyzing information of the test result of the test case.

The invention also discloses a test device for an application memory of a smart device, wherein the test device comprises: a use case module, a configuration module, an execution module, a comparison module, wherein

The use case module is configured to write a test scenario corresponding to the application to an application of the smart device, and set at least one test case based on the application according to the test scenario;

The configuration module is communicatively coupled to the use case module, and configured to configure a test execution file based on the test case according to the information of the test case;

The execution module is communicatively coupled to the configuration module, and configured to execute the test case according to the test execution file to obtain a memory output result of the test case;

The comparison module is in communication with the execution module, and is configured to compare the memory output result with a memory expected result to obtain a test result of the test case.

Preferably, the use case module includes:

a scene unit, configured to write each operation flow of the application into a test scenario for the application;

The use case unit is configured to be in communication with the scenario unit, configured to acquire the relationship of the test scenario according to the information about the test scenario of the application, and integrate the test scenario based on the relationship to generate the test case.

Preferably, the configuration module includes:

An association unit, configured to obtain information about the test case to obtain an association between the test cases, and configure an execution manner of the test case according to the association;

And a configuration unit, configured to communicate with the associated unit, to record the execution mode in the test execution file.

Preferably, the execution module includes:

a time unit, configured to set a preset time interval threshold;

An execution unit, configured to be in communication with the time unit, configured to record memory information of the smart device according to a preset time interval threshold and integrate the memory output result when the test case is executed according to the test execution file .

Preferably, the comparison module comprises:

a storage unit, configured to pre-store a correspondence between the test case and the expected result of the memory based on the test case;

And a comparison unit, configured to communicate with the storage unit, to compare the information of the memory output result with the expected result of the memory, and analyze the information of the test result of the test case.

After adopting the above technical solution, compared with the prior art, the following beneficial effects are obtained:

1. Improved memory test can be implemented: execute shell script test, simplify test case writing, maintenance; executable function test, stress test; timely log capture and save during test; select free module to test and obtain test memory anytime and anywhere Test Results;

2. Improved memory test advantages: script writing is simple, no need for testers to understand the code implementation details, based on Java, the test code structure is simple, interactive test can get the memory usage information of the specified application, separate from the third-party tools, completely apply Android itself The command, offline test, does not need to occupy PC resources, freely select the test module according to the test requirements, obtain memory information anytime and anywhere, does not affect the execution of the script.

DRAWINGS

1 is a schematic flow chart in accordance with a preferred embodiment of the present invention;

2 is a schematic flow chart of a specific implementation of step 101 shown in FIG. 1;

3 is a schematic flow chart of a specific implementation of step 102 shown in FIG. 1;

4 is a schematic flow chart of a specific implementation of step 103 shown in FIG. 1;

FIG. 5 is a schematic flow chart of a specific implementation of step 104 shown in FIG. 1;

Figure 6 is a schematic view showing the structure in accordance with a preferred embodiment of the present invention;

Figure 7 is a schematic view of a structure in accordance with a preferred embodiment of the present invention;

Figure 8 is a schematic view of a structure in accordance with a preferred embodiment of the present invention;

Figure 9 is a schematic view showing the structure in accordance with a preferred embodiment of the present invention;

Figure 10 is a schematic view of the structure in accordance with a preferred embodiment of the present invention.

Reference mark:

10-test device, 11-use case module, 12-configuration module, 13-execution module, 14-comparison module:

Detailed ways

Advantages of the present invention are further explained below in conjunction with the accompanying drawings and specific embodiments.

Exemplary embodiments will be described in detail herein, examples of which are illustrated in the accompanying drawings. The following description refers to the same or similar elements in the different figures unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with aspects of the present disclosure as detailed in the appended claims.

Those skilled in the art can understand that the smart device used herein includes a device of a wireless signal receiver, a device having only a wireless signal receiver without a transmitting capability, and a device for receiving and transmitting hardware, which has the capability to A device that performs bidirectional communication reception and transmission hardware on a two-way communication link. Such a device may comprise: a cellular or other communication device having a single line display or a multi-line display or a cellular or other communication device without a multi-line display; PCS (Personal Communications Service), which may Combined voice, data processing, fax and/or data communication capabilities; PDA (Personal Digital Assistant), which can include radio frequency receivers, pagers, Internet/Intranet access, web browsers, notepads, calendars and / Or a GPS (Global Positioning System) receiver; a conventional laptop and/or palmtop computer or other device having a conventional laptop and/or palmtop computer or other including a radio frequency receiver or other device. As used herein, "device", "smart device" may be portable, transportable, installed in a vehicle (aviation, sea and/or land), or adapted and/or configured to operate locally, and/or Run in any other location on the Earth and/or space in a distributed form. The "device" and "smart device" used herein may also be a communication device, an internet device, a music/video playback device, such as a PDA, a MID (Mobile Internet Device), and/or have a music/video playback. Functional mobile phones can also be smart TVs, set-top boxes and other devices.

It should be understood that although the terms first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as second information without departing from the scope of the present disclosure. Similarly, the second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to a determination."

In the description of the present invention, it is to be understood that the terms "longitudinal", "transverse", "upper", "lower", "front", "rear", "left", "right", "vertical", The orientation or positional relationship of the indications of "horizontal", "top", "bottom", "inside", "outside", etc. is based on the orientation or positional relationship shown in the drawings, only for the convenience of describing the present invention and simplifying the description, rather than It is to be understood that the device or elements referred to have a particular orientation, are constructed and operated in a particular orientation and are therefore not to be construed as limiting.

Referring to Figures 1-5, a flow diagram consistent with a preferred embodiment of the present invention includes:

Step 101: Write a test scenario corresponding to the application to the application of the smart device, and set at least one test case based on the application according to the test scenario;

Write each operation flow of the application as a test scenario for the application

In a specific implementation, when performing a functional test of an application of a smart device, the input is a test requirement, for example, each operation flow to the application. If you need to drive the model, you need to constrain the test requirements, that is, we need to formalize the test requirements. The formalization of test requirements is easy to convert to test requirements.

Specifically, the formalization of test requirements is the need to express the test requirements, which can include the transformation from natural language to UML. In the test, it is mainly expressed by, but not limited to, UML usecase diagrams and activity diagrams.

In addition, after formalizing the test requirements, you need to import the corresponding activities when you input the test requirements. Moving pictures, otherwise you need to test the requirements analysis to do more work, artificially solve the unnecessary test requirements, and the problems expressed by humans. This can lead to deviations in understanding and lack of testing. Briefly, the input test requirements can include an activity graph that is formalized in UML form for the requirement.

Acquiring the relationship of the test scenario according to the information of the test scenario of the application, and integrating the test scenario based on the relationship to generate the test case.

As can be seen from the above method, the test requirements include a test activity map. More specifically, the basis of the conversion is to define test items, that is, to define test items in the test requirements, such as, but not limited to, which application operations need to be tested. Then, according to the test item, the activity graph is analyzed to see if it is necessary to increase the check node for the demand item (which will be converted into a checkpoint). If the original activity map has been able to meet the requirements, you can directly convert the demand activity map into a test activity map; if it is missing, you need to add checkpoints to the demand activity graph, mainly to increase the inspection function, the most typical is to increase the query. And can be verified according to the query results.

Corresponding test data is generated according to the test scenario, and the test data is added to the test scenario corresponding thereto to form a test case, and all the test cases are output.

Specifically, test case design is required after the test scenario is established. From the perspective of model driving, the test cases are formed by adding test data to the test scenario, and there is a certain relationship between the test scenarios, namely: test scenario + test data - test case. Therefore, the focus of this method step is to design a test case, or add test data to the test case to form a test case. Obviously, the test case can include many test scenarios.

Step 102: Configure a test execution file based on the test case according to the information of the test case;

Specifically, when it is required to determine the runtime memory usage of the functional test of the application for the smart device, the code under test may be compiled to generate an executable file for code coverage analysis, ie, setting the compilation parameters, The executable file is generated according to the compilation parameters, that is, the test case parameters are added in the component compilation. For example, the test execution file with the test case information is packaged, that is, the information for identifying the test case is obtained, the information including the test case is generated, and the information of the test case is packaged into the test execution file. The test execution file identifies the code during execution to be used for runtime memory usage analysis, that is, the test execution file, and the test execution file includes test case information, which is added during packaging. Finally, the corresponding method is encapsulated to generate AndroidUiTool.jar. In the write interface file: Uitool is implanted in the phone, calling the encapsulation method of uiautomator.

The execution mode is recorded in the test execution file.

Because testing needs to be performed in a specific environment, you need to deploy a test environment. Therefore, will After the tested test case is compiled to generate a test execution file for runtime memory usage, the test execution file is deployed in the test environment, that is, the jar file is deployed in the test environment to deploy the test environment. This includes, but is not limited to, the operating environment of the smart device.

The executable file is deployed in the test environment, that is, after the test environment is deployed, the test case for the functional test is executed in the test environment, and the test execution file and the test case for the functional test are submitted to the test case execution management tool. In this embodiment, a custom sh file or the like is used to test the test cases configured in the test execution file.

Step 103: Execute the test case according to the test execution file to obtain a memory output result of the test case.

Setting a preset time interval threshold;

When you run test execution files on a smart device to create test cases and automate these test cases, they take the test cases in order. Then, when the smart device executes the taken test, an execution time interval of the test case is set between each test case, so that the test case is executed according to the interval of the execution time, and the test frame used in this embodiment is preset to wait. The period, that is, the maximum tolerance time of the response after the test case is executed, and continuously detects whether the smart device returns a response to the test message within the preset waiting period; if the smart device returns a response within a preset waiting period, The test framework stops waiting, and the smart device receives the returned response and performs subsequent tests according to the returned response; if the smart device does not return a response within a predetermined waiting period, the test framework no longer waits, directly returns the timeout information to the smart The device notifies the smart device to skip testing the taken test case and perform the test of the next test case.

When the test case is executed according to the test execution file, the memory information of the smart device is recorded according to a preset time interval threshold and integrated into the memory output result;

The pushed test execution file can be received according to the operating principle of the above test framework. The first thread of the test framework executes the test case, and the first thread can execute the test case by calling the relationship of the test case included in the test execution file, and at the same time, the second thread is created, and the memory monitoring is started in the second thread. When the test execution file finishes running, the test case execution ends and the first thread terminates. At this time, the termination signal is sent to the second thread, the termination signal indicates the end of the test case, and the second thread terminates. When there are subsequent test cases that need to be executed, the above execution steps will be repeated. When multiple test cases need to be executed simultaneously, the embodiment is not limited to only starting a pair of threads, for example, the first thread executes the test case, and the second The thread monitors the memory and records it in real time with the memory output.

Specifically, the second thread is in operation, detecting whether the test case in the first thread is still executing, detecting whether a termination signal from the first thread is received, and if yes, determining that the execution of the test case in the first thread ends, otherwise determining Test cases in one thread are still executing. If it is determined that the execution of the test case in the first thread is finished, the memory can be stopped. Monitor and terminate the second thread. If it is determined that the test case in the first thread is still executing, the memory usage data of the tested application is collected. The application to be tested can be selected, and the memory occupation data of the tested application is collected from the memory monitoring data acquired by the smart device.

Step 104: Comparing the memory output result with the expected result of the memory to obtain a test result of the test case;

Pre-storing a correspondence between the test case and the expected result of the memory based on the test case;

The estimated memory expected result of the test case is pre-set. The expected result of the memory is the memory usage of the application associated with the test case at runtime, and is mainly used to detect whether the application has a memory leak at runtime.

Comparing the information of the memory output result with the expected result of the memory, and analyzing the information of the test result of the test case;

Obtaining the memory output result, that is, after the memory occupies the data, it can determine whether the tested application has a memory leak according to the memory occupation data. Specifically, it can be determined whether the memory occupation data is greater than the expected result of the memory, that is, the maximum memory alarm value, and if yes, determining that the tested application has a memory leak; or calculating the memory occupancy growth rate according to the memory occupation data, and performing the adjacent two executions. The degree of memory change in the time interval is usually abnormal growth. It is judged whether the memory occupancy growth rate is greater than the memory growth speed alarm value. If yes, it is determined that the tested application has a memory leak. If both of the above are negative, it is determined that no memory leak has occurred in the application under test. After subtracting the memory usage data collected in the previous time, the memory occupancy growth rate can be obtained by dividing the sampling time interval. For example, for a music program, the maximum memory alert value can be 50MB, and the memory growth speed alert value can be 10KB/s.

According to the above time interval threshold, if it is determined that the tested application does not have a memory leak, the execution result of the test case is marked as normal completion.

When it is determined that the tested application has a memory leak, an alarm signal is sent, and the memory information file of the tested application is simultaneously extracted, so as to locate the memory leak location of the tested application according to the memory information file. Specifically, the PID of the application under test can be passed. Use the get command: dumpsys meminfo+ package name to get the detailed information of the memory and the overall memory value. Obtain the memory table from this value to view the trend of the memory. For the functional problems generated during the operation, the corresponding screenshots can be obtained, and the corresponding mtklog provides a certain basis for solving the problem.

In this way, memory occupancy data and memory growth rate can more accurately determine whether a memory leak occurs, and when a memory leak is found, the tester can be notified at the first time, and the file storing the complete memory information can be obtained without connecting to the PC. Through this file tester can more accurately locate the location where the memory leak occurs, and avoid the situation that the memory information is incomplete and difficult to locate due to the memory being released.

A smart device embodying various embodiments of the present invention will now be described with reference to the accompanying drawings. In the following description, the use of suffixes such as "module", "component" or "unit" for indicating an element is merely an explanation for facilitating the present invention, and does not have a specific meaning per se. Therefore, "module" and "component" can be used in combination.

In the description of the present invention, unless otherwise specified and limited, it should be noted that the terms "mounted", "connected", and "connected" are to be understood broadly, and may be, for example, mechanical or electrical, or both. The internal communication of the components may be directly connected or indirectly connected through an intermediate medium. For those skilled in the art, the specific meanings of the above terms may be understood according to specific circumstances.

Referring to Figures 6-10, a device in accordance with the present invention can be implemented by a test device 10, including: a use case module 11, a configuration module 12, an execution module 13, and a comparison module 14.

The use case module 11 is configured to write a test scenario corresponding to the application to the application of the smart device, and set at least one test case based on the application according to the test scenario;

In addition, after formalizing the test requirements, you need to import the corresponding activity diagram when inputting the test requirements. Otherwise, you need to test the requirements analysis to do more work, artificially solve the unnecessary test requirements, and The problem that is artificially expressed. This can lead to deviations in understanding and lack of testing. Briefly, the input test requirements can include an activity graph that is formalized in UML form for the requirement.

Generating corresponding test data according to the test scenario, and adding the test data to the test field corresponding thereto Test cases are formed in the scene and all of the test cases are output.

The configuration module 12 is communicatively coupled to the use case module, and configured to configure a test execution file based on the test case according to the information of the test case;

The execution mode is recorded in the test execution file.

Because testing needs to be performed in a specific environment, you need to deploy a test environment. Therefore, after the test case being tested is compiled to generate a test execution file for runtime memory usage, the test execution file is deployed in the test environment, that is, the jar file is deployed in the test environment to deploy the test environment. The test environment includes, but is not limited to, the operating environment of the smart device.

The execution module 13 is in communication with the configuration module, and is configured to execute the test case according to the test execution file to obtain a memory output result of the test case;

Setting a preset time interval threshold;

Run test execution files on smart devices to create test cases and automate testing of these test cases When it is, the test cases are sequentially taken out in order. Then, when the smart device executes the taken test, an execution time interval of the test case is set between each test case, so that the test case is executed according to the interval of the execution time, and the test frame used in this embodiment is preset to wait. The period, that is, the maximum tolerance time of the response after the test case is executed, and continuously detects whether the smart device returns a response to the test message within the preset waiting period; if the smart device returns a response within a preset waiting period, The test framework stops waiting, and the smart device receives the returned response and performs subsequent tests according to the returned response; if the smart device does not return a response within a predetermined waiting period, the test framework no longer waits, directly returns the timeout information to the smart The device notifies the smart device to skip testing the taken test case and perform the test of the next test case.

Specifically, the second thread is in operation, detecting whether the test case in the first thread is still executing, detecting whether a termination signal from the first thread is received, and if yes, determining that the execution of the test case in the first thread ends, otherwise determining Test cases in one thread are still executing. If it is determined that the execution of the test case in the first thread is finished, the memory monitoring can be stopped and the second thread is terminated. If it is determined that the test case in the first thread is still executing, the memory usage data of the tested application is collected. The application to be tested can be selected, and the memory occupation data of the tested application is collected from the memory monitoring data acquired by the smart device.

The comparison module 14 is in communication with the execution module, and is configured to compare the memory output result with the expected result of the memory to obtain a test result of the test case;

Comparing the information of the memory output result with the expected result of the memory, analyzing the test result of the test case Information

In addition, an embodiment of the present invention further provides a computer readable storage medium having stored therein computer executable instructions, such as a non-volatile memory such as an optical disk, a hard disk, or a flash memory. The above computer executable instructions are for causing a computer or similar computing device to perform various operations in the above described test method for the application memory of the smart device.

Those skilled in the art will appreciate that the present invention includes apparatus related to performing one or more of the operations described herein. These devices may be specially designed and manufactured for the required purposes, or may also include known devices in a general purpose computer. These devices have computer programs stored therein that are selectively activated or reconfigured. Such computer program can be stored in a device (eg, computer) readable medium or in any type of medium suitable for storing electronic instructions and separately coupled to a bus, the computer readable medium comprising But not limited to any type of disk (including floppy disk, hard disk, optical disk, CD-ROM, and magneto-optical disk), ROM (Read-Only Memory), RAM (Random Access Memory), EPROM (Erasable Programmable) Read-Only Memory, EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory, magnetic card or light card. That is, a readable medium includes any medium that is stored or transmitted by a device (eg, a computer) in a readable form.

In the description of the present specification, the description with reference to the terms "one embodiment", "some embodiments", "example", "specific example", or "some examples" and the like means a specific feature described in connection with the embodiment or example. A structure, material or feature is included in at least one embodiment or example of the invention. In the present specification, the schematic representation of the above terms does not necessarily mean the same embodiment or example. Furthermore, the particular features, structures, materials, or characteristics described may be combined in a suitable manner in any one or more embodiments or examples.

It should be noted that the embodiments of the present invention are preferred embodiments, and are not intended to limit the scope of the present invention. Any one skilled in the art may use the above-disclosed technical contents to change or modify the equivalent embodiments. Any modification or equivalent changes and modifications of the above embodiments in accordance with the technical spirit of the present invention are still within the scope of the technical solutions of the present invention.

Claims

A test method for application memory of a smart device, characterized in that the test method comprises:

Writing a test scenario corresponding to the application to an application of the smart device, and setting at least one test case based on the application according to the test scenario;

Configuring a test execution file based on the test case according to the information of the test case;

Performing the test case according to the test execution file to obtain a memory output result of the test case;

Comparing the memory output result with the expected result of the memory to obtain a test result of the test case.
The test method according to claim 1, wherein a test scenario corresponding to the application is written to an application of the smart device, and at least one test case based on the application is set according to the test scenario, include:

Writing each operation flow of the application into a test scenario for the application;

Acquiring the relationship of the test scenario according to the information about the test scenario of the application, and integrating the test scenario based on the relationship ranking to generate the test case.
The test method according to claim 1, wherein the test execution file based on the test case is configured according to the information of the test case, comprising:

Obtaining information about the test case to obtain an association between the test cases, and configuring an execution manner of the test case according to the association;

The execution mode is recorded in the test execution file.
The test method of claim 1, wherein executing the test case according to the test execution file to obtain a memory output result of the test case comprises:

Setting a preset time interval threshold;

When the test case is executed according to the test execution file, the memory information of the smart device is recorded according to a preset time interval threshold and integrated into the memory output result.
The test method according to claim 1, wherein the memory output result is compared with an expected result of the memory, and the test result of the test case is obtained, including:

Pre-preserving a correspondence between the test case and the expected result of the memory based on the test case;

Comparing the information of the memory output result with the information of the expected result of the memory, and analyzing information of the test result of the test case.
A test device for an application memory of a smart device, wherein the test device includes: a use case module, a configuration module, an execution module, and a comparison module, wherein

The use case module is configured to write a test scenario corresponding to the application to an application of the smart device, and set at least one test case based on the application according to the test scenario;

The configuration module is communicatively coupled to the use case module, and configured to configure a test execution file based on the test case according to the information of the test case;

The execution module is communicatively coupled to the configuration module, and configured to execute the test case according to the test execution file to obtain a memory output result of the test case;

The comparison module is in communication with the execution module, and is configured to compare the memory output result with a memory expected result to obtain a test result of the test case.
The device of claim 6, wherein the use case module comprises:

a scene unit, configured to write each operation flow of the application into a test scenario for the application;

The use case unit is configured to be in communication with the scenario unit, configured to acquire the relationship of the test scenario according to the information about the test scenario of the application, and integrate the test scenario based on the relationship to generate the test case.
The device of claim 6, wherein the configuration module comprises:

An association unit, configured to obtain information about the test case to obtain an association between the test cases, and configure an execution manner of the test case according to the association;

And a configuration unit, configured to communicate with the associated unit, to record the execution mode in the test execution file.
The device of claim 6, wherein the execution module comprises:

a time unit, configured to set a preset time interval threshold;

An execution unit, configured to be in communication with the time unit, configured to record memory information of the smart device according to a preset time interval threshold and integrate the memory output result when the test case is executed according to the test execution file .
The device of claim 6, wherein the comparing module comprises:

a storage unit, configured to pre-store a correspondence between the test case and the expected result of the memory based on the test case;

And a comparison unit, configured to communicate with the storage unit, to compare the information of the memory output result with the expected result of the memory, and analyze the information of the test result of the test case.