CN109726104B - Test packet generation method of mobile terminal, test terminal and storage medium - Google Patents
Test packet generation method of mobile terminal, test terminal and storage medium Download PDFInfo
- Publication number
- CN109726104B CN109726104B CN201810463140.0A CN201810463140A CN109726104B CN 109726104 B CN109726104 B CN 109726104B CN 201810463140 A CN201810463140 A CN 201810463140A CN 109726104 B CN109726104 B CN 109726104B
- Authority
- CN
- China
- Prior art keywords
- test
- test packet
- unique identifier
- construction
- source code
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 260
- 238000000034 method Methods 0.000 title claims abstract description 55
- 238000010276 construction Methods 0.000 claims abstract description 82
- 230000010354 integration Effects 0.000 claims abstract description 50
- 238000012986 modification Methods 0.000 claims description 15
- 230000004048 modification Effects 0.000 claims description 15
- 230000002085 persistent effect Effects 0.000 claims description 15
- 238000004891 communication Methods 0.000 claims description 12
- 238000013507 mapping Methods 0.000 claims description 12
- 238000004590 computer program Methods 0.000 claims description 9
- 238000013515 script Methods 0.000 claims description 4
- 230000002349 favourable effect Effects 0.000 abstract 1
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000012544 monitoring process Methods 0.000 description 3
- 238000004806 packaging method and process Methods 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 238000009434 installation Methods 0.000 description 2
- 238000012856 packing Methods 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 1
- 230000000739 chaotic effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011981 development test Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The invention discloses a test packet generation method of a mobile terminal, the test terminal and a storage medium, wherein the method comprises the following steps: obtaining a test packet from the continuous integration tool; acquiring a unique identifier and a construction parameter of each test packet; configuring a corresponding folder for each test packet according to the unique identifier; storing all the test packages into corresponding folders respectively; naming the test packages stored in the folder according to the unique identifier and the construction parameters of each test package. The invention names the test packets by using the unique identifiers and the construction parameters of the test packets, and simultaneously, the test packets are respectively stored in the folders corresponding to the unique identifiers, which is favorable for distinguishing different test packets, is convenient for engineers to quickly position the test packets, saves the search time and has ordered storage management of the test packets.
Description
Technical Field
The present invention relates to the field of software testing, and in particular, to a method for generating a test packet for a mobile terminal, a test terminal, and a computer readable storage medium.
Background
The popularity of mobile terminals benefits in large part from the mobile terminal's application extensibility, which means that a wide variety of applications can be downloaded from the application marketplace to extend the functionality of the mobile terminal. In order to realize the function expansion of the mobile terminal, development test is required to be performed on the application. When the application is developed and tested, various compiled test packages need to be stored. The existing test packets are stored in a chaotic manner, and when the test packets are in a problem, engineers cannot quickly locate the test packets, so that the search time is consumed, and the management of the test packets is disordered.
Disclosure of Invention
The invention mainly aims to provide a test packet generation method of a mobile terminal, the test terminal and a computer readable storage medium, and aims to solve the technical problem that a user cannot quickly locate a test packet due to disordered test packet storage.
In order to achieve the above object, the present invention provides a method for generating a test packet for a mobile terminal, including the steps of:
obtaining a test packet from the continuous integration tool;
acquiring a unique identifier and a construction parameter of each test packet;
configuring a corresponding folder for each test packet according to the unique identifier;
storing all the test packages into corresponding folders respectively;
naming the test packages stored in the folder according to the unique identifier and the construction parameters of each test package.
Optionally, the construction parameters include a construction time stamp, a construction version number, and a construction number of the test packet;
the step of naming the test packages stored in the folder according to the unique identifier and the construction parameters of each test package comprises the following steps:
arranging the unique identifier, the construction time stamp, the construction version number and the construction number according to a preset sequence to form an arrangement character string;
and setting the arrangement character string as the name of the test packet.
Optionally, before the step of obtaining the test packet from the persistent integration tool, the method further includes:
acquiring a configuration file corresponding to a source code to be compiled;
receiving a configuration request of a user, and changing the configuration file according to the configuration request;
and sending the source code after the configuration file modification to the continuous integration tool so as to control the continuous integration tool to compile and package the source code after the configuration file modification to generate the test package.
Optionally, the configuration request includes a certificate type configured by the user and mapping relation data between the certificate type and a preset variable;
the step of changing the configuration file according to the configuration request includes:
acquiring certificate information in the configuration file;
searching a preset variable corresponding to the certificate type configured by the user from the mapping relation data between the certificate type and the preset variable;
and replacing the certificate information in the configuration file with the searched preset variable.
Optionally, the persistent integration tool includes Jenkins, the test package includes an IPA package, and the configuration file includes a pbxpro file; the step of controlling the persistent integration tool to compile and package the source code after the configuration file modification to generate the test packet includes:
controlling the Jenkins to compile and pack the source code after the pbxpro file is changed so as to generate the IPA package;
the step of replacing the certificate information in the configuration file with the searched preset variable comprises the following steps:
and replacing certificate information in the pbxpro file by using the searched preset variable as a script.
Optionally, the step of controlling the persistent integration tool to compile and package the source code after the configuration file modification to generate the test packet includes:
controlling the continuous integration tool to compile the source code after the configuration file is changed;
the method comprises the steps of obtaining version information when source codes after configuration files are changed are compiled, and storing the version information as a document file, wherein the version information comprises the unique identifier and the construction information;
controlling the continuous integration tool to pack the document file and the compiled source code so as to generate the test packet;
the step of obtaining the unique identifier and the construction parameter of each test packet comprises the following steps:
extracting the document file from each of the test packages;
and searching the unique identifier and the construction parameters from the document file of each test packet.
Optionally, after the step of naming the test packages corresponding to the test packages stored in the folder according to the unique identifier of each test package and the construction parameter, the method further includes:
sending the named test packets to a server so that the server generates a corresponding two-dimensional code for each named test packet;
after the preset time, sending a clearing instruction to the server so that the server clears the corresponding test packet according to the clearing instruction.
In addition, in order to achieve the above object, the present invention further provides a test terminal, including:
the first acquisition module is used for acquiring the test packet from the continuous integration tool;
the second acquisition module is used for acquiring the unique identifier and the construction parameters of each test packet;
the configuration module is used for configuring a corresponding folder for each test packet according to the unique identifier;
the storage module is used for respectively storing all the test packets into corresponding folders;
and the naming module is used for naming the test packages stored in the folder correspondingly according to the unique identifier of each test package and the construction parameters.
In addition, to achieve the above object, the present invention also provides a test terminal, including: the mobile terminal test packet generating method comprises the steps of a communication module, a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the computer program is executed by the processor to realize the test packet generating method of the mobile terminal.
In addition, in order to achieve the above object, the present invention also provides a computer-readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the test packet generating method of a mobile terminal as described above.
The invention provides a test packet generation method of a mobile terminal, the test terminal and a computer readable storage medium, wherein the test packet is obtained from a continuous integration tool; acquiring a unique identifier and a construction parameter of each test packet; configuring a corresponding folder for each test packet according to the unique identifier; storing all the test packages into corresponding folders respectively; naming the test packages stored in the folder according to the unique identifier and the construction parameters of each test package. Therefore, the test packages with different unique identifiers are respectively stored in different folders, and the test packages are renamed according to the unique identifiers and the construction parameters of all the test packages, so that the classified storage and the differentiated archiving of the test packages are facilitated, engineers can conveniently and quickly position the test packages, the searching time is saved, and the storage management of the test packages is ordered.
Drawings
FIG. 1 is a schematic structural diagram of a test terminal according to an embodiment of the present invention;
FIG. 2 is a flowchart of a first embodiment of a method for generating a test packet of a mobile terminal according to the present invention;
fig. 3 is a detailed flowchart of step S50 in the second embodiment of the test packet generating method of the mobile terminal according to the present invention;
FIG. 4 is a flowchart of a third embodiment of a method for generating a test packet of a mobile terminal according to the present invention;
fig. 5 is a schematic diagram of a refinement flow of step S20 in a third embodiment of a test packet generating method of a mobile terminal according to the present invention;
fig. 6 is a detailed flowchart of step S02 in a fourth embodiment of the test packet generating method of the mobile terminal according to the present invention;
fig. 7 is a schematic diagram of functional modules of the test terminal according to the present invention.
The achievement of the objects, functional features and advantages of the present invention will be further described with reference to the accompanying drawings, in conjunction with the embodiments.
Detailed Description
It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention.
Referring to fig. 1, fig. 1 is a schematic hardware structure of a test terminal 100 according to various embodiments of the present invention, and in the test terminal 100 provided by the present invention, components such as a communication module 10, a memory 20, and a processor 30 may be included. The test terminal 100 may be a computer, a server, a dedicated test terminal, etc., and the test terminal 100 may also be connected in communication with other servers. The test terminal 100 may be locally installed with persistent integration tools such as Jenkins, gitLab CI, teamCity, and the like. The processor 30 is connected to the memory 20 and the communication module 10, respectively, and a computer program is stored in the memory 20, and the computer program is executed by the processor 30 at the same time.
The communication module 10 is connectable to an external communication device via a network. The communication module 10 may receive a request sent by an external communication device, and may also send a request, an instruction, and information to the external communication device. The external communication device may be a server or other test terminal.
The memory 20 is used for storing software programs and various data. The memory 20 may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function (such as acquiring a unique identifier), and the like; the storage data area may include a database, may store data or information created according to the use of the test terminal 100, and the like. In addition, the memory 20 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid-state storage device.
The processor 30, which is a control center of the test terminal 100, connects various parts of the entire test terminal 100 using various interfaces and lines, performs various functions of the test terminal 100 and processes data by running or executing software programs and/or modules stored in the memory 20, and calling data stored in the memory 20, thereby performing overall monitoring of the test terminal 100. Processor 30 may include one or more processing units; preferably, the processor 30 may integrate an application processor that primarily handles operating systems, user interfaces, applications, etc., with a modem processor that primarily handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 30.
Although not shown in fig. 1, the test terminal 100 may further include a circuit control module for connecting to a power source to ensure normal operation of other components. The test terminal can further comprise a display module, wherein the display module can be used for displaying source codes to be compiled and monitoring the compiling and packing progress of the continuous integration tool. Those skilled in the art will appreciate that the configuration of the test terminal 100 shown in fig. 1 does not constitute a limitation of the test terminal 100, and may include more or fewer components than shown, or may combine certain components, or may have a different arrangement of components.
Based on the above hardware structure, various embodiments of the method of the present invention are presented.
Referring to fig. 2, in a first embodiment of the test packet generating method of the mobile terminal of the present invention, the method includes the steps of:
step S10, obtaining a test packet from a continuous integration tool;
CI (Continuous Integration ) is suitable for use in software development practice, verified by automated construction by each software developer, and integrated errors can be found as early as possible. The Jenkins platform is described below as an example.
The Jenkins platform is a continuous integration tool based on Java development and is used for monitoring continuous repeated work, and can compile preset executable files or source codes in the development process and then make the test package by combining necessary design documents, such as using instructions. The installation position of the Jenkins platform can be set according to actual implementation, for example, the Jenkins platform can be installed on a public server or a test terminal.
The controller of the test terminal can monitor the state of the Jenkins platform, can acquire the test packet in real time when the test packet with the compiled and packaged completion is generated, and can acquire the test packet with the compiled and packaged completion in preset time from the Jenkins platform at intervals of preset time. The test Package may be an IPA (iPhone Application, apple application) file, or an apk (Android Package) file.
Step S20, obtaining a unique identifier and a construction parameter of each test packet;
each test packet will leave version information corresponding to each test packet in the compiling process, and the controller can acquire the version information, wherein the version information is mainly divided into identification information and construction information, and the identification information is a unique identifier, and the unique identifier can be used for distinguishing different test packets or application programs. The build information may include a build timestamp, an upload timestamp, a test packet size, a build version number, a project identification to which the test packet belongs, a project name to which the test packet belongs, a build number, and the like of the test packet. The construction time stamp, the construction version number and the construction number can also be used as construction parameters. In addition, the construction parameters may further include the name of the item and/or the identifier of the test package application system, such as IOS or Android (Android) systems.
Step S30, configuring a corresponding folder for each test packet according to the unique identifier;
step S40, storing all the test packets into corresponding folders respectively;
taking continuous integration of IPA test packages by using Jenkins platform as an example for explanation, at this time, the unique identifier is bound, bound refers to Bundle Identifier, after the account of developer is registered, it can be generated when the certificate is created by registering account App ID of apple company, bound refers to unique identifier for distinguishing different IPA test packages, and bound and test package have one-to-one correspondence. When configuring the folder for each test package, the suffix name of the bound may be used as the folder name, and then all test packages are placed in the configured folder. If multiple test packages are placed in the same folder, it is indicated that the test packages are identical in bound and are different versions of the same test package. The folder may also store only the latest test package of the test package iterations. Or other word forming algorithms can be used for naming folders, so that different test packages can be classified and stored.
And step S50, naming the test packages stored in the folders correspondingly according to the unique identifier and the construction parameters of each test package.
In performing test package naming, unique identifiers and build parameters may be utilized for combining. For example, any several construction parameters may be selected from the construction parameters as naming parameters for naming the test package, and then the naming parameters are combined with the unique identifier in a string, and the combined string is the name of the test package. One character string can be selected from each construction parameter according to the compiling sequence of the test packet, and then the unique identifier and the character strings selected from all construction parameters are combined to obtain the name of the test packet. For example, the compilation order of the current test package is 3, then the 3 rd bit string of each build parameter may be selected and then combined with the unique identifier.
The embodiment obtains the test packet from the continuous integration tool; acquiring a unique identifier and a construction parameter of each test packet; configuring a corresponding folder for each test packet according to the unique identifier; storing all the test packages into corresponding folders respectively; naming the test packages stored in the folder according to the unique identifier and the construction parameters of each test package. Therefore, the test packages with different unique identifiers are respectively stored in different folders, and the test packages are renamed according to the unique identifiers and the construction parameters of all the test packages, so that the classified storage of the test packages is facilitated, the different test packages are favorably distinguished and filed, engineers can conveniently and quickly locate the test packages, the searching time is saved, and the storage management of the test packages is ordered.
Referring to fig. 3, a second embodiment of the test packet generating method of the mobile terminal is proposed based on the first embodiment of the test packet generating method of the mobile terminal of the present invention, in which the construction parameters include a construction time stamp, a construction version number, and a construction number of the test packet; the step S50 includes:
step S51, arranging the unique identifier, the construction time stamp, the construction version number and the construction number according to a preset sequence to form an arrangement character string;
step S52, setting the arrangement string as the name of the test packet.
The construction time stamp refers to construction time and date of the test packet, the construction version number (currentversion) refers to an external version number of the current iteration, and the construction version number (build) can be used for distinguishing each version, is generally towards a developer, cannot be seen to the outside, is an internal version number, and when the test packet version is updated, the construction number and the construction version number are higher than those of the previous test packet.
The character strings may be arranged randomly according to a predetermined sequence, or may be combined according to a fixed sequence. Assuming a random string combination, the naming of all test packages will include the elements unique identifier and build parameters, but the order of arrangement may be different. Another way is to use a fixed way, taking the unique identifier, the construction time stamp, the construction version number and the construction number as examples, assuming that the unique identifier is pin gan, the construction time stamp is 180411, the construction version number is 1.0 and the construction number is 12, then the name of the test packet obtained by combining the character strings may be pin gan-180411-1.0-12 or pin gan1804111.012. The naming scheme of the test package is further refined, so that a user can quickly locate a specific test package when finding out a problem of the test package.
Referring to fig. 4, a third embodiment of the test packet generating method of the mobile terminal according to the present invention is provided based on the first embodiment of the test packet generating method of the mobile terminal according to the present invention, in this embodiment, before step S10, the method further includes:
step S01, acquiring a configuration file corresponding to a source code to be compiled;
the source code to be compiled may be automatically downloaded locally at a fixed time of day for the continuous integration tool to compile the source code to be compiled. The latest source code can be obtained from the source code editor as the source code to be compiled when the program issuing instruction is received. The source code to be compiled is correspondingly provided with a configuration file, and the configuration file and the source code have uniqueness. The configuration file can be an xml file, a json file or a pbxproj file, the configuration information is a file which carries out different configurations on different objects, and various information is counted in the configuration information.
Step S02, receiving a configuration request of a user, and changing the configuration file according to the configuration request;
different test pack users have different configuration requirements, such as different test pack certificate types, or special requirements in the test pack compiling and packing process, and the like. The information in the configuration file can be modified according to a configuration request of a user, wherein the configuration request can comprise the information to be replaced and the association relationship between the information to be replaced and the original information, and can also comprise the position and the like of the original information.
And step S03, the source code after the configuration file modification is sent to the continuous integration tool, so that the continuous integration tool is controlled to compile and package the source code after the configuration file modification to generate the test packet.
Taking the Jenkins platform to generate the IPA test packet as an example for explanation, the Jenkins may be controlled to compile and package the source code after the pbxpro file is changed to generate the IPA packet.
In this embodiment, the process of generating the test package is to compile the source code first, then obtain version information generated in the compiling process, and make the version information into a document file and package the document file together with the compiled source code. It should be noted that, the version information includes a unique identifier and a construction parameter, and when the unique identifier and the construction parameter of each test packet are obtained, a corresponding extraction operation may be performed from the document file.
Optionally, the step S03 may include the steps of:
controlling the continuous integration tool to compile the source code after the configuration file is changed;
the method comprises the steps of obtaining version information when source codes after configuration files are changed are compiled, and storing the version information as a document file, wherein the version information comprises the unique identifier and the construction information;
and controlling the continuous integration tool to package the document file and the compiled source code so as to generate the test package.
Referring to fig. 5 together, fig. 5 is a detailed flowchart of the step S20, and the step S20 may include the steps of:
step S21, extracting the document file from each test packet;
and step S22, searching the unique identifier and the construction parameters from the document file of each test packet.
Referring to fig. 6, a fourth embodiment of the test packet generating method of the mobile terminal is proposed based on a third embodiment of the test packet generating method of the mobile terminal, in which the configuration request includes a certificate type configured by the user and mapping relationship data between the certificate type and a preset variable;
the step S02 may include the steps of:
step S04, certificate information in the configuration file is obtained;
it should be noted that, the certificate information may include a unique identifier, for example, bound, and may also be descriptive file name enumeration, certificate name enumeration, and the like.
Step S05, searching a preset variable corresponding to the certificate type configured by the user from the mapping relation data between the certificate type and the preset variable;
step S06, replacing the certificate information in the configuration file with the searched preset variable.
Currently, when packaging is performed by using a continuous integration tool, the certificate type of the test package is often limited, and some certificate types often fail to be compiled, so that all requirements of users cannot be met. For example, when Jenkins are used as a continuous integration tool to compile and package, only an enterprise certificate issue (Release) package or an apple application store issue (appstore Release) package can be generated, a personal certificate Debug (Debug) package can not be generated, continuous integration compilation failure can sometimes be caused even due to different configuration certificates, and the problem can not be solved through Xcode.
To address this issue, the user's configuration may be received and the credential information in the configuration file altered prior to continued integration. Firstly, setting corresponding preset variables for all certificate types, then determining the certificate types required by a user, then searching the preset variables corresponding to the certificate types required by the user from mapping relation data of all the certificate types and the corresponding preset variables, finally replacing the searched preset variables as scripts and smoothly packaging the certificate information in the configuration file by using a continuous integration tool.
Assuming the persistent integration tool is Jenkins and the packaged test package is IPA package, alternative credential information may include bound, descriptive file name enumeration, credential name enumeration, and so forth. The mapping relationship data may be that the enterprise certificate type corresponds to a preset variable a, the apple application Store APP Store certificate corresponds to a preset variable B, and the individual push certificate corresponds to a preset variable C, wherein the preset variables A, B and C are different from each other.
Because the certificate information in the configuration file information is replaced by a preset variable, the continuous integration tool can not cause the condition of compiling failure due to different configuration certificates, and can perfectly support all certificate types. In addition, different certificate types are distinguished through variables, so that the supportable certificate types of the test packet can be obtained after the test packet is packaged, verification of different service scenes is facilitated, and the working efficiency is improved.
Optionally, in other embodiments, the step S50 further includes:
sending the named test packets to a server so that the server generates a corresponding two-dimensional code for each named test packet;
by sending the named test packages to the server, automatic release of the test packages is achieved. The generated two-dimensional code can be displayed on the continuous integration tool, so that all users can conveniently perform scanning installation test.
Further, after the preset time, a clearing instruction may be sent to the server, so that the server clears the corresponding test packet according to the clearing instruction.
For example, the preset time is set to 3 days, that is, the storage time of the named test packet from the date of distribution is 3 days, and the server can automatically clear the uploaded test packet after the preset time, or send a clearing instruction to the server to clear the corresponding test packet through the issued test terminal, so that sufficient memory space of the server is ensured, and real-time update of the test packet on the server is also ensured. When the test packet is cleared, the corresponding two-dimensional code is also automatically invalidated and cleared.
Referring to fig. 7, the present invention further proposes a test terminal 100, including:
a first obtaining module 10, configured to obtain a test packet from the persistent integration tool;
a second obtaining module 20, configured to obtain a unique identifier and a construction parameter of each test packet;
a configuration module 30, configured to configure a corresponding folder for each test packet according to the unique identifier;
the storage module 40 is used for respectively storing all the test packets into corresponding folders;
a naming module 50, configured to name the test packages stored in the folders according to the unique identifier and the construction parameters of each test package.
Optionally, in another embodiment, the build parameters include a build timestamp, a build version number, and a build number of the test packet;
the naming module 50 includes:
an arrangement unit 51 for arranging the unique identifier, the construction time stamp, the construction version number, and the construction number in a preset order to form an arrangement character string;
a setting unit 52, configured to set the arrangement string as the name of the test packet.
Optionally, in yet another embodiment, the test terminal 100 further includes:
a third obtaining module 60, configured to obtain a configuration file corresponding to the source code to be compiled;
a modification module 70, configured to receive a configuration request from a user, and modify the configuration file according to the configuration request;
and the control module 80 is configured to send the source code after the configuration file is changed to the persistent integration tool, so that the persistent integration tool is controlled to compile and package the source code after the configuration file is changed to generate the test packet.
Optionally, in a further embodiment, the configuration request includes a certificate type configured by the user and mapping relationship data between the certificate type and a preset variable;
the modification module 70 includes:
an acquisition unit 71 for acquiring certificate information in the configuration file;
a searching unit 72, configured to search, from mapping relationship data between the certificate type and a preset variable, the preset variable corresponding to the certificate type configured by the user;
and a replacing unit 73, configured to replace the certificate information in the configuration file with the searched preset variable.
Optionally, in yet another embodiment, the persistent integration tool includes Jenkins, the test package includes an IPA package, and the configuration file includes a pbxpro file;
the control module 80 is further configured to control the Jenkins to compile and package the source code after the pbxpro file is changed, so as to generate the IPA package;
the replacing unit 73 is further configured to replace the certificate information in the pbxpro file with the found preset variable as a script.
Optionally, in yet another embodiment, the control module 80 includes:
a compiling control unit 81, configured to control the persistent integration tool to compile the source code after the configuration file is changed;
a storage unit 82, configured to obtain version information when compiling the source code after the configuration file modification, and store the version information as a document file, where the version information includes the unique identifier and the build information;
a packaging control unit 83, configured to control the persistent integration tool to package the document file and the compiled source code to generate the test package;
the second acquisition module 20 includes:
an extracting unit 21 for extracting the document file from each of the test packages;
an information searching unit 22 for searching the unique identifier and the construction parameter from the document file of each of the test packages.
Optionally, in yet another embodiment, the test terminal 100 further includes:
a sending module 90, configured to send the named test packets to a server, so that the server generates a corresponding two-dimensional code for each named test packet;
the sending module 90 is further configured to send a clearing instruction to the server after a preset time, so that the server clears the corresponding test packet according to the clearing instruction.
The present invention also proposes a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of a test packet generating method of a mobile terminal as described above.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or server that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or server. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or server comprising the element.
The foregoing embodiment numbers of the present invention are merely for the purpose of description, and do not represent the advantages or disadvantages of the embodiments.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on this understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM (Read-Only Memory)/RAM (Random Access Memory ), magnetic disk, optical disk) as described above, including instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The foregoing description is only of the preferred embodiments of the present invention, and is not intended to limit the scope of the invention, but rather is intended to cover any equivalents of the structures or equivalent processes disclosed herein or in the alternative, which may be employed directly or indirectly in other related arts.
Claims (8)
1. The test packet generating method of the mobile terminal is characterized by comprising the following steps:
obtaining a test packet from the continuous integration tool;
acquiring a unique identifier and a construction parameter of each test packet;
configuring a corresponding folder for each test packet according to the unique identifier;
storing all the test packages into corresponding folders respectively;
naming the test packages stored in the folders according to the unique identifier and the construction parameters of each test package;
wherein, before the step of obtaining the test packet from the continuous integration tool, the method further comprises:
receiving a configuration request of a user, wherein the configuration request comprises a certificate type configured by the user and mapping relation data between the certificate type and a preset variable;
when a program issuing instruction is received, acquiring a configuration file corresponding to a source code to be compiled from a source code editor, wherein the configuration file contains certificate information;
determining the certificate type required by the user according to the configuration request, and searching a preset variable corresponding to the certificate type configured by the user from the mapping relation data between the certificate type and the preset variable according to the certificate type;
replacing the certificate information in the configuration file with the searched preset variable, wherein the certificate information comprises a unique identifier, a file name and a certificate name;
and sending the source code after the configuration file modification to the continuous integration tool so as to control the continuous integration tool to compile and package the source code after the configuration file modification to generate the test package.
2. The test packet generating method of the mobile terminal according to claim 1, wherein the construction parameters include a construction time stamp, a construction version number, and a construction number of the test packet; the step of naming the test packages stored in the folder according to the unique identifier and the construction parameters of each test package comprises the following steps:
arranging the unique identifier, the construction time stamp, the construction version number and the construction number according to a preset sequence to form an arrangement character string;
and setting the arrangement character string as the name of the test packet.
3. The method for generating a test packet for a mobile terminal according to claim 1, wherein the persistent integration tool comprises Jenkins, the test packet comprises an IPA packet, and the configuration file comprises a pbxpro file; the step of controlling the persistent integration tool to compile and package the source code after the configuration file modification to generate the test packet includes:
controlling the Jenkins to compile and pack the source code after the pbxpro file is changed so as to generate the IPA package;
the step of replacing the certificate information in the configuration file with the searched preset variable comprises the following steps:
and replacing certificate information in the pbxpro file by using the searched preset variable as a script.
4. The method for generating a test packet for a mobile terminal according to claim 1, wherein the step of controlling the persistent integration tool to compile and package the source code after the configuration file modification to generate the test packet comprises:
controlling the continuous integration tool to compile the source code after the configuration file is changed;
the version information of the source code after the configuration file is changed during compiling is obtained, and the version information is stored as a document file, wherein the version information comprises the unique identifier and the construction parameters;
controlling the continuous integration tool to pack the document file and the compiled source code so as to generate the test packet;
the step of obtaining the unique identifier and the construction parameter of each test packet comprises the following steps:
extracting the document file from each of the test packages;
and searching the unique identifier and the construction parameters from the document file of each test packet.
5. The test packet generating method of any one of claims 1-4, wherein after the step of naming the test packet corresponding to the test packet stored in the folder according to the unique identifier of each test packet and the build parameter, the method further comprises:
sending the named test packets to a server so that the server generates a corresponding two-dimensional code for each named test packet;
after the preset time, sending a clearing instruction to the server so that the server clears the corresponding test packet according to the clearing instruction.
6. A test terminal, comprising:
the first acquisition module is used for acquiring the test packet from the continuous integration tool;
the second acquisition module is used for acquiring the unique identifier and the construction parameters of each test packet;
the configuration module is used for configuring a corresponding folder for each test packet according to the unique identifier;
the storage module is used for respectively storing all the test packets into corresponding folders;
the naming module is used for naming the test packages stored in the folder correspondingly according to the unique identifier and the construction parameters of each test package;
the test packet generation module is used for receiving a configuration request of a user, wherein the configuration request comprises a certificate type configured by the user and mapping relation data between the certificate type and a preset variable; when a program issuing instruction is received, acquiring a configuration file corresponding to a source code to be compiled from a source code editor, wherein the configuration file contains certificate information; determining the certificate type required by the user according to the configuration request, and searching a preset variable corresponding to the certificate type configured by the user from the mapping relation data between the certificate type and the preset variable according to the certificate type; replacing the certificate information in the configuration file with the searched preset variable, wherein the certificate information comprises a unique identifier, a file name and a certificate name; and sending the source code after the configuration file modification to the continuous integration tool so as to control the continuous integration tool to compile and package the source code after the configuration file modification to generate the test package.
7. A test terminal, the test terminal comprising: communication module, a memory, a processor and a computer program stored on the memory and executable on the processor, which computer program, when being executed by the processor, realizes the steps of the test packet generating method of a mobile terminal according to any of claims 1 to 5.
8. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the test packet generating method of a mobile terminal according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810463140.0A CN109726104B (en) | 2018-05-15 | 2018-05-15 | Test packet generation method of mobile terminal, test terminal and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201810463140.0A CN109726104B (en) | 2018-05-15 | 2018-05-15 | Test packet generation method of mobile terminal, test terminal and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109726104A CN109726104A (en) | 2019-05-07 |
| CN109726104B true CN109726104B (en) | 2024-02-27 |
Family
ID=66293805
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201810463140.0A Active CN109726104B (en) | 2018-05-15 | 2018-05-15 | Test packet generation method of mobile terminal, test terminal and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109726104B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110399295B (en) * | 2019-06-28 | 2023-09-22 | 奇安信科技集团股份有限公司 | Application program testing method and device based on original file name |
| CN112732265B (en) * | 2019-10-29 | 2024-03-19 | 腾讯科技（深圳）有限公司 | Data processing method and related device |
| CN111124914B (en) * | 2019-12-20 | 2023-10-24 | 广州品唯软件有限公司 | Automatic test pre-compiling method, terminal and computer readable storage medium |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103702177A (en) * | 2013-12-13 | 2014-04-02 | 乐视网信息技术（北京）股份有限公司 | Method for storing video file and player |
| CN105487979A (en) * | 2015-12-02 | 2016-04-13 | 广州华多网络科技有限公司 | Test tool management method and user terminal |
| CN105512039A (en) * | 2015-12-16 | 2016-04-20 | 青岛海信电器股份有限公司 | Software test request form generating method and device |
| CN105743725A (en) * | 2014-12-10 | 2016-07-06 | 无锡买卖宝信息技术有限公司 | Method and device for testing application programs |
| CN106445548A (en) * | 2016-10-11 | 2017-02-22 | 武汉斗鱼网络科技有限公司 | Test pack issuing method and device |
| CN106776266A (en) * | 2015-11-25 | 2017-05-31 | 腾讯科技（深圳）有限公司 | The collocation method and terminal device of testing tool |
| CN107992409A (en) * | 2017-11-21 | 2018-05-04 | 平安养老保险股份有限公司 | Method for generating test case, device, computer equipment and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10268570B2 (en) * | 2016-05-05 | 2019-04-23 | Oracle International Corporation | Methods, systems, and computer readable media for automated generation of test files and testing network equipment using same |
-
2018
- 2018-05-15 CN CN201810463140.0A patent/CN109726104B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103702177A (en) * | 2013-12-13 | 2014-04-02 | 乐视网信息技术（北京）股份有限公司 | Method for storing video file and player |
| CN105743725A (en) * | 2014-12-10 | 2016-07-06 | 无锡买卖宝信息技术有限公司 | Method and device for testing application programs |
| CN106776266A (en) * | 2015-11-25 | 2017-05-31 | 腾讯科技（深圳）有限公司 | The collocation method and terminal device of testing tool |
| CN105487979A (en) * | 2015-12-02 | 2016-04-13 | 广州华多网络科技有限公司 | Test tool management method and user terminal |
| CN105512039A (en) * | 2015-12-16 | 2016-04-20 | 青岛海信电器股份有限公司 | Software test request form generating method and device |
| CN106445548A (en) * | 2016-10-11 | 2017-02-22 | 武汉斗鱼网络科技有限公司 | Test pack issuing method and device |
| CN107992409A (en) * | 2017-11-21 | 2018-05-04 | 平安养老保险股份有限公司 | Method for generating test case, device, computer equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109726104A (en) | 2019-05-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109726104B (en) | Test packet generation method of mobile terminal, test terminal and storage medium | |
| CN110290049B (en) | Message pushing method, server and computer readable storage medium | |
| CN110708210B (en) | Cloud test configuration method and device, computer equipment and storage medium | |
| CN104252342B (en) | Embedded application implementation method and device capable of configuring parameters | |
| US20150193296A1 (en) | Run-time error repairing method, device and system | |
| KR101038965B1 (en) | How to Configure Test Systems, Computer-readable Media, and Computing Systems | |
| CN105373401A (en) | Method and system for automatically releasing software package | |
| CN106610839B (en) | Method for issuing upgrade package, lightweight upgrade method, device and system | |
| CN110727454A (en) | Updating method and device of intelligent equipment, electronic equipment and storage medium | |
| CN103294514A (en) | System software release integrated method, compiling server and system | |
| CN112416353A (en) | Channel package packaging method and device and computer equipment | |
| WO2020015191A1 (en) | Business rule releasing and managing method, electronic device and readable storage medium | |
| CN113064630B (en) | Mobile terminal APP automatic packaging method, system, electronic equipment and storage medium | |
| CN107632829A (en) | A kind of App automation continuous integration systems and method based under iOS system | |
| US20170262263A1 (en) | Process and system for the generation of an operating program in the form of a mobile application that is capable of operating on a mobile device | |
| CN106569863B (en) | Resource and code modularization-based android app resource updating and repairing method | |
| CN109254765B (en) | Timing task management method, device, computer equipment and storage medium | |
| CN108629052B (en) | Kettle task scheduling method, system, computer equipment and storage medium | |
| CN113032245A (en) | Error positioning identification test method and device, computer equipment and storage medium | |
| CN105204910A (en) | Script hot updating method and system | |
| CN110851151B (en) | Method, device, terminal, server and storage medium for pre-installing application | |
| CN110413292B (en) | Light application installation method of application program, mobile terminal and storage medium | |
| US9854429B2 (en) | Mobile terminal configuration method and system | |
| CN113254054A (en) | Intelligent contract one-stop development system and method | |
| CN106569865B (en) | Method and device for manufacturing system upgrade file of terminal |
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 | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20240122 Address after: 518000 World Trade Plaza 101-1, Funan Community, Futian Street, Futian District, Shenzhen, Guangdong Province Applicant after: SHENZHEN XINGHAI IOT TECHNOLOGY Co.,Ltd. Country or region after: China Address before: 518000 Room 201, building A, No. 1, Qian Wan Road, Qianhai Shenzhen Hong Kong cooperation zone, Shenzhen, Guangdong (Shenzhen Qianhai business secretary Co., Ltd.) Applicant before: PING AN PUHUI ENTERPRISE MANAGEMENT Co.,Ltd. Country or region before: China |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |