CN108228228B - Application software publishing method and device - Google Patents
Application software publishing method and device Download PDFInfo
- Publication number
- CN108228228B CN108228228B CN201611146788.2A CN201611146788A CN108228228B CN 108228228 B CN108228228 B CN 108228228B CN 201611146788 A CN201611146788 A CN 201611146788A CN 108228228 B CN108228228 B CN 108228228B
- Authority
- CN
- China
- Prior art keywords
- application software
- application
- information
- release
- page
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
- Stored Programmes (AREA)
Abstract
The application provides an application software publishing method, which comprises the following steps: receiving an application release file which is uploaded by a user and corresponds to an application software version to be released, wherein the application release file comprises a login instruction, an information input instruction and an information submission instruction; logging in an application software issuing platform according to the login instruction; loading an application software release page of the application software release platform; sequentially searching text boxes corresponding to the text box screenshots in the information input instruction on the application software release page; sequentially copying the text box contents in the information input instruction to corresponding text boxes; searching page elements corresponding to the information submission key screenshots in the information submission instruction; and triggering an event corresponding to the page element so as to submit the text box content copied to the text box to the application software publishing platform. The application also provides an application software release device.
Description
Technical Field
The present application relates to the field of Information Technology (IT), and in particular, to a method and an apparatus for issuing application software.
Background
Under the age background of the development of science and technology, the rapid development of internet technology greatly expands the Application range and experience of people, and in recent years, the rapid development of mobile technology and Application software (APP) of five-door and eight-door enable people to obtain information, social activities, games and the like.
However, in the current APP uploading process, because the variety of the application software publishing platforms is large, after one application is developed, an operator needs to manually fill each item of information of the application software on the multiple application software publishing platforms, upload an installation package of the application software, and then submit the installation package to the application software publishing platforms for auditing. Similarly, when an updated version of an application software is released, an operator needs to manually fill in various pieces of information of the updated version of the application software on a plurality of application software release platforms, upload an update package, and then submit the update package to the application software release platforms for auditing. Especially in the current application environment, the iteration speed of the application software version is very fast in order to quickly preempt the market, and one version is updated usually 1 or 2 weeks. Thus, the manual application software release and version update method brings about a great waste of labor cost and time cost.
Disclosure of Invention
The application provides an application software publishing method, which comprises the following steps:
receiving an application release file which is uploaded by a user and corresponds to an application software version to be released, wherein the application release file comprises a login instruction, an information input instruction and an information submission instruction;
logging in an application software issuing platform according to the login instruction;
loading an application software release page of the application software release platform;
sequentially searching text boxes corresponding to the text box screenshots in the information input instruction on the application software release page;
sequentially copying the text box contents in the information input instruction to corresponding text boxes;
searching page elements corresponding to the information submission key screenshots in the information submission instruction; and
and triggering an event corresponding to the page element so as to submit the text box content copied to the text box to the application software publishing platform.
The application also provides an application software publishing device, which comprises:
the receiving module is used for receiving an application release file which is uploaded by a user and corresponds to the version of the application software to be released; the application release file comprises a login instruction, an information input instruction and an information submission instruction;
the login module is used for logging in an application software release platform according to the login instruction and loading an application software release page of the application software release platform;
the filling module is used for sequentially searching the text boxes corresponding to the text box screenshots in the information input instruction on the application software release page and sequentially copying the text box contents in the information input instruction to the corresponding text boxes; and
the submission module is used for searching page elements corresponding to the information submission key screenshots in the information submission instruction; and triggering an event corresponding to the page element so as to submit the text box content copied to the text box to the application software publishing platform.
By the scheme, the automatic release of the updated version of the application software on different application software release platforms can be realized, the application software operator does not need to manually log in each application release platform, manually fill in each information of the application software and manually submit, and the application software operator can complete the release of the application software version without knowing the address of the application release platform server. The scheme can greatly improve the working efficiency of operators, realize the rapid release of the application software and simultaneously improve the operating efficiency of hardware equipment for releasing the application software.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to these drawings without creative efforts.
FIG. 1 is a schematic diagram of a system architecture according to an example of the present application;
FIG. 2 is a flowchart of an application software publishing method according to an embodiment of the present application;
FIG. 3 is an example of an application publication file in an example of the present application;
FIG. 4 is a flowchart of a method for logging in one or more application software publishing platforms according to an example of the present application;
fig. 5 is a flowchart of a method for filling information of an application software version to be released in an example of the present application;
fig. 6 is a flowchart of a method for submitting information of a filled version of an application to be released in an example of the present application;
FIG. 7 is a schematic diagram of an internal structure of an application software distribution apparatus according to an example of the present application;
FIG. 7a is a schematic diagram illustrating an internal structure of a login module 702 in an application software publishing device according to an example of the present application;
fig. 7b is a schematic diagram of an internal structure of the fill-write module 703 in the application software distribution apparatus according to an example of the present application;
FIG. 8 is a diagram illustrating a hardware structure of an application software distribution apparatus according to an example of the present application;
FIG. 9 is a flowchart of an application software publishing method according to another example of the present application;
FIG. 10 is a schematic diagram of an internal structure of an application software distribution apparatus according to another embodiment of the present application;
fig. 11 is a schematic diagram of a hardware structure of an application software distribution apparatus according to another example of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
For simplicity and clarity of description, the invention will be described below by describing several representative embodiments. The numerous details of the examples are merely provided to assist in understanding the inventive arrangements. It will be apparent, however, that the invention may be practiced without these specific details. Some embodiments are not described in detail, but rather are merely provided as frameworks, in order to avoid unnecessarily obscuring aspects of the invention.
The release platforms of the current application software are various, such as APP malls under IOS systems; also as in the mainstream application market under the android system, including: the application software is released on a plurality of application software releasing platforms as much as possible in order to improve market share. As mentioned above, the manual release and version update of the application software reduces the work efficiency, and greatly increases the labor cost and the time cost.
Therefore, the application software publishing method can simulate manual operation of a user, automatic publishing of application software on a plurality of application software publishing platforms is achieved, labor cost and time cost in the application software uploading process are saved, working efficiency of application software operators is improved, and operating efficiency of hardware equipment used in application software publishing is improved.
Fig. 1 shows a schematic structural diagram of a system to which the application software publishing method is applied. As shown in fig. 1, the system may include a terminal 101, a network 102, and one or more application software distribution platforms 103 (shown illustratively as 103a and 103b in fig. 1).
In the present application, the terminal 101 may be various terminal devices, such as: personal Computers (PCs), tablets, smart phones, and the like, as well as various handheld devices, wearable devices, and the like. The operator of the application software may publish the application software through these terminal devices, and these terminals 101 may be based on various operating system platforms, such as: android (android) systems, IOS systems, Windows systems, etc. The terminal 101 can communicate with the application software distribution platform 103 through the network 102.
The network 102 may be a wired network or a wireless network. The terminal 101 and the application software distribution platform 103 may access the network 102 in a wired or wireless manner. As shown in fig. 1, a terminal 101 accesses a network 102 by wireless, and an application distribution platform 103 accesses the network 102 by wired.
The above-mentioned application publishing platforms 103a, 103b, etc., collectively referred to as the application publishing platform 103, may be servers of various application markets, such as an app treasure, and various cell phone assistants, cell phone app stores, etc. The application software distribution platform 103 is used to store various application software for the software providing method to distribute the application software and the application software user to download the application software. The application software distribution platform 103 may further include a database for storing application software.
Based on the system structure, the application provides an application software publishing method. The method is suitable for releasing the updated version of the application software. In the present application, an application software operator simulates manual operation by writing a graphical script file, for example, a graphical script written using a graphical scripting language sikuli, and calling and executing the graphical script file by the terminal 101, so as to implement a function of automatically publishing application software on a plurality of application software publishing platforms 103 by one key.
The graphical script file, such as sikuli graphical script, does not need a software programmer to write a line of codes, but uses a screen capture mode to combine the captured graphic elements to form an application program.
Fig. 2 shows an implementation flow of the application software publishing method according to the embodiment of the present application. Here, all the steps can be implemented by the terminal 101. The method comprises the following steps:
step 201: and receiving an application release file which is uploaded by a user and corresponds to the to-be-released application software version, wherein the application release file comprises a login instruction, an information input instruction and an information submission instruction.
It should be noted that in some examples of the present application, each application publication file will correspond to a version of an application software. That is, for each application software, each time a new version is released, an application release file corresponding to the version will be generated. This application release file records all information required for releasing the version of the application software, for example, the application release file may include Uniform Resource Locators (URLs) of the application software to be released on each application release platform. For example, the application release file may further include information of the version of the application software to be released, including: application provider, application profile, version description, language type, tariff information specification, etc. For another example, the application release file may further include an address of an update package or an upgrade package storing the version of the application software to be released.
Since different application publication platforms have different requirements for the information that the application needs to publish, in some instances, each application publication file may include one or more application publication subfiles. And each application publishing subfile corresponds to one application software publishing platform. By executing the application release subfile, the terminal can release the new version of the application software corresponding to the application release file on the corresponding application software release platform. For example, if a new version of the application software is to be released simultaneously on an app store, a hectometre mobile phone assistant, a 360 mobile phone assistant, a huawei application store, and a millet application store, the application release file corresponding to the new version of the application software will include at least 5 application release subfiles, which correspond to the 5 application release platforms respectively.
Specifically, the application publication subfile may include the following parts:
and the login instruction part is used for logging in the page corresponding to the application software to be issued on the application software issuing platform corresponding to the application issuing subfile when the terminal 101 executes the instruction of the login instruction part. The login portion may include instructions to: clicking a desktop browser icon; clicking an address input box after the initial browser page is loaded; inputting a URL (uniform resource locator) of the application software to be published on the corresponding application software publishing platform, which is set in the application publishing subfile; and clicking the login icon on the browser page after the browser page is loaded.
And an information filling instruction part, when the terminal 101 executes the instruction of the information filling instruction part, the terminal fills various information corresponding to the version of the application software to be released in the page corresponding to the application software to be released on the application software release platform corresponding to the component part, and uploads an installation package of the version of the application software to be released, such as an update package or an upgrade package. The information filling part may include instructions for: after the browser page is loaded, clicking each text box in sequence; sequentially inputting information corresponding to the content of the text box in the information of the version of the application software to be published set in the application publishing subfile; and clicking the installation package text box, and inputting the address, which is set in the application publishing subfile and used for storing the installation package of the application software version to be published.
An information submitting part, when the terminal 101 executes the information submitting part, the terminal will automatically submit the information items automatically filled in the front. The information submission section may include instructions to: and clicking a submission auditing key on the browser page to complete information submission.
In some examples of the present application, the application publication file may be a graphical script, such as a sikuli graphical script. Therefore, the application publishing subfile may include an intercepted picture of a user on a corresponding application publishing platform, and by identifying a page element, such as a text box, an icon, or a key, etc., corresponding to the picture in the instruction of the application publishing subfile on the desktop or the browser page, the operation on the corresponding page element on the browser page is completed, for example, clicking the icon or the key corresponding to the picture to trigger an event corresponding to the icon or the key; or click on a text box corresponding to the picture and enter text within the text box, etc.
An example of an application publishing subfile for publishing application software on an application platform is given below in conjunction with fig. 3, taking the application marketplace as an example. As shown in fig. 3, the application issuance subfile will also include a login instruction section 301, an information filling instruction section 302, and an information submission instruction section 303.
The login instruction part 301 may include an instruction to Click an icon corresponding to the first picture 304, for example, an instruction to Click a Click (the first picture 304). The first picture 304 is a screenshot of a browser icon on a desktop, for example, the screenshot of a google browser icon in fig. 3. In this way, when the terminal 101 executes the instruction, the first picture 304 in the instruction is first matched with each icon on the desktop, and the icon corresponding to the first picture 304 in the instruction, that is, the google browser icon, is found. Then, clicking the google browser icon according to a click command, namely activating the google browser application, so as to open the initial browser page. It should be noted that, the google browser indicates an example, it is also possible to use a screenshot of an icon of another browser, for example, a screenshot of an IE browser icon or a screenshot of an icon of a vacation browser may also be used to achieve the purpose of activating an IE browser or a vacation browser on a desktop.
As shown in fig. 3, the login instruction portion 301 may further include an instruction to Click on the browser address bar and input a URL, which may be implemented by Click and Type instructions, for example. The Click command is mainly used to find the location of the address bar, i.e. to find where to enter the URL. The corresponding URL is the link obtained when the application software to be released is released on the application treasure for the first time. The URL is written in the login command section 301 of the application subfile, so that the terminal can directly obtain the URL from the login command section of the application issuing subfile and automatically input the URL into the address bar of the browser by inputting a type (URL) command.
As shown in fig. 3, the login instruction portion 301 may further include an instruction to wait for a second picture 305 to appear on the browser page and click on a page element corresponding to the second picture 305. The second picture 305 may be a screenshot of an icon corresponding to the user account in the URL page. The above instructions may be implemented, for example, by Wait for Wait (second picture 305) and Click (second picture 305) instructions. The Wait instruction represents that an icon corresponding to the user account icon screenshot appears on a browser page; and the Click instruction is used for triggering an event corresponding to the icon corresponding to the user account. In this way, when the terminal 101 executes the instruction, an icon corresponding to the user account corresponding to the second picture 305 appears in the browser page to be loaded first, then a mouse action is simulated to click the icon corresponding to the user account, an event corresponding to the icon is triggered, so that a login request carrying user account information is sent to the application software publishing platform, and the user logs in the application treasure. In some examples, the method for logging in the application publishing platform can log in through a third-party application account, such as directly through an account such as a QQ or a WeChat, without inputting information such as a user name and a password. If necessary, the user name and the password of the user can be directly recorded in the login instruction part, and the positions of the text boxes for inputting the user name and the password can be respectively found through a Click command; and then copying the user name and the password recorded in the login instruction to a corresponding text box through a Type command, so as to realize the automatic filling of the user name and the password. And finally, finding a page element corresponding to the login key screenshot through a Click command, and triggering an event corresponding to the page element, for example, sending a login request carrying user account information to an application software release platform, thereby realizing user login.
After the user logs in, the browser jumps to an application software release page when the version of the application software is updated on the application platform. At this time, information of the version to be updated needs to be filled in on the page. In this case, the information filling instruction section 302 may include an instruction to Click on each information item text box, which may be realized by a Click (third picture 306) instruction, and to enter each item of information. The third pictures 306 may be respective screenshots of various information item textboxes, such as an application provider textbox screenshot 306a, an application profile textbox screenshot 306b, a version description textbox screenshot, an installation package textbox screenshot 306c, and so on. The position of each text box can be found in sequence on the current browser page through the instruction terminal. In addition, the instruction for inputting various items of information may be realized by an instruction of Type (custom content), where the custom content is various items of information corresponding to the current application software version recorded in the application distribution subfile, such as the actual content of the application provider, the application profile, the version description, the installation package address, and the like. When executing the above command, the terminal 101 first finds a page element (text box) corresponding to the third picture 306 on the current browser page, then clicks the page element according to the Click instruction, that is, positions the cursor to the position corresponding to the text box, and copies the corresponding content recorded in the application publishing subfile to the corresponding text box according to the customized content in the Type instruction. For example, upon executing a Click (application provider text box screenshot 306a) instruction, the terminal 101 will first find a text box on the browser page that corresponds to the application provider text box screenshot 306a, positioning the cursor into the text box. Then, when executing the Type (custom content) instruction, the terminal 101 copies the custom content into the text box, and realizes an operation of automatically filling in application provider information in the application provider text box of the browser page.
The information submission instruction section 303 may include an instruction to Click a submission button, which may be implemented by a Click (fourth picture 307) instruction, for example. The fourth picture 307 may be a screenshot of an submit button on the page. When executing the above command, the terminal 101 will first find the page element corresponding to the fourth picture 307 on the current browser page, i.e. the submit button. Then, the simulated mouse clicks the submit button to trigger the event corresponding to the submit button, so as to submit the content copied to the text box to the server of the application software publishing platform, thereby completing the submission of the information. In some implementations, according to a browser program designed by the application publishing platform, such as an HTML program, when detecting that an event corresponding to a submit button is triggered, the browser on the terminal 101 sends a request (e.g., a Post message) to a server of the application publishing platform, where the request carries information that has been entered in a textbox of a current browser page. Therefore, the purpose of submitting the information input in the text box of the current page to the application software publishing platform server is achieved.
The application publishing subfile is described by taking an application treasure as an example, and in some examples of the application, the application publishing file may include a plurality of application publishing subfiles in a serial manner, and the application publishing subfiles correspond to different application software publishing platforms respectively. In this way, when the terminal executes the application distribution file including the plurality of application distribution subfiles, the application software can be sequentially distributed on different application software distribution platforms.
After the software provider edits the application distribution file, the application distribution file is saved and uploaded to the terminal 101. And the terminal executes the application software when the application software is released so as to complete the automatic release of the application software.
Step 202: and logging in the application software publishing platform according to the login instruction of the application publishing file.
Specifically, in some examples of the present application, the terminal may log in the one or more application software distribution platforms in series, sequentially, or simultaneously and in parallel according to a login instruction of the application distribution file. The method for logging in an application software publishing platform may be as shown in fig. 4, and includes the following steps:
If the activation is realized through a script, the activation can be realized through a click command.
Step 403, after the initial browser page is loaded, finding the position of the address bar according to the login instruction, copying the URL address recorded in the login instruction to the address bar of the browser page, and opening the browser page corresponding to the URL; the URL is an address created by the application release platform when the application software of the new version to be released is released on the application software release platform for the first time.
And step 404, after the browser page is loaded, searching a page element corresponding to the user account icon screenshot recorded in the application release file on the browser page.
In this step, the terminal identifies each page element on the current browser page and matches the user account icon screenshot recorded in the application release file, so as to find the page element corresponding to the user account icon screenshot recorded in the application release file.
If the triggering of the event is realized through a script, the triggering can be realized through a click command.
The method for logging in the app bank is described in detail below with reference to fig. 3. As shown in fig. 3, when executing the first instruction of the login portion 301 in the application distribution subfile, the terminal 101 first matches the first picture 304 in the instruction with each icon on the desktop one by one until the icon matching the first picture 304 in the instruction is found, executes a Click instruction, simulates an action of a user clicking the icon of the google browser through a mouse, so as to open the google browser, and completes the steps 401 and 402.
After the loading of the initial browser page is completed, the terminal 101 first clicks an address field of the browser by simulating a mouse action according to a Click command in accordance with an input command of the login section 301 in the application release file, captures the address field of the browser, positions a cursor in the address field of the browser, and copies a parameter (URL) of the Type command shown in fig. 3 to the address field. As mentioned above, the URL is a unique address corresponding to the application software generated by the application software publishing platform when the application software to be published is first published on the application software publishing platform, for example, when the application software of the QQ browser is first published in the app marketplace, the app marketplace generates a unique address corresponding to the application software of the QQ browser: http:// op. open. qq. com/apregv 2/create _ android ═ 1105545505& from ═ http% 3A% 2F. op. open. qq. com% 2Fappregv 2% 2F. After the URL is input, the browser loads the application software publishing platform page corresponding to the application software, and completes step 403.
According to the login instruction of the login part 301 in the application release file, the terminal 101 first waits for an icon corresponding to the user account corresponding to the second picture 305 in the login instruction to appear in the loaded browser page, and then simulates a mouse action according to the Click instruction to Click the icon corresponding to the user account, so as to complete the login of the user on the application release platform, and thus the steps 404 and 405 are completed.
The terminal can log in more than one application software release platform in sequence or simultaneously according to the method.
As an alternative to the above-described steps 404 and 405, the user login may also be realized by the following procedure. First, after loading an application publishing platform page corresponding to application software, the terminal 101 may match a corresponding username and password text box on a browser page based on a username and password text box screenshot in a login instruction. Then, the terminal 101 may copy the user name and the password of the user described in the login instruction to the corresponding text boxes in sequence. Then, the terminal 101 may match a corresponding login key on the browser page based on the login key screenshot in the login instruction. Finally, the terminal 101 may trigger an event corresponding to the login key, so that the user name and the password copied to the user name and password text box are taken as user account information to be carried in the login request, and are sent to the application software release platform for user identity verification, so as to complete user login.
Step 203: and loading the application software publishing page of the application software publishing platform.
After the user identity authentication is passed, the application publishing platform returns an application publishing page to the browser of the terminal 101. At this time, the browser of the terminal 101 loads the application distribution page returned by the application distribution platform.
Step 204: and filling information of the version of the application software to be released in the application software release page respectively according to the information input instruction of the application release file.
Specifically, in some examples of the present application, a method for filling out information of an application software version to be released on an application software release platform may be as shown in fig. 5, and includes the following steps:
In this step, the terminal identifies each page element on the current browser page and matches the page element with the textbox screenshot recorded in the application release file, so as to find the textbox corresponding to the textbox screenshot recorded in the application release file, that is, the position where the corresponding application software version information is filled in.
If the operations of finding the text box and positioning the cursor to the text box are realized through the graphical script, the operations can be realized by clicking (Click) a command of screenshot of the text box.
If the above copying is realized by a graphical script, it can be realized by an input (Type) command.
And according to the information input instruction, repeatedly executing the steps 501 and 503 until all the information that the version of the application software to be issued needs to be updated is filled.
The method for logging in the app bank is described in detail below with reference to fig. 3. As shown in fig. 3, the terminal 101 executes the instruction of the application distribution document information filling instruction part 302, and first, finds a page element corresponding to the third picture 306a, that is, an application provider text box, in the loaded browser page. And then, simulating a mouse action to Click the text box according to the Click command in the application release file, and positioning the cursor in the text box. Finally, the parameters in the later Type command, such as "Tencent science and technology (Shenzhen) Limited", are copied into the text box. Likewise, the page element corresponding to the third picture 306b, i.e., the application profile text box, is found below. And then, simulating a mouse action to Click the text box according to the Click command in the application release file, and positioning the cursor in the text box. Finally, the parameters in the subsequent Type command, i.e. the content of the application profile, are copied into the text box. Then, a page element corresponding to the third picture 306c, that is, an installation package text box, is found, a mouse action is simulated according to a Click instruction in the application release file to Click the text box, a cursor is positioned in the text box, and a parameter in a subsequent type command, that is, a local address (for example, E: \ Android _ upload \ yingyonbao. Therefore, the automatic filling of each information item of the version of the application software to be released on the corresponding application software release platform can be completed through the content recorded in the application release file.
Step 205: and submitting the filled information of the version of the application software to be released on the application software releasing platform according to the information submitting instruction in the application releasing file.
In some examples of the present application, the method for submitting the filled-in information of the version of the application software to be released may be as shown in fig. 6, and includes the following steps:
In this step, the terminal identifies each page element on the current browser page and matches the information submission key screenshot recorded in the application release file, so as to find the page element corresponding to the submission key screenshot recorded in the application release file, that is, the submission key, and determine the position of the submission key.
If the activation is realized through a script, the activation can be realized through a click command.
Still taking fig. 3 as an example to explain the method in this step, after filling all the information to be updated according to the application distribution file, the terminal 101 searches the page element corresponding to the fourth picture 307, that is, the page element corresponding to the "submit this page review" key, on the page of the application software distribution platform according to the information submitting portion 303 of the application distribution file. And then, simulating a mouse action according to the Click command to Click the submission button, and submitting the audit. Specifically, after detecting that the "submit this page review" key is "clicked", the browser triggers an event when the "submit this page review" key is "clicked" according to an instruction in the currently loaded browser page, for example, sends a Post message to a corresponding server, where the Post message carries the content input in the text box of the current page. Those skilled in the art will understand that the event corresponding to the key is preset by the application software distribution platform and is sent to the browser of the terminal through a language that can be recognized by the browser, for example, an HTML language. And when detecting that the corresponding event is triggered, the browser of the terminal executes corresponding operation according to the instruction of the application software issuing platform.
Through the steps, various information of the application software can be submitted to the application software publishing platform, namely the application treasure, so that the application software publishing platform is requested to be checked.
In addition, by the method, the application software provider does not need to know the URL address of the application software release platform server when writing the application software release file, so that the automatic release of the application software version can be realized even when the application software release platform intentionally hides the URL address of the server, the operation of the application software provider is greatly facilitated, and the manpower and material resources required by the shelf operation of the application software are saved.
In some examples, in order to write the graphical script conveniently, each application software publishing platform may be respectively logged in advance, and each page element, including an icon, a text box, and the like, on the application software publishing page on each application software publishing platform may be captured in advance and stored locally to establish a software publishing file material library. In this way, when the graphical script shown in fig. 3 is written, the screen shot in the software distribution file material library can be used as it is.
Based on the above example, the present application also proposes an application software distribution device, which can be installed on the terminal 101.
In some examples of the present application, the application software distribution apparatus may be implemented by a structure diagram shown in fig. 7, including: a receiving module 701, a logging module 702, a filling module 703, and a submitting module 704.
In some examples, the modules function as follows:
the receiving module 701 is configured to receive an application release file corresponding to an application software version to be released, which is uploaded by a user; the application issuing file comprises a login instruction, an information input instruction and an information submission instruction;
the login module 702 is configured to log in an application software publishing platform according to a login instruction, and load an application software publishing page of the application software publishing platform;
the filling module 703 is configured to sequentially search, on the application software release page, text boxes corresponding to the text box screenshots in the information input instruction, and sequentially copy the text box contents in the information input instruction to the corresponding text boxes;
the submission module 704 is configured to search for a page element corresponding to the information submission key screenshot in the information submission instruction; and triggering an event corresponding to the page element so as to submit the text box content copied to the text box to the application software publishing platform.
In some examples, the login module 702 includes an open unit 7021, an input unit 7022, and a login unit 7023, and fig. 7a shows an internal structure of the login module 702, where functions of the units are as follows:
the opening unit 7021 is configured to search, on the desktop, a browser icon corresponding to the browser icon screenshot recorded in the application release file; after the browser icon corresponding to the browser icon screenshot is found, activating the browser application corresponding to the browser icon, and opening an initial browser page;
the input unit 7022 is configured to find a position of an address bar of a browser page after the initial browser page is loaded, copy the URL address recorded in the application release file to the address bar of the browser page, and open a page corresponding to the URL;
the login unit 7023 is configured to search, on a browser page, a page element corresponding to the user account icon screenshot recorded in the application release file after the browser page is loaded; and after the page element corresponding to the user account icon screenshot is found, triggering an event corresponding to the page element to complete the login of the user on an application software release platform.
In some examples, the filling module 703 includes a searching unit 7031 and an inputting unit 7032, and fig. 7b shows an internal structure of the filling module 703, where functions of the units are as follows:
the searching unit 7031 is configured to search, after the browser page is loaded, a text box corresponding to the text box screenshot recorded in the application release file on the browser page;
the input unit 7032 is configured to, after finding the text box corresponding to the screenshot of the text box, position the cursor in the text box, and copy the content, which is recorded in the information input instruction and should be filled in the text box, to the text box.
In some examples, the submission module 704 is configured to search, on a browser page, a page element corresponding to the screenshot of the information submission key recorded in the information submission instruction; and after finding the page element corresponding to the screenshot of the information submission key frame, triggering an event corresponding to the page element so as to submit the text frame content copied to the text frame to the application software publishing platform.
It should be noted that the detailed description of the specific method and principle for implementing various functions by the above modules (for example, the descriptions in fig. 2 to fig. 7) is provided in the foregoing, and the detailed description is omitted here.
In some examples, the apparatus may be run in any computing device that can play a live media stream and loaded in memory of the computing device. As shown in fig. 8, the computing device may include: memory 801, processor 803, bus 802, ports 804.
The processor 803 and memory 801 are interconnected by a bus 802.
The processor 803 may receive and transmit data through the port 804 to enable network communications and/or local communications.
The modules 701-706 may be machine-executable instructions stored in the memory 801.
The processor 803 can implement the functions of the modules 701 to 706 by executing the machine-executable instructions included in the modules 701 to 706 in the memory 801.
By the scheme, the automatic release of the updated version of the application software on different application software release platforms can be realized, and the application software operator does not need to manually log in each application release platform, manually fill in each information of the application software and manually submit the information. The scheme can greatly improve the working efficiency of operators, realize the rapid release of the application software and simultaneously improve the operating efficiency of hardware equipment for releasing the application software.
Furthermore, by writing a visual script file, an operator of the application software does not need to know the code logic behind the visible content on the browser page, can position the corresponding page element on the browser page by using the screenshot of each page element on the page, and can execute various operations, such as clicking, waiting, inputting text content and the like, on the corresponding page element, thereby triggering the event corresponding to each page element. Therefore, even under the condition that the URL submitted by the server of each application software release platform is hidden, the script file can be still written, and the release and submission of the application software version can be normally finished, so that the working efficiency and the utilization rate of hardware equipment are greatly improved.
In some examples of the application, in order to further ensure the accuracy of the release of the updated version of the application software, some improvements are made to the method, and another application software release method is provided, which can further implement a verification function on the released result. Fig. 9 shows a flow of the software distribution method, and as shown in fig. 9, the method includes:
step 901: receiving a configuration file corresponding to the to-be-released application software version uploaded by a user, wherein the configuration file comprises the information of the application software version.
In this step, one application software is usually released to different application markets to preempt more users, and the information that needs to be filled in each version of the application software to be released on different application software release platforms is also different, so that the information that needs to be filled in each version of the application software can be updated according to the different application software release platforms, configuration files of the application software on each application software release platform are established, and preparation is made for a verification stage after the application software is released.
Here, the content of the configuration file of the application software in each application market may be an application profile, a sentence profile, a current version introduction, a support language, a tariff type, and the like of the application software, and the configuration file is created according to the configuration requirements of different application software distribution platforms for the application software, and is locally stored in the configuration file of each application software distribution platform. The configuration file may be in the form of a database table, an Excel table, or a text. In the configuration file, the content of each item of information of the application software may be indexed by the name of the information item, for example, the content of the application profile recorded in the configuration file is indexed by the application profile; the content of the current version introduction is indexed by the current version introduction, and so on.
Furthermore, the information content recorded in the above configuration file should be consistent with the content recorded in the application distribution file.
Step 902: and receiving an application release file which is uploaded by a user and corresponds to the to-be-released application software version, wherein the application release file comprises a login instruction, an information input instruction and an information submission instruction.
In this step, the writing method and content included in the application release file corresponding to the version of the application software to be released are the same as those described in step 201, and are not specifically described here.
After the software provider edits the application distribution file, the application distribution file is saved and uploaded to the terminal 101. And is executed by the terminal when the application software is released so as to complete the release of the application software.
Step 903: and logging in the application software publishing platform according to the login instruction of the application publishing file.
In this step, the method for the terminal 101 to log in one or more application software distribution platforms according to the application distribution file is the same as that described in step 202, and is not specifically described here.
Step 904: and loading the application software publishing page of the application software publishing platform.
Step 905: and filling information of the version of the application software to be released on the application software release page according to the information input instruction of the application release file.
In this step, the method for filling in the version information of the application software to be released on the one or more application software release platforms by the terminal 101 according to the application release file is the same as that described in step 203, and is not described in detail here.
Step 906: and submitting the filled information of the version of the application software to be released on the application software releasing platform according to the information submitting instruction in the application releasing file.
In this step, the method for the terminal 101 to submit the filled version information of the application software to be released on the one or more application software releasing platforms according to the application releasing file is the same as that described in step 204, and is not described in detail here.
Step 907: and reading the information of the released application software version from the one or more application software releasing platforms.
In some examples, after the release of the application software version is completed, the terminal 101 searches for the content of each page element displayed in the corresponding area on the page corresponding to the application software on the one or more application software release platforms. For example, the content of the corresponding area of each information item displayed on the page is the application provider, the application profile, the version description, the tariff description, the language description and the like. And indexes the contents of the respective information items by the names of the respective information items. For example, the read and recorded application provider corresponds to the region page element content "tennessee science (Shenzhen) Limited," and the recorded content is indexed with the application provider.
Step 908: and comparing the information of the read released application software version with the corresponding information recorded in the configuration file, and if the information of the read released application software version is consistent with the corresponding information recorded in the configuration file, the release of the application software version is successful.
In some examples, in order to ensure the accuracy of the released application software, the page element read in step 907 and corresponding to the version information of the application software to be released is matched with the corresponding information of the version of the application software in the configuration file, and if all the page elements are consistent with the corresponding information of the version of the application software, the application software is considered to be successfully released; if not, the contents of the configuration file and the application release file need to be checked, and after the configuration file and the application release file are modified to be consistent, the new version of the application software can be released again.
In some examples, in order to write the graphical script conveniently, each application software publishing platform may be respectively logged in advance, and each page element, including an icon, a text box, and the like, on the application software publishing page on each application software publishing platform may be captured in advance and stored locally to establish a software publishing file material library.
Based on the above example, the present application also proposes an application software distribution device, which can be installed on the terminal 101.
In some examples of the present application, the application software distribution apparatus may be implemented by a structure diagram shown in fig. 10, including: configuration module 1001, receive module 1002, login module 1003, fill-in module 1004, submit module 1005, and check module 1006.
In some examples, the modules function as follows:
the configuration module 1001 is configured to receive a configuration file corresponding to an application software version to be released, where the configuration file includes information of the application software version.
The function of the receiving module 1002 is the same as that of the receiving module 701 in fig. 7, and is not described in detail again;
the function of the login module 1003 is the same as that of the receiving module 702 in fig. 7, and is not described in detail again;
the function of the filling module 1004 is the same as that of the receiving module 703 in fig. 7 and is not described in detail again;
the function of the submit module 1005 is the same as that of the receive module 704 in FIG. 7 and will not be described in detail again;
the verification module 1006 is configured to read information of the released application software version from the one or more application software release platforms; and comparing the information of the read released application software version with the corresponding information recorded in the configuration file, and if the information of the read released application software version is consistent with the corresponding information recorded in the configuration file, the release of the application software version is successful.
It should be noted that the detailed description of the specific method and principle for implementing various functions by the above modules (for example, the descriptions in fig. 9 to fig. 10) is provided in the foregoing, and the detailed description is omitted here.
In some examples, the apparatus may be run in any computing device where application software distribution may be performed and loaded into a memory of the computing device. As shown in fig. 11, the computing device may include: memory 1101, processor 1103, bus 1102, ports 1104.
The processor 1103 and the memory 1101 are interconnected by a bus 1102.
The processor 1103 can receive and transmit data through the port 1104 to enable network communications and/or local communications.
The modules 1001-1006 may be machine-executable instruction modules stored in the memory 1101.
The processor 1103 can further implement the functions of the modules 1001 to 1006 by executing machine-executable instructions included in the modules 1001 to 1006 in the memory 1101.
By the technical scheme, the automatic release of the application software version can be realized, and the released application software version information can be verified according to the configuration file edited by an application software operator in advance. And if the issued information is consistent with the information recorded in the configuration file, the application software is considered to be successfully issued.
In addition to the method and apparatus for implementing application software publishing described above, in the example of the present application, a computer program for implementing application software publishing automatically is also provided, where the computer program may be a visual script file written in a visual script language, and may include, for example, the instruction for implementing step 202 and step 205 in fig. 2 or the instruction for implementing step 903 and step 906 in fig. 9 shown in fig. 3. In an example of the present application, a non-volatile computer-readable medium for storing the above-described computer program is also presented.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (10)
1. A method of application software release, the method comprising:
receiving a configuration file corresponding to an application software version to be released uploaded by a user, wherein the configuration file corresponding to each application software release platform is respectively created according to the configuration requirements of each application software release platform on the application software; the configuration file comprises information of the application software version; receiving an application release file which is uploaded by a user and corresponds to an application software version to be released, wherein the application release file comprises one or more application release subfiles, and each application release subfile corresponds to one application software release platform; the application issuing subfile comprises a login instruction, an information input instruction and an information submission instruction;
logging in an application software issuing platform according to the login instruction;
loading an application software release page of the application software release platform;
sequentially searching text boxes corresponding to the text box screenshots in the information input instruction on the application software release page;
sequentially copying the text box contents in the information input instruction to corresponding text boxes;
searching page elements corresponding to the information submission key screenshots in the information submission instruction; and
triggering an event corresponding to the page element so as to submit the text box content copied to the text box to the application software publishing platform;
reading the information of the released application software version from the application software release platform; and
comparing the released information of the application software version with the information of the application software version recorded in the configuration file,
if the application software versions are consistent, prompting the user that the application software versions are successfully published;
and if the version is inconsistent, prompting that the release of the application software version of the user is unsuccessful.
2. The method of claim 1, wherein the application publication file is a visualization script.
3. The method of claim 2, wherein the logging into the application software publication platform comprises:
searching a browser icon corresponding to the browser icon screenshot in the login instruction on the current desktop;
activating a browser application corresponding to the browser icon;
opening an initial browser page;
copying a Uniform Resource Locator (URL) in the login instruction to an address bar of the initial browser page, and opening the browser page corresponding to the URL;
searching a page element corresponding to the user account icon screenshot recorded in the application release file on the browser page; and
and triggering an event corresponding to the page element to send a login request to the application software release platform, wherein the login request carries account information of the user.
4. The method of claim 2, wherein the text box screenshot comprises one or any combination of the following on the application publication page: an application provider text box screenshot, an application profile text box screenshot, a version description text box screenshot and an installation package text box screenshot;
the text box content comprises one or any combination of the following: an application provider, an application profile, a version description, and an installation package storage address.
5. The method of claim 1, wherein the comparing the published information of the application software version with the information of the application software version in the configuration file comprises:
and matching the content of the read page element corresponding to the information of the application software version to be released with the corresponding information of the application software version to be released in the configuration file.
6. The method of claim 2, the method further comprising:
and intercepting corresponding pictures of each page element on the application software publishing pages on the one or more application software publishing platforms, and storing the intercepted pictures in an application publishing file material library.
7. An application software distribution apparatus, the apparatus comprising:
the configuration module is used for receiving a configuration file corresponding to the application software version to be released uploaded by a user, wherein the configuration file corresponding to each application software release platform is respectively created according to the configuration requirements of each application software release platform on the application software; the configuration file comprises the information of the application software version; the receiving module is used for receiving an application release file which is uploaded by a user and corresponds to the to-be-released application software version, wherein the application release file comprises one or more application release subfiles, and each application release subfile corresponds to one application software release platform; the application issuing subfile comprises a login instruction, an information input instruction and an information submission instruction;
the login module is used for logging in an application software release platform according to the login instruction and loading an application software release page of the application software release platform;
the filling module is used for sequentially searching the text boxes corresponding to the text box screenshots in the information input instruction on the application software release page and sequentially copying the text box contents in the information input instruction to the corresponding text boxes; and
the submission module is used for searching page elements corresponding to the information submission key screenshots in the information submission instruction; triggering an event corresponding to the page element so as to submit the text box content copied to the text box to the application software publishing platform;
the verification module is used for reading the information of the released application software version from the one or more application software release platforms; and comparing the information of the released application software version with the corresponding information recorded in the configuration file, and if the information of the released application software version is consistent with the corresponding information recorded in the configuration file, the release of the application software version is successful.
8. The apparatus of claim 7, wherein the login module comprises:
the opening unit is used for searching a browser icon corresponding to the browser icon screenshot recorded in the login instruction on the current desktop; after the browser icon corresponding to the browser icon screenshot is found, activating a browser application corresponding to the browser icon, and opening an initial browser page;
the input unit is used for copying a Uniform Resource Locator (URL) in the login instruction into an address bar of the initial browser page and opening the browser page corresponding to the URL; and
the login unit is used for searching a second page element corresponding to the user account icon screenshot in the login instruction on the browser page corresponding to the URL; after the second page element corresponding to the user account icon screenshot is found, triggering an event corresponding to the second page element to send a login request to the application software publishing platform, wherein the login request carries account information of the user.
9. A computer-readable medium having computer-readable instructions stored thereon for execution by at least one processor to perform the method of any one of claims 1-6.
10. A computing device, comprising: a processor, a memory;
the memory for storing a computer program;
the processor is configured to execute the method of any one of claims 1-6 by calling the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611146788.2A CN108228228B (en) | 2016-12-13 | 2016-12-13 | Application software publishing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201611146788.2A CN108228228B (en) | 2016-12-13 | 2016-12-13 | Application software publishing method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN108228228A CN108228228A (en) | 2018-06-29 |
| CN108228228B true CN108228228B (en) | 2021-02-23 |
Family
ID=62638240
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201611146788.2A Active CN108228228B (en) | 2016-12-13 | 2016-12-13 | Application software publishing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN108228228B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109101267B (en) * | 2018-07-31 | 2021-11-23 | 上海携程金融信息服务有限公司 | Application release management method and device, electronic equipment and storage medium |
| CN109284124A (en) * | 2018-08-01 | 2019-01-29 | 北京奇虎科技有限公司 | A kind of Software package method and apparatus |
| CN109542468B (en) * | 2018-11-23 | 2022-05-20 | 北京金山安全软件有限公司 | Application program release method and device and electronic equipment |
| CN110392095A (en) * | 2019-06-19 | 2019-10-29 | 深圳壹账通智能科技有限公司 | Method for uploading, device, server and the storage medium of installation package file |
| CN112528051B (en) * | 2019-09-19 | 2022-10-14 | 聚好看科技股份有限公司 | Singing work publishing method, display device and server |
| CN112163784A (en) * | 2020-10-20 | 2021-01-01 | 成都中科大旗软件股份有限公司 | Application software management method and system |
| CN112541148A (en) * | 2020-12-15 | 2021-03-23 | 北京百度网讯科技有限公司 | Information issuing method and device and electronic equipment |
| CN112860311A (en) * | 2021-02-04 | 2021-05-28 | 京东数字科技控股股份有限公司 | Application program issuing method and device and electronic equipment |
| CN113627887B (en) * | 2021-08-11 | 2024-08-13 | 网易（杭州）网络有限公司 | Software release step checking method and device, electronic equipment and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102868726A (en) * | 2012-08-23 | 2013-01-09 | 北京神鹰城讯科技有限公司 | Method and system for publishing Internet information |
| US8819840B2 (en) * | 2012-08-20 | 2014-08-26 | Adobe Systems Incorporated | Method and apparatus for provisioning subscription products |
| CN104516738A (en) * | 2014-12-15 | 2015-04-15 | 北京金和软件股份有限公司 | Integrated implementing method for development and release of APP |
| CN105634919A (en) * | 2015-12-21 | 2016-06-01 | 中国电子科技集团公司第三十研究所 | Information releasing method based on user behavior simulation |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102750332B (en) * | 2012-05-31 | 2016-12-14 | 北京城市网邻信息技术有限公司 | Information issuing method, Apparatus and system |
| US9817804B2 (en) * | 2013-09-12 | 2017-11-14 | Wix.Com Ltd. | System for comparison and merging of versions in edited websites and interactive applications |
| CN104065517A (en) * | 2014-07-07 | 2014-09-24 | 用友软件股份有限公司 | Distributed-system software configuration management method and system |
| CN105608198A (en) * | 2015-12-28 | 2016-05-25 | 武汉传神信息技术有限公司 | Method for input validation of E-business platform commodity information |
-
2016
- 2016-12-13 CN CN201611146788.2A patent/CN108228228B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8819840B2 (en) * | 2012-08-20 | 2014-08-26 | Adobe Systems Incorporated | Method and apparatus for provisioning subscription products |
| CN102868726A (en) * | 2012-08-23 | 2013-01-09 | 北京神鹰城讯科技有限公司 | Method and system for publishing Internet information |
| CN104516738A (en) * | 2014-12-15 | 2015-04-15 | 北京金和软件股份有限公司 | Integrated implementing method for development and release of APP |
| CN105634919A (en) * | 2015-12-21 | 2016-06-01 | 中国电子科技集团公司第三十研究所 | Information releasing method based on user behavior simulation |
Non-Patent Citations (2)
| Title |
|---|
| 基于Sikuli的自动化测试研究与应用;王小巍;《软件导刊》;20120430(第04期);第103-105页 * |
| 安卓app如何发布到91手机助手;板华二船TKP;《https://zhidao.baidu.com/question/487984136275853892.html》;20160811;第1页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN108228228A (en) | 2018-06-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108228228B (en) | Application software publishing method and device | |
| CN108415832B (en) | Interface automation test method, device, equipment and storage medium | |
| US10095609B1 (en) | Intermediary for testing content and applications | |
| CN107925696B (en) | System and method for identifying, indexing and navigating to a depth state of a mobile application | |
| CN108293081B (en) | Deep linking of program playback to mobile application state through user interface events | |
| WO2019072110A1 (en) | Method for generating application program, apparatus, system, device, and medium | |
| CN105765527B (en) | The method and apparatus of software development kit (SDK) for customization | |
| US7992127B2 (en) | Method and system of encapsulating web site transactions for computer-aided generation of web services | |
| CN105849691B (en) | The method and apparatus generated for code virtualization and remote process call | |
| US11635974B2 (en) | Providing a different configuration of added functionality for each of the stages of predeployment, deployment, and post deployment using a layer of abstraction | |
| CN111552627A (en) | User interface testing method and device, storage medium and computer equipment | |
| WO2022252637A1 (en) | Browser-based rpa implementation method and apparatus, device, and medium | |
| JP2015510632A (en) | Client-side minimal download and simulated page navigation mechanism | |
| US20130007113A1 (en) | Creating web services from an existing web site | |
| CN110727575B (en) | Information processing method, system, device and storage medium | |
| KR20060079080A (en) | Methods and apparatus for evaluating aspects of a web page | |
| CN111177618A (en) | Website building method, device, equipment and computer readable storage medium | |
| CN102004695A (en) | Method and system for testing browser | |
| CN105556505A (en) | Legacy system | |
| CN109614319B (en) | Automatic testing method and device, electronic equipment and computer readable medium | |
| CN111539775A (en) | Application program management method and device | |
| CN113778442A (en) | System menu generating method, device, equipment and storage medium | |
| CN114036439A (en) | Website building method, device, medium and electronic equipment | |
| CN114461533A (en) | Method, system, electronic device and storage medium for automatic testing of Web page | |
| CN115268964A (en) | Data reinjection method and system, electronic device and readable storage medium |
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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |