CN114265782B - Application program based shell adding tool testing method, storage medium and electronic equipment - Google Patents
Application program based shell adding tool testing method, storage medium and electronic equipment Download PDFInfo
- Publication number
- CN114265782B CN114265782B CN202111615021.0A CN202111615021A CN114265782B CN 114265782 B CN114265782 B CN 114265782B CN 202111615021 A CN202111615021 A CN 202111615021A CN 114265782 B CN114265782 B CN 114265782B
- Authority
- CN
- China
- Prior art keywords
- sample
- program
- shell adding
- programs
- test
- 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.)
- Active
Links
Images
Abstract
The disclosure provides a test method of a shell adding tool based on an application program, a storage medium and an electronic device, wherein the method comprises the following steps: acquiring a preset number of sample programs from all the shelled sample programs stored in a preset path to serve as first batch programs; respectively installing each sample program in the first batch of programs in a preset number of test devices; starting sample programs in all the test equipment, and carrying out limited time pressure test on each sample program; obtaining a crash log formed after limited time pressure measurement of each sample program; and determining the test result of the shell adding tool according to the crash log. According to the method, the steps of obtaining, installing, running and testing of the sample program are achieved in an automatic mode, the execution condition of the sample program is reflected through the crash log content, the test result of the shell adding tool is further reflected, the test period of the shell adding tool in the test process is shortened, and the test efficiency is improved.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a method for testing a shell adding tool based on an application program, a storage medium, and an electronic device.
Background
In response to popularization of smart phones, various application programs are also continuously developed to enrich actual experience of users on smart phones, application program developers upload packaged application programs to application stores for downloading and installation by users, but at the same time, packaged installation programs are also cracked by competitors or lawless persons, so that source codes written by programmers are leaked, and use safety of the application programs is not facilitated.
In the related art, an application program may be protected by a shell adding tool, and the shell adding tool generally has the following functions: the method comprises the following steps of function virtualization, dex encryption, inverse debugging, inverse injection, file verification, signature verification, resource encryption and the like, and further comprises the functions of memory verification, unity engine protection, metadata encryption, metadata name confusion and the like. After the application program is subjected to shell adding processing by the shell adding tool, the application program also needs to correctly realize the original function of the application program, and if the application program after shell adding cannot normally run or the program crashes in the using process, a problem may occur in the shell adding process; meanwhile, the variety of the model and system version of the intelligent terminal may also cause the application program after the shell is added to be incapable of running normally.
Therefore, the application program after shell adding needs to be tested to reflect possible problems of the shell adding tool, in the prior art, the test is mainly implemented manually, the application program after shell adding is respectively installed in different devices, and the stability and the adaptability of the application program after shell adding are judged according to the execution condition of the program, so that the shell adding effect of the shell adding tool is reflected. However, the test based on manual implementation consumes a lot of manpower and material resources, increases the time cost of the test, and when the program execution screenshot is used as a basis for reflecting the program problem, developers cannot intuitively know which function of the shell adding tool specifically causes the problem, thereby affecting the debugging and modifying efficiency of the shell adding tool.
Disclosure of Invention
An object of the embodiments of the present disclosure is to provide a method for testing a shelling tool based on an application program, a storage medium, and an electronic device, so as to solve the problems of long test period and low test efficiency of the shelling tool in the prior art.
The embodiment of the disclosure adopts the following technical scheme: a test method of a shell adding tool based on an application program comprises the following steps: acquiring a preset number of sample programs from all the shelled sample programs stored in a preset path to serve as first batch programs; installing each sample program in the first batch program in a preset number of test devices respectively; starting the sample programs in all the test equipment, and carrying out limited time pressure measurement on each sample program; obtaining a crash log formed by each sample program after the limited time pressure measurement; and determining the test result of the shell adding tool according to the crash log.
In some real-time examples, the sample programs in the first batch program have the same or different shell adding modes; the sample programs in the first batch program have different shell adding modes with the sample programs of other batches except the first batch program in all the sample programs.
In some real-time embodiments, each of the test devices has at least one device parameter with a value different from the values of the device parameters of the other test devices; wherein the device parameter at least comprises any one of the following: device ID, device model, operating system version number.
In some real-time embodiments, the starting the sample programs in all the test devices comprises: acquiring a package name and an activity name of the sample program; and starting the sample program according to the package name and the activity name.
In some real-time examples, before obtaining a predetermined number of sample programs as the first batch program from all the shelled sample programs stored in the preset path, the method further includes: shell the application program based on the first configuration file to form a sample program; each application program corresponds to one first configuration file, and the first configuration files at least comprise option contents used for representing a current shell adding mode, so that the shell adding tool can realize shell adding processing on the application program according to the option contents.
In some real-time examples, the obtaining a predetermined number of sample programs from all the shelled sample programs stored in the preset path as the first batch program includes: determining whether the value of a first preset node is a first preset value in a second configuration file corresponding to the shell adding tool; the first preset node is used for representing whether the shell adding tool signs the sample program or not; taking the value of a second preset node in the second configuration file as the preset path under the condition that the value of the first preset node is a first preset value; the second preset node is used for representing the storage position of the signed sample program; and under the condition that the value of the first preset node is a second preset value, controlling the shell adding tool to sign the sample program again, and storing the signed sample program to the preset path.
In some real-time examples, the determining a test result of the shelling tool from the crash log includes: determining that the test of the shelling tool passes if the crash log is empty; and under the condition that the crash log is not empty, determining an error code recorded in the crash log, and determining option content corresponding to the error code in a first configuration file of the sample program corresponding to the crash log.
In some real-time examples, after determining the test result of the shelling tool according to the crash log, the method further includes: and storing the sample program name corresponding to the crash log which is not empty in an associated manner with the option content corresponding to the error code.
The embodiment of the present disclosure further provides a storage medium storing a computer program, where the computer program is executed by a processor to implement the steps of the application-based shell tool testing method.
An embodiment of the present disclosure further provides an electronic device, which at least includes a memory and a processor, where the memory stores a computer program, and the processor implements the steps of the application-based shell tool testing method when executing the computer program on the memory.
The beneficial effects of this disclosed embodiment lie in: the steps of obtaining, installing, running and testing the sample program after the shell is added are achieved in an automatic mode, the execution condition of the sample program is reflected through the crash log content of the sample program, the test result of the shell adding tool is further reflected, the test period of the shell adding tool in the test process is greatly shortened, the test efficiency is improved, the problem of the shell adding tool can be visually displayed, debugging and modification of the shell adding tool can be more favorably carried out by a tester, and the compatibility effect of each function of the shell adding tool can be verified.
Drawings
In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present disclosure, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.
FIG. 1 is a flow chart of a method for testing an application-based shell tool according to a first embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of an electronic device in a third embodiment of the present disclosure.
Detailed Description
Various aspects and features of the disclosure are described herein with reference to the drawings.
It will be understood that various modifications may be made to the embodiments of the present application. Accordingly, the foregoing description should not be construed as limiting, but merely as exemplifications of embodiments. Other modifications will occur to those skilled in the art within the scope and spirit of the disclosure.
The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate embodiments of the disclosure and, together with a general description of the disclosure given above, and the detailed description of the embodiments given below, serve to explain the principles of the disclosure.
These and other characteristics of the present disclosure will become apparent from the following description of preferred forms of embodiment, given as a non-limiting example, with reference to the attached drawings.
It should also be understood that, although the present disclosure has been described with reference to some specific examples, a person of skill in the art shall certainly be able to achieve many other equivalent forms of the disclosure, having the characteristics as set forth in the claims and hence all coming within the field of protection defined thereby.
The above and other aspects, features and advantages of the present disclosure will become more apparent in view of the following detailed description when taken in conjunction with the accompanying drawings.
Specific embodiments of the present disclosure are described hereinafter with reference to the accompanying drawings; however, it is to be understood that the disclosed embodiments are merely exemplary of the disclosure that may be embodied in various forms. Well-known and/or repeated functions and structures have not been described in detail so as not to obscure the present disclosure with unnecessary or unnecessary detail. Therefore, specific structural and functional details disclosed herein are not to be interpreted as limiting, but merely as a basis for the claims and as a representative basis for teaching one skilled in the art to variously employ the present disclosure in virtually any appropriately detailed structure.
The specification may use the phrases "in one embodiment," "in another embodiment," "in yet another embodiment," or "in other embodiments," which may each refer to one or more of the same or different embodiments in accordance with the disclosure.
In response to popularization of smart phones, various application programs are continuously developed to enrich actual experience of users on smart phones, application program developers upload packaged application programs to application stores for downloading and installation of users, but at the same time, packaged installation programs are also cracked by competitors or lawless persons, so that source codes written by programmers are leaked, and the use safety of the application programs is not facilitated.
In the related art, an application program may be protected by a shell adding tool, and the shell adding tool generally has the following functions: the method comprises the following steps of function virtualization, dex encryption, inverse debugging, inverse injection, file verification, signature verification, resource encryption and the like, and also comprises the functions of memory verification, unity engine protection, metadata encryption, metadata name confusion and the like. After the application program is subjected to shell adding processing by the shell adding tool, the application program also needs to correctly realize the original function of the application program, and if the application program after shell adding cannot normally run or the program crashes in the using process, a problem may occur in the shell adding process; meanwhile, the variety of the model and system version of the intelligent terminal may also cause the application program after the shell is added to be incapable of running normally.
Therefore, the application program after the shell is added needs to be tested to reflect possible problems of the shell adding tool, in the prior art, the testing is mainly implemented manually, the application program after the shell is added is respectively installed in different devices, the stability and the adaptability of the application program after the shell is added are judged according to the execution condition of the program, and then the shell adding effect of the shell adding tool is reflected. However, the test based on manual implementation consumes a lot of manpower and material resources, increases the time cost of the test, and when the program execution screenshot is used as a basis for reflecting the program problem, developers cannot intuitively know which function of the shell adding tool specifically causes the problem, thereby affecting the debugging and modifying efficiency of the shell adding tool.
In order to solve the above problem, a first embodiment of the present disclosure provides an application-based shell adding tool testing method, which mainly reflects stability and adaptability of various shell adding functions of a shell adding tool according to operating conditions of a shell added application in different testing devices, and automatically executes processes of obtaining, installing, running and testing a sample program after shell adding through a program, without manually performing repeated operations, thereby greatly improving testing efficiency. Specifically, fig. 1 shows a flow chart of the test method, which mainly includes steps S10 to S50:
and S10, acquiring a preset number of sample programs from all the shelled sample programs stored in the preset path to serve as first batch programs.
And S20, respectively installing each sample program in the first batch of programs in a preset number of test devices.
The sample program may be an application program that can stably run in different intelligent device models and different operating systems after being tested by a program developer, and the application program may be an application program formed in a dynamic packaging manner (Android App BundleM, AAB), or an application program formed in another packaging manner, which is not limited in this embodiment. The shelling tool supports protection of Android abb and Android unity abb programs, wherein functions which can be realized by the Android abb include function virtualization, application code file (such as dex file) encryption, anti-debugging, anti-injection, file verification, signature verification, resource encryption and the like, functions which can be realized by the Android unity abb program include memory verification, unity engine protection, metadata encryption, metadata name confusion and the like, and a large number of test devices and a large number of applications are required to be used for verifying compatibility of each function of the shelling tool in a shelling tool test process.
Before testing, shell based on different functions can be carried out on the application program, so that a plurality of shell application programs can be used as sample programs. Specifically, the tester may adjust the content of the first configuration file, and the shell adding tool performs shell adding in a corresponding manner on the application program according to the specific content in the first configuration file, where the first configuration file at least includes option content for representing a current shell adding manner, and the tester may adjust the option content corresponding to the corresponding function according to a test requirement, so as to indicate whether the shell adding tool implements the corresponding function. It should be noted that, in order to implement automatic shell adding by the shell adding tool, it is necessary to ensure that the first configuration file and the application program to be added with the shell are placed in the same path, and then the shell adding tool is controlled by an instruction of the shell adding tool to implement shell adding operation.
In this embodiment, a predetermined number of sample programs are obtained as a first batch program from a plurality of sample programs subjected to a shelling process based on different shelling modes, so as to perform a current testing procedure. Specifically, the obtaining of the sample programs in the first batch program may be performed randomly, and the predetermined number of values may be determined according to the number of the current testing devices, so as to ensure that each sample program in the first batch program can be installed in one testing device for the stability test. When the intelligent terminals are selected, it should be ensured that each of the test devices has at least one device parameter with a value different from the values of the device parameters of other test devices, where the device parameters at least include any one of the following: device ID, device model, operating system version number, and may also include other device parameters such as device brand. In addition, the number of the test equipment for testing each time can be set according to actual conditions, and the test equipment is connected with control equipment such as a computer through a data line and the computer is allowed to control the test equipment.
In some embodiments, it may be defined that the sample programs included in the first batch program have the same or different shelling modes, and the sample programs included in the first batch program and the sample programs of other batches of all the sample programs except the first batch program are defined to have different shelling modes, so that in the tests of different batches, the stability of multiple shelling modes can be tested respectively, and the test of a single shelling mode is avoided. In practical implementation, the selection of the sample program in the first batch program may be random, and it may also be random for which test device a sample program is installed, so as to ensure the diversity of the corresponding relationship between the sample program and the test device as much as possible, and at this time, the test result obtained after the test may have better accuracy and trustability.
In some embodiments, when a first batch of samples is obtained, first, whether a value of a first preset node is a first preset value is determined in a second configuration file corresponding to a shell adding tool; the first preset node is used for representing whether the shell adding tool signs the sample program or not, the first preset value can be a specific value for representing that the shell adding tool finishes signing the sample program, and the shell adding tool can be determined to successfully add the shell to the program only after the shell adding tool finishes signing the sample program. Further, under the condition that the value of the first preset node is the first preset value, taking the value of a second preset node in a second configuration file as a preset path; the second preset node is used for representing a storage position where the signed sample program is located, and is usually a path of a file, and a corresponding sample program installation package can be obtained in the preset path when the test is started. If the value of the first preset node is the second preset value, controlling the shell adding tool to re-sign the sample program, and controlling the shell adding program to store the signed sample program to a preset path; the second preset value is used for representing a specific value of the sample program which fails to sign, and the sample program needs to be re-signed under the condition that the signature fails, and for the position where the re-signed sample program is stored, the position can be a path of any catalogue specified by a tester, as long as the installation package from which the sample program can be obtained during testing can be ensured. In practical implementation, the first preset node may be an < enable _ sign > node, the first preset value may be set to 1, the second preset value may be 0, and the second preset node may be an < apks _ path > node, where the value of the node may be a preset directory path.
And S30, starting sample programs in all the test equipment, and carrying out limited time pressure test on each sample program.
After the sample programs are installed in the testing equipment, the testing equipment can be controlled to obtain package names (package names) and activity names (activity names) of the sample programs, the sample programs in the testing equipment are sequentially started through control instructions according to the package names and the activity names of the programs in the testing equipment in a certain sequence, and limited time pressure testing is carried out on each sample program which is currently running.
Specifically, the limited-time pressure test may be implemented based on a monkey instruction in the adb tool, which mainly simulates operations of a user touching a screen, sliding, pressing a key, and the like through the monkey program to test the sample program, and the specifically-defined test time and the test intensity of the limited-time pressure test may be adjusted according to requirements. In some embodiments, before the limited-time pressure test is performed, the cache log in the current test equipment may be cleared through the control instruction, so as to further ensure the uniformity of the test environment.
And S40, acquiring a crash log formed after the limited time pressure measurement of each sample program.
And S50, determining a test result of the shell adding tool according to the crash log.
In the limited time pressure measurement process, if the program is crashed and the like, an error code representing the type of crash of the sample program is recorded in a corresponding crash log, and the generation of the crash caused by which operation is specific can be recorded at the same time.
If the content of the crash log is not empty, determining the option content corresponding to the error code in the first configuration file corresponding to the sample program according to the error code recorded in the crash log, so as to obtain which function in the shell adding tool causes the crash. It should be understood that, the corresponding relationship between the error code and the content of the option is preset, and which function in the shell adding tool causes the occurrence of crash when the function is implemented can be determined according to the content of the option corresponding to the error code, so that a tester can debug and modify the shell adding tool in a targeted manner.
In addition, the program name corresponding to the sample program whose crash log is not empty, the error code recorded in the crash log, the option content corresponding to the error code, and the like can be stored in an associated manner, and in addition, the device parameters of the corresponding testing device can be further stored for reference.
In practical implementation, after the pressure test of the sample programs included in the first batch program is finished within the limited time, the sample programs are unloaded from the test equipment through the control instruction, then a predetermined number of sample programs are selected from all the sample programs as new first batch programs, and the test process is repeated until all the sample programs are tested.
The embodiment realizes the steps of obtaining, installing, running and testing the sample program after the shell is added in an automatic mode, reflects the execution condition of the sample program through the crash log content of the sample program, further reflects the test result of the shell adding tool, greatly shortens the test period of the shell adding tool in the test process, improves the test efficiency, can visually display the problem of the shell adding tool, is more favorable for a tester to debug and modify the shell adding tool, and is favorable for verifying the compatibility effect of each function of the shell adding tool.
A second embodiment of the present disclosure provides a storage medium, which is installable in a computer or other control device, the computer is connected to a plurality of test devices through a data line, and can implement control over a shell adding tool and the test devices, and is specifically a computer-readable medium storing a computer program, and when the computer program is executed by a processor, the method provided in any embodiment of the present disclosure is implemented, including the following steps S31 to S35:
s31, obtaining a preset number of sample programs from all the shelled sample programs stored in a preset path to serve as first batch programs;
s32, respectively installing each sample program in the first batch of programs in a preset number of test devices;
s33, starting sample programs in all the test equipment, and carrying out limited time pressure test on each sample program;
s34, obtaining a crash log formed after the limited time pressure measurement of each sample program;
and S35, determining a test result of the shell adding tool according to the crash log.
Specifically, the sample programs in the first batch program have the same or different shell adding modes; the shell adding mode is different between the sample procedure in the first batch procedure and the sample procedures of other batches except the first batch procedure in all the sample procedures.
Specifically, each test device has at least one device parameter with a value different from the values of the device parameters of the other test devices; wherein, the device parameter at least comprises any one of the following: device ID, device model, operating system version number.
When the computer program is executed by the processor to start the sample programs in all the test devices, the processor specifically executes the following steps: acquiring a package name and an activity name of a sample program; the sample program is started based on the package name and the activity name.
Before the computer program is executed by the processor to obtain a predetermined number of sample programs as a first batch program from all the shelled sample programs stored in the preset path, the following steps are further executed by the processor: shell the application program based on the first configuration file to form a sample program; each application program corresponds to a first configuration file, and the first configuration file at least comprises option content used for representing the current shell adding mode, so that the shell adding tool can realize shell adding processing on the application program according to the option content.
When the computer program is executed by the processor to obtain a predetermined number of sample programs as first batch programs from all the shelled sample programs stored in the preset path, the processor specifically executes the following steps: determining whether the value of the first preset node is a first preset value or not in a second configuration file corresponding to the shell adding tool; the first preset node is used for representing whether the shell adding tool signs the sample program or not; taking the value of a second preset node in a second configuration file as a preset path under the condition that the value of the first preset node is a first preset value; the second preset node is used for representing the storage position of the signed sample program; and under the condition that the value of the first preset node is a second preset value, controlling the shell adding tool to sign the sample program again, and storing the signed sample program to a preset path.
When the computer program is executed by the processor according to the crash log and the test result of the shell adding tool is determined, the following steps are specifically executed by the processor: determining that the test of the shell adding tool passes under the condition that the crash log is empty; and under the condition that the crash log is not empty, determining an error code recorded in the crash log, and determining option content corresponding to the error code in a first configuration file of a sample program corresponding to the crash log.
After the computer program is executed by the processor to determine the test result of the shell adding tool according to the crash log, the computer program is further executed by the processor to perform the following steps: and storing the sample program name corresponding to the crash log which is not empty in a correlated manner and the option content corresponding to the error code.
The embodiment realizes the steps of obtaining, installing, running and testing the sample program after the shell is added in an automatic mode, reflects the execution condition of the sample program through the crash log content of the sample program, further reflects the test result of the shell adding tool, greatly shortens the test period of the shell adding tool in the test process, improves the test efficiency, can visually display the problem of the shell adding tool, is more favorable for a tester to debug and modify the shell adding tool, and is favorable for verifying the compatibility effect of each function of the shell adding tool.
The third embodiment of the present disclosure provides an electronic device, which may be a computer or other control device, and may be connected to a plurality of test devices through data lines, and may implement control over a shell adding tool and the test devices, and its structural schematic diagram is shown in fig. 2, and includes at least a memory 100 and a processor 200, where the memory 100 stores a computer program, and the processor 200 implements the method provided in any embodiment of the present disclosure when executing the computer program on the memory 100. Illustratively, the electronic device computer program steps are as follows S41 to S45:
s41, obtaining a preset number of sample programs from all the shelled sample programs stored in a preset path to serve as first batch programs;
s42, respectively installing each sample program in the first batch of programs in a preset number of test devices;
s43, starting sample programs in all the test equipment, and carrying out limited time pressure test on each sample program;
s44, obtaining a crash log formed after the limited time pressure measurement of each sample program;
and S45, determining the test result of the shell adding tool according to the crash log.
Specifically, the sample programs in the first batch of programs have the same or different shell adding modes; the shell adding mode is different between the sample procedure in the first batch procedure and the sample procedures of other batches except the first batch procedure in all the sample procedures.
Specifically, each test device has at least one device parameter with a value different from the values of the device parameters of the other test devices; wherein, the equipment parameter at least comprises any one of the following: device ID, device model, operating system version number.
When the processor executes the sample program stored in the memory and used for starting all the test devices, the following computer programs are specifically executed: acquiring a package name and an activity name of a sample program; the sample program is started based on the package name and the activity name.
The processor further executes the following computer program before executing a predetermined number of sample programs stored on the memory among all the shelled sample programs stored in the preset path as the first batch program: shell the application program based on the first configuration file to form a sample program; each application program corresponds to a first configuration file, and the first configuration file at least comprises option content for representing a current shell adding mode, so that the shell adding tool can add shells to the application programs according to the option content.
When the processor acquires a predetermined number of sample programs as a first batch program from all the shelled sample programs stored in the memory in a preset path, the following computer programs are specifically executed: determining whether the value of the first preset node is a first preset value or not in a second configuration file corresponding to the shell adding tool; the first preset node is used for representing whether the shell adding tool signs the sample program or not; taking the value of a second preset node in a second configuration file as a preset path under the condition that the value of the first preset node is a first preset value; the second preset node is used for representing the storage position of the signed sample program; and under the condition that the value of the first preset node is a second preset value, controlling the shell adding tool to sign the sample program again, and storing the signed sample program to a preset path.
When the processor executes the test result of the shell adding tool, which is stored in the memory and determined according to the crash log, the following computer program is specifically executed: determining that the test of the shell adding tool passes under the condition that the crash log is empty; and under the condition that the crash log is not empty, determining an error code recorded in the crash log, and determining option content corresponding to the error code in a first configuration file of a sample program corresponding to the crash log.
After the processor executes the test result of the shelling tool determined from the crash log stored in the memory, the following computer program is executed: and storing the sample program name corresponding to the crash log which is not empty in a correlated manner and the option content corresponding to the error code.
The embodiment realizes the steps of obtaining, installing, running and testing the sample program after the shell is added in an automatic mode, reflects the execution condition of the sample program through the crash log content of the sample program, further reflects the test result of the shell adding tool, greatly shortens the test period of the shell adding tool in the test process, improves the test efficiency, can visually display the problem of the shell adding tool, is more favorable for a tester to debug and modify the shell adding tool, and is favorable for verifying the compatibility effect of each function of the shell adding tool.
While the present disclosure has been described in detail with reference to the embodiments, the present disclosure is not limited to the specific embodiments, and those skilled in the art can make various modifications and alterations based on the concept of the present disclosure, and the modifications and alterations should fall within the scope of the present disclosure as claimed.
Claims (9)
1. A method for testing a shell adding tool based on an application program is characterized by comprising the following steps:
obtaining a preset number of sample programs from all the shelled sample programs stored in a preset path as first batch programs;
installing each sample program in the first batch program in a preset number of test devices respectively;
starting the sample programs in all the test equipment, and carrying out limited time pressure measurement on each sample program;
obtaining a crash log formed by each sample program after the limited time pressure measurement;
determining a test result of the shell adding tool according to the crash log;
before acquiring a predetermined number of sample programs as a first batch program from all the shelled sample programs stored in the preset path, the method further comprises the following steps:
shell the application program based on the first configuration file to form a sample program;
each application program corresponds to one first configuration file, and the first configuration files at least comprise option contents used for representing a current shell adding mode, so that the shell adding tool can realize shell adding processing on the application program according to the option contents.
2. The shelling tool testing method of claim 1 wherein said sample programs in said first batch program have the same or different shelling styles therebetween;
the sample programs in the first batch program have different shell adding modes with the sample programs of other batches except the first batch program in all the sample programs.
3. The casing tool testing method of claim 1, wherein each of the test devices has at least one device parameter having a value different from the values of the device parameters of the other test devices;
wherein the device parameter at least comprises any one of the following:
device ID, device model, operating system version number.
4. The method as claimed in claim 1, wherein said initiating said sample routine in all of said test devices comprises:
acquiring a package name and an activity name of the sample program;
and starting the sample program according to the package name and the activity name.
5. The method for testing a shelling tool as defined in claim 1 wherein said obtaining a predetermined number of sample programs as a first batch program from all of the shelled sample programs stored in the predetermined path comprises:
determining whether the value of a first preset node is a first preset value or not in a second configuration file corresponding to the shell adding tool; the first preset node is used for representing whether the shell adding tool signs the sample program or not;
taking the value of a second preset node in the second configuration file as the preset path under the condition that the value of the first preset node is a first preset value; the second preset node is used for representing the storage position of the signed sample program;
and under the condition that the value of the first preset node is a second preset value, controlling the shell adding tool to sign the sample program again, and storing the signed sample program to the preset path.
6. The method for testing a shelling tool as defined in claim 1, wherein said determining a test result for said shelling tool based on said crash log comprises:
determining that the test of the shelling tool passes if the crash log is empty;
and under the condition that the crash log is not empty, determining an error code recorded in the crash log, and determining option content corresponding to the error code in a first configuration file of the sample program corresponding to the crash log.
7. The method of claim 6, wherein after determining the test result of the shelling tool from the crash log, further comprising:
and storing the sample program name corresponding to the crash log which is not empty in an associated manner with the option content corresponding to the error code.
8. A storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the application-based shelling tool testing method of any of claims 1-7.
9. An electronic device comprising at least a memory, a processor, the memory having a computer program stored thereon, wherein the processor, when executing the computer program on the memory, implements the steps of the application based shelling tool testing method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111615021.0A CN114265782B (en) | 2021-12-27 | 2021-12-27 | Application program based shell adding tool testing method, storage medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111615021.0A CN114265782B (en) | 2021-12-27 | 2021-12-27 | Application program based shell adding tool testing method, storage medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114265782A CN114265782A (en) | 2022-04-01 |
| CN114265782B true CN114265782B (en) | 2023-01-24 |
Family
ID=80830530
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111615021.0A Active CN114265782B (en) | 2021-12-27 | 2021-12-27 | Application program based shell adding tool testing method, storage medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114265782B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104050075A (en) * | 2013-03-11 | 2014-09-17 | 百度国际科技（深圳）有限公司 | Test method and device for Andriod application program |
| CN107273298A (en) * | 2017-07-07 | 2017-10-20 | 北京深思数盾科技股份有限公司 | A kind of method of testing of shell adding instrument, apparatus and system |
| WO2017219589A1 (en) * | 2016-06-19 | 2017-12-28 | 乐视控股（北京）有限公司 | Method and system for processing program crash message |
-
2021
- 2021-12-27 CN CN202111615021.0A patent/CN114265782B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104050075A (en) * | 2013-03-11 | 2014-09-17 | 百度国际科技（深圳）有限公司 | Test method and device for Andriod application program |
| WO2017219589A1 (en) * | 2016-06-19 | 2017-12-28 | 乐视控股（北京）有限公司 | Method and system for processing program crash message |
| CN107273298A (en) * | 2017-07-07 | 2017-10-20 | 北京深思数盾科技股份有限公司 | A kind of method of testing of shell adding instrument, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114265782A (en) | 2022-04-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109302522B (en) | Test method, test device, computer system, and computer medium | |
| US9355017B2 (en) | Automated error checking system for a software application and method therefor | |
| CN106598835B (en) | Application testing method, device and system | |
| CN107659455B (en) | Method, storage medium, device and system for Mock data of iOS (internet operating system) end | |
| CN109634648B (en) | Method and device for rapidly switching SDK network interface environment | |
| CN109543417B (en) | Vulnerability mining method and device based on Qemu platform | |
| CN112052169A (en) | Test management method, system, device and computer readable storage medium | |
| CN110597544A (en) | Software system upgrading method and device | |
| CN107861875B (en) | Simulation method and system for hybrid mobile application | |
| CN111563032A (en) | APP debugging method and device, computer equipment and storage medium | |
| CN110928777B (en) | Test case processing method, device, equipment and storage medium | |
| CN114265782B (en) | Application program based shell adding tool testing method, storage medium and electronic equipment | |
| CN111128139B (en) | Non-invasive voice test method and device | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| CN112650689A (en) | Test method, test device, electronic equipment and storage medium | |
| CN105339974B (en) | Analog sensor | |
| CN109683929A (en) | Test method, system and storage medium based on FOTA system update | |
| CN114880244A (en) | Application testing method and device, storage medium and electronic equipment | |
| CN115934503A (en) | Program testing method, device, equipment and storage medium | |
| CN112346994A (en) | Test information correlation method and device, computer equipment and storage medium | |
| CN112988561B (en) | Method, device, server and storage medium for detecting display configuration code | |
| CN112463500A (en) | Hard disk partition testing method, device, equipment and storage medium | |
| CN115309594A (en) | Program automatic test method, device, equipment and medium | |
| CN113971035A (en) | Method for checking differential upgrade package and computer equipment | |
| CN112346984A (en) | Web end comprehensive test method and system |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 100193 5th floor 510, No. 5 Building, East Yard, No. 10 Wangdong Road, Northwest Haidian District, Beijing Applicant after: Beijing Shendun Technology Co.,Ltd. Address before: 100193 5th floor 510, No. 5 Building, East Yard, No. 10 Wangdong Road, Northwest Haidian District, Beijing Applicant before: BEIJING SENSESHIELD TECHNOLOGY Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |