CN114201392A - Android environment and android application stability testing method - Google Patents
Android environment and android application stability testing method Download PDFInfo
- Publication number
- CN114201392A CN114201392A CN202111481706.0A CN202111481706A CN114201392A CN 114201392 A CN114201392 A CN 114201392A CN 202111481706 A CN202111481706 A CN 202111481706A CN 114201392 A CN114201392 A CN 114201392A
- Authority
- CN
- China
- Prior art keywords
- test
- acquiring
- android
- application
- event
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 238000012430 stability testing Methods 0.000 title claims abstract description 19
- 238000012360 testing method Methods 0.000 claims abstract description 158
- 230000008569 process Effects 0.000 claims abstract description 22
- 238000009434 installation Methods 0.000 claims description 8
- 230000000694 effects Effects 0.000 claims description 4
- 238000012163 sequencing technique Methods 0.000 claims description 4
- 230000007613 environmental effect Effects 0.000 claims description 3
- 238000013112 stability test Methods 0.000 abstract description 11
- 238000001514 detection method Methods 0.000 abstract description 3
- 241000282693 Cercopithecidae Species 0.000 description 4
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
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
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
A method for testing stability of an android environment and an android application comprises the following steps: acquiring a test request; acquiring a test software list; acquiring test application information; acquiring a test event; testing the test software list according to the test event; and generating a test report. According to the android environment and the android application stability testing method, a testing method for environment stability in a container is provided for the first time aiming at a kmre android compatible environment in a domestic Kylin operating system, a user pseudo-random event stability test of the kmre environment is completed by adding a first control process, and stability testing of a plurality of APPs in the environment is realized; by adding a second control process, the detection of the APP window is completed, and the stability test is supplemented; by adding the third control process, the environment log is monitored, collected and stored, the stability test can be automatically ended and restarted, manual intervention is reduced, test operation is facilitated, and efficiency is improved.
Description
Technical Field
The invention belongs to the technical field of terminal application testing, and particularly relates to an android environment and an android application stability testing method.
Background
In the conventional android stability test, after a socket connection is established between an upper computer and an entity device or a simulator, a pseudo-user random event (such as screen clicking, sliding and the like) is triggered by using monkey to perform the test, wherein the monkey is a command line tool provided by an android software development kit, and the random operation event is simulated by a main screen; in the traditional monkey test, only a single APP or the whole system can be subjected to random event test, and the test form is single.
The technical scheme of the KMRE android compatible environment adopted in the domestic Kylin operating system is greatly different from a common simulator, the android system is operated through a container, the Linux kernel of the operating system is directly used, the main screen output of the android system is cut off, and the main screen output is displayed through a virtual screen. This implementation makes the traditional android stability monkey test impossible.
Disclosure of Invention
In order to solve the above problems, the present invention provides a method for testing stability of an android environment and an android application, wherein the method comprises the following steps:
acquiring a test request;
acquiring a test software list;
acquiring test application information;
acquiring a test event;
testing the test software list according to the test event;
and generating a test report.
Preferably, the obtaining of the test request includes the steps of:
acquiring test time;
acquiring a test application;
acquiring the testing times of each application;
acquiring a test event proportion;
acquiring a test event type;
and performing regression testing according to the recorded testing events.
Preferably, the acquiring the test software list includes the steps of:
acquiring an installation package of an android system in a container;
acquiring all applications in the installation package;
sequencing all the applications according to a preset sequence;
and generating a test software list according to the sorting order.
Preferably, the step of obtaining the test software list further comprises the steps of:
acquiring a test application white list;
and deleting all applications in the test application white list from the test software list. Preferably, the acquiring the test application information includes the steps of:
acquiring a test application name;
acquiring a test application window name;
acquiring the size of a test application window;
acquiring a position of a test application window;
and acquiring a test application address.
Preferably, the acquiring a test event comprises the steps of:
acquiring the percentage of the specified touch events;
acquiring a click event;
acquiring a navigation event;
acquiring a system key event;
acquiring an activity switching event;
acquiring a seed value for generating a random event;
acquiring a detailed level of the designated print information;
acquiring an ignore crash event;
acquiring an overtime neglecting event;
acquiring environmental resource use information;
and acquiring environment operation information.
Preferably, the step of testing the test software list according to the test event includes the steps of:
carrying out a system pressure test;
carrying out wireless network pressure test;
carrying out wired network pressure test;
carrying out a weak network pressure test;
performing an application pressure test;
performing multimedia pressure test;
a camera pressure test was performed.
Preferably, the step of testing the test software list according to the test event further includes the steps of:
carrying out a first control process test;
carrying out a second control process test;
a third control procedure test is performed.
According to the android environment and the android application stability testing method, a testing method for environment stability in a container is provided for the first time aiming at a kmre android compatible environment in a domestic Kylin operating system, a user pseudo-random event stability test of the kmre environment is completed by adding a first control process, and stability testing of a plurality of APPs in the environment is realized; by adding a second control process, the detection of the APP window is completed, and the stability test is supplemented; by adding the third control process, the environment log is monitored, collected and stored, the stability test can be automatically ended and restarted, manual intervention is reduced, test operation is facilitated, and efficiency is improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
Fig. 1 is a schematic diagram of an android environment and an android application stability testing method provided by the invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention will be described in further detail with reference to the accompanying drawings in conjunction with the following detailed description. It should be understood that the description is intended to be exemplary only, and is not intended to limit the scope of the present invention. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present invention.
As shown in fig. 1, in the embodiment of the present application, the present invention provides an android environment and an android application stability testing method, where the method includes the steps of:
s1: acquiring a test request;
in an embodiment of the present application, the obtaining of the test request includes:
acquiring test time;
acquiring a test application;
acquiring the testing times of each application;
acquiring a test event proportion;
acquiring a test event type;
and performing regression testing according to the recorded testing events.
In the embodiment of the application, when the test request is obtained, the test time can be obtained, the test application can be obtained, the test times of each application can be obtained, the proportion and the type of the test event can be obtained, and regression test can be performed according to the recorded test event.
S2: acquiring a test software list;
in an embodiment of the present application, the acquiring a test software list includes:
acquiring an installation package of an android system in a container;
acquiring all applications in the installation package;
sequencing all the applications according to a preset sequence;
and generating a test software list according to the sorting order.
In the embodiment of the application, when the test software list is obtained, firstly, an installation package of the android system in the container is obtained, then, all applications in the installation package are obtained, then, all the applications are sequenced according to a preset sequence, and finally, the test software list is generated according to the sequencing sequence.
In this embodiment of the present application, the acquiring a test software list further includes:
acquiring a test application white list;
and deleting all applications in the test application white list from the test software list.
In the embodiment of the present application, after the test software list is preliminarily obtained, a test application white list may be further obtained, and then all applications in the test application white list are deleted from the test software list.
S3: acquiring test application information;
in an embodiment of the present application, the acquiring test application information includes:
acquiring a test application name;
acquiring a test application window name;
acquiring the size of a test application window;
acquiring a position of a test application window;
and acquiring a test application address.
In the embodiment of the application, when the test application information is obtained, the name of the test application is obtained first, then the name of the test application window and the size and position of the window are obtained, and then the address of the test application is obtained.
S4: acquiring a test event;
in an embodiment of the present application, the acquiring a test event includes:
acquiring the percentage of the specified touch events;
acquiring a click event;
acquiring a navigation event;
acquiring a system key event;
acquiring an activity switching event;
acquiring a seed value for generating a random event;
acquiring a detailed level of the designated print information;
acquiring an ignore crash event;
acquiring an overtime neglecting event;
acquiring environmental resource use information;
and acquiring environment operation information.
In an embodiment of the present application, acquiring a test event may include: acquiring the percentage of a specified touch event, acquiring a click event, acquiring a navigation event, acquiring a system key event, acquiring an activity switching event, acquiring a seed value of a specified random event, acquiring the detailed level of specified printing information, acquiring an ignore crash event, acquiring an ignore overtime event and acquiring environment resource use information; and acquiring environment operation information.
S5: testing the test software list according to the test event;
in an embodiment of the present application, the testing the test software list according to the test event includes:
carrying out a system pressure test;
carrying out wireless network pressure test;
carrying out wired network pressure test;
carrying out a weak network pressure test;
performing an application pressure test;
performing multimedia pressure test;
a camera pressure test was performed.
In this embodiment of the application, when the test software list is tested according to the test event, specifically, a system pressure test, a wireless network pressure test, a wired network pressure test, a weak network pressure test, an application pressure test, a multimedia pressure test, and a camera pressure test are sequentially performed.
In this embodiment of the present application, the testing the test software list according to the test event further includes:
carrying out a first control process test;
carrying out a second control process test;
a third control procedure test is performed.
In the embodiment of the application, a first control process is added to pull up the APP in the list randomly and obtain application information such as APP window names and the like; executing the proportion and the quantity of the pseudo-random operation events of different users according to the test configuration and the APP type, wherein the proportion and the quantity of the APP type and the pseudo-random operation events are defined in advance; recording a user pseudorandom operation event which can be used as the execution process of the next return; adding a second control process to obtain the size of the APP window and monitor the window change, and determining different operation positions according to the horizontal and vertical directions of the APP window; adding a third control process, monitoring an environment operation log and resource occupation, collecting and storing the environment log when a preset problem keyword occurs, and terminating the third control process; when the third control process is terminated, the main process terminates all the sub-processes, and restarts the environment to start a new round of test; when the number of the pseudo-user random events of the APP reaches the test configuration number, switching another APP to perform stability test;
s6: and generating a test report.
In the embodiment of the application, a test report can be generated according to the test result.
According to the android environment and the android application stability testing method, a testing method for environment stability in a container is provided for the first time aiming at a kmre android compatible environment in a domestic Kylin operating system, a user pseudo-random event stability test of the kmre environment is completed by adding a first control process, and stability testing of a plurality of APPs in the environment is realized; by adding a second control process, the detection of the APP window is completed, and the stability test is supplemented; by adding the third control process, the environment log is monitored, collected and stored, the stability test can be automatically ended and restarted, manual intervention is reduced, test operation is facilitated, and efficiency is improved.
It is to be understood that the above-described embodiments of the present invention are merely illustrative of or explaining the principles of the invention and are not to be construed as limiting the invention. Therefore, any modification, equivalent replacement, improvement and the like made without departing from the spirit and scope of the present invention should be included in the protection scope of the present invention. Further, it is intended that the appended claims cover all such variations and modifications as fall within the scope and boundaries of the appended claims or the equivalents of such scope and boundaries.
Claims (8)
1. An android environment and android application stability testing method is characterized by comprising the following steps:
acquiring a test request;
acquiring a test software list;
acquiring test application information;
acquiring a test event;
testing the test software list according to the test event;
and generating a test report.
2. The android environment and android application stability testing method of claim 1, the obtaining of the test request comprising the steps of:
acquiring test time;
acquiring a test application;
acquiring the testing times of each application;
acquiring a test event proportion;
acquiring a test event type;
and performing regression testing according to the recorded testing events.
3. The android environment and android application stability testing method of claim 1, the obtaining a list of testing software includes:
acquiring an installation package of an android system in a container;
acquiring all applications in the installation package;
sequencing all the applications according to a preset sequence;
and generating a test software list according to the sorting order.
4. The android environment and android application stability testing method of claim 3, the obtaining a list of testing software further comprising the steps of:
acquiring a test application white list;
and deleting all applications in the test application white list from the test software list.
5. The android environment and android application stability testing method of claim 1, wherein the obtaining of the test application information includes the steps of:
acquiring a test application name;
acquiring a test application window name;
acquiring the size of a test application window;
acquiring a position of a test application window;
and acquiring a test application address.
6. The android environment and android application stability testing method of claim 1, the obtaining test events comprising the steps of:
acquiring the percentage of the specified touch events;
acquiring a click event;
acquiring a navigation event;
acquiring a system key event;
acquiring an activity switching event;
acquiring a seed value for generating a random event;
acquiring a detailed level of the designated print information;
acquiring an ignore crash event;
acquiring an overtime neglecting event;
acquiring environmental resource use information;
and acquiring environment operation information.
7. The android environment and android application stability testing method of claim 1, wherein the testing the list of testing software according to the test event includes steps of:
carrying out a system pressure test;
carrying out wireless network pressure test;
carrying out wired network pressure test;
carrying out a weak network pressure test;
performing an application pressure test;
performing multimedia pressure test;
a camera pressure test was performed.
8. The android environment and android application stability testing method of claim 7, wherein the testing the list of test software according to the test event further comprises:
carrying out a first control process test;
carrying out a second control process test;
a third control procedure test is performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111481706.0A CN114201392A (en) | 2021-12-06 | 2021-12-06 | Android environment and android application stability testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111481706.0A CN114201392A (en) | 2021-12-06 | 2021-12-06 | Android environment and android application stability testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114201392A true CN114201392A (en) | 2022-03-18 |
Family
ID=80650826
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111481706.0A Pending CN114201392A (en) | 2021-12-06 | 2021-12-06 | Android environment and android application stability testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114201392A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105094783A (en) * | 2014-05-19 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and device for testing Android application stability |
| CN106155907A (en) * | 2016-07-04 | 2016-11-23 | 厦门美图移动科技有限公司 | A kind of automated testing method, device and computing device |
| CN107977306A (en) * | 2016-10-25 | 2018-05-01 | 百度在线网络技术（北京）有限公司 | Method and apparatus for testing Android application stability |
| CN112100085A (en) * | 2020-11-17 | 2020-12-18 | 深圳市房多多网络科技有限公司 | Android application program stability testing method, device and equipment |
| CN112181811A (en) * | 2020-09-14 | 2021-01-05 | 麒麟软件有限公司 | Application stability testing method |
-
2021
- 2021-12-06 CN CN202111481706.0A patent/CN114201392A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105094783A (en) * | 2014-05-19 | 2015-11-25 | 腾讯科技（深圳）有限公司 | Method and device for testing Android application stability |
| CN106155907A (en) * | 2016-07-04 | 2016-11-23 | 厦门美图移动科技有限公司 | A kind of automated testing method, device and computing device |
| CN107977306A (en) * | 2016-10-25 | 2018-05-01 | 百度在线网络技术（北京）有限公司 | Method and apparatus for testing Android application stability |
| CN112181811A (en) * | 2020-09-14 | 2021-01-05 | 麒麟软件有限公司 | Application stability testing method |
| CN112100085A (en) * | 2020-11-17 | 2020-12-18 | 深圳市房多多网络科技有限公司 | Android application program stability testing method, device and equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| CN106557424B (en) | Memory test method, tested terminal, test client and system | |
| CN107562610B (en) | Method, device, terminal and medium for acquiring page loading time | |
| CN105094783B (en) | method and device for testing stability of android application | |
| WO2016095554A1 (en) | Test method, device and system for application | |
| CN106681811B (en) | Multithreading scheduling method and device based on thread pool | |
| CN107659455B (en) | Method, storage medium, device and system for Mock data of iOS (internet operating system) end | |
| CN102681938B (en) | Memory leakage detecting method and device | |
| CN110162453B (en) | Test method, test device, computer readable storage medium and computer equipment | |
| CN109543417B (en) | Vulnerability mining method and device based on Qemu platform | |
| CN112148606B (en) | Buried point test method, buried point test device, buried point test equipment and computer readable medium | |
| CN104346279A (en) | Method and device for software testing | |
| CN110768863A (en) | Scheme for simulation test of AIOT equipment | |
| CN110806965A (en) | Automatic test method, device, equipment and medium | |
| CN111966603A (en) | Memory leak detection method and device, readable storage medium and electronic equipment | |
| CN114168429A (en) | Error reporting analysis method and device, computer equipment and storage medium | |
| CN111400199B (en) | Software aging detection method and device and computer readable storage medium | |
| CN114201392A (en) | Android environment and android application stability testing method | |
| CN106484604B (en) | Application test control method and device | |
| CN105339974B (en) | Analog sensor | |
| CN111708704A (en) | Cloud real machine testing method and device, terminal and storage medium | |
| CN111258875A (en) | Interface test method and system, electronic device and storage medium | |
| CN111163309A (en) | Testing method based on behavior simulation, television equipment and storage medium | |
| CN113238901A (en) | Multi-device automatic testing method and device, storage medium and computer device | |
| CN108415822B (en) | Random test method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |