CN111639019B - Code testing method, device and readable storage medium - Google Patents
Code testing method, device and readable storage medium Download PDFInfo
- Publication number
- CN111639019B CN111639019B CN202010335495.9A CN202010335495A CN111639019B CN 111639019 B CN111639019 B CN 111639019B CN 202010335495 A CN202010335495 A CN 202010335495A CN 111639019 B CN111639019 B CN 111639019B
- Authority
- CN
- China
- Prior art keywords
- branch
- file
- identifier
- static resource
- target
- 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
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the invention provides a code testing method, a code testing device and a readable storage medium. The code testing method comprises the following steps: receiving a resource request sent by target terminal equipment, analyzing the resource request to obtain a Uniform Resource Locator (URL) path corresponding to the target static resource file of the first branch and a first branch identifier, determining a physical path of the target static resource file according to the URL path and the first branch identifier, obtaining the target static resource file according to the physical path, and sending the target static resource file to the target terminal equipment so that the target terminal equipment tests new function codes of the first branch according to the target static resource file. Therefore, the method can support different personnel to test the new function codes of the branches responsible for the personnel at the same time, thereby improving the code testing efficiency.
Description
Technical Field
The present invention relates to the field of computer technologies, and in particular, to a code testing method and apparatus, and a readable storage medium.
Background
In the software industry, most companies do not build multiple test environments for one project due to cost factors, and basically only one test environment is provided. Since there is only one test environment, i.e. only one test server is provided. For an item, multiple people are responsible for different modules, each module corresponds to a branch, and different people need to test the branch in charge of the people.
Currently, if a person needs to test a branch, the updated file corresponding to the function code of the branch, or the file corresponding to the newly added function code (the file corresponding to the new function code) and the file corresponding to the un-updated function code (the file corresponding to the original function code) need to be uploaded to a code server, and the test server obtains the files corresponding to the function codes of the branch from the code server and stores the files corresponding to the function codes under one file, wherein the files corresponding to the function codes are static resource files.
However, since the files of the branches created by different personnel are all stored under the same file, the test server will cover the static resource files of the branches submitted by the personnel before the static resource files of the branches submitted by the personnel after the personnel, if there are multiple test/development personnel to simultaneously test (i.e. there are test/development personnel want to simultaneously test different branches), only the static resource files of the branches uploaded last time are effective, and the static resource files of other branches are covered. Therefore, the prior art does not support different personnel to test the branches respectively responsible at the same time, and only the functional code of one branch can be tested at a time, so that the testing efficiency is reduced.
Disclosure of Invention
The embodiment of the invention provides a code testing method, a code testing device and a readable storage medium, which are used for solving the problems that different personnel are not supported at present to test branches respectively responsible at the same time, only the functional code of one branch can be tested at a time, and the testing efficiency is reduced.
In a first aspect of an embodiment of the present invention, a code testing method is provided, which is executed in a test server, and includes:
receiving a resource request sent by target terminal equipment, and analyzing the resource request to obtain a Uniform Resource Locator (URL) path corresponding to a target static resource file of a first branch and a first branch identifier, wherein the first branch identifier is an identifier corresponding to the first branch selected by a user from at least three displayed branch identifiers, and the target static resource file comprises a file corresponding to an updated or newly added new function code of the first branch and a file corresponding to an unexplored original function code;
determining a physical path of the target static resource file according to the URL path and the first branch identifier;
and acquiring the target static resource file according to the physical path, and sending the target static resource file to the target terminal equipment so that the target terminal equipment tests the new function code of the first branch according to the target static resource file.
In a second aspect of the embodiment of the present invention, a code testing method is provided, which is executed in a terminal device, and includes:
a resource request is sent to a test server, wherein the resource request comprises a Uniform Resource Locator (URL) path corresponding to a target static resource file of a first branch and a first branch identifier, the first branch identifier is an identifier corresponding to the first branch, selected by a user from at least three displayed branch identifiers, and comprises a file corresponding to a new function code of the first branch and a file corresponding to an original function code;
receiving the target static resource file sent by the test server;
and testing the new function code of the first branch according to the target static resource file.
In a third aspect of the embodiment of the present invention, the method, provided in a test server, includes:
the receiving module is used for receiving a resource request sent by target terminal equipment and analyzing the resource request to obtain a Uniform Resource Locator (URL) path corresponding to a target static resource file of a first branch and a first branch identifier, wherein the first branch identifier is an identifier corresponding to the first branch selected by a user from at least three displayed branch identifiers, and the target static resource file comprises a file corresponding to an updated or newly added new function code of the first branch and a file corresponding to an unexplored original function code;
The determining module is used for determining the physical path of the target static resource file according to the URL path and the first branch identifier;
and the sending module is used for acquiring the target static resource file according to the physical path and sending the target static resource file to the target terminal equipment so that the target terminal equipment tests the new function code of the first branch according to the target static resource file.
A fourth aspect of an embodiment of the present invention is provided in a terminal device, including:
the system comprises a sending module, a testing server and a testing module, wherein the sending module is used for sending a resource request to the testing server, the resource request comprises a Uniform Resource Locator (URL) path corresponding to a target static resource file of a first branch and a first branch identifier, the first branch identifier is an identifier corresponding to the first branch selected by a user from at least three displayed branch identifiers, and the target static resource file comprises a file corresponding to a new function code of the first branch and a file corresponding to an original function code;
the receiving module is used for receiving the target static resource file sent by the test server;
and the testing module is used for testing the new function codes of the first branch according to the target static resource file.
In a fifth aspect of the embodiments of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the steps of the code testing method described above.
In a sixth aspect of the present invention, there is provided a code testing device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program implementing the steps of the code testing method described above when executed by the processor.
Aiming at the prior art, the invention has the following advantages:
according to the code testing method provided by the embodiment, the resource request sent by the target terminal equipment is received, the resource request is analyzed to obtain the URL path of the uniform resource locator corresponding to the target static resource file of the first branch and the first branch identifier, the physical path of the target static resource file is determined according to the URL path and the first branch identifier, the target static resource file is obtained according to the physical path, and the target static resource file is sent to the target terminal equipment, so that the target terminal equipment tests the new function code of the first branch according to the target static resource file. Because each branch corresponds to one branch identifier, and each static resource file of each branch corresponds to one URL path, after a user selects a first branch identifier on target terminal equipment, the user can refresh a page to enable the target terminal equipment to send a resource request to a test server, so that the test server receives the resource request and analyzes the resource request to obtain the URL path corresponding to the target static resource file of the first branch and the first branch identifier. And because the branch identification of each branch is different, the determined physical path is different from the physical paths of the static resource files of other branches according to the URL path and the first branch identification, namely the URL path and the branch identification corresponding to the static resource file of each branch are respectively corresponding to different physical paths, so that the static resource files under each physical path are not affected by each other, namely the static resource file of the branch created by one person cannot cover the static resource file of the branch created by other person, thereby supporting the simultaneous test of new function codes of the branches responsible by different persons, and improving the code test efficiency.
The foregoing description is only an overview of the present invention, and is intended to be implemented in accordance with the teachings of the present invention in order that the same may be more clearly understood and to make the same and other objects, features and advantages of the present invention more readily apparent.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to designate like parts throughout the figures. In the drawings:
FIG. 1 is a flow chart of steps of a code testing method according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating steps of another code testing method according to an embodiment of the present invention;
fig. 3 is a schematic structural diagram of a code testing device according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of another code testing device according to an embodiment of the present invention.
Detailed Description
In order that the above-recited objects, features and advantages of the present invention will become more readily apparent, a more particular description of the invention will be rendered by reference to the appended drawings and appended 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 step flowchart of a code testing method provided by an embodiment of the present invention, where the code testing method of the present embodiment is suitable for supporting different personnel to simultaneously test branch codes, and ensuring that branch codes submitted by a person do not cover branch codes submitted by other personnel before the person, so that a plurality of different personnel can test branches responsible for the person at the same time. The method can be executed on a test server, and the method of the embodiment comprises the following steps:
step 101, receiving a resource request sent by a target terminal device, and analyzing the resource request to obtain a URL path corresponding to a target static resource file of a first branch and a first branch identifier.
The number of the target terminal devices can be at least one, the first branch identifier is an identifier corresponding to the first branch selected by a user from at least three branch identifiers, and each branch identifier is a branch identifier corresponding to a plurality of branches created by the user on different terminal devices. The target static resource files include, for example, static resource files such as JS files and cascading style sheets (CSS, cascading Style Sheets). The JS file is a text script named by JS extension and places the JS script into a file class. The CSS file is a text file for loading CSS codes, and the CSS not only can statically modify a webpage, but also can dynamically format each element of the webpage in cooperation with various scripting languages.
The target static resource file includes a file corresponding to the updated or newly added new function code of the first branch and a file corresponding to the original function code that is not updated. After the branches are created, the user can update or add the function code of the created branches (the updated function code or the added function code is the new function code). For example, user 1 creates branch 1 on terminal device 1, user 2 creates branch 2 on terminal device 2, and both branch 1 and branch 2 include function code a and function code b, which are the original function codes. If the user 1 updates the function code a of the branch 1, the updated function code a is, for example, a new function code a1, and the new function code a1 corresponds to the file a1. The user 2 updates the function code b of the branch 2, and the updated function code b is, for example, a new function code b1, and the new function code b1 corresponds to the file b1. If the function code b of the branch 1 corresponds to the file b and the function code a of the branch 2 corresponds to the file a, the static resource file 1 of the branch 1 includes the file a1 and the file b, and the static resource file 2 of the branch 2 includes the file a and the file b1. Wherein, the file corresponding to each function code is a static resource file. Specifically, reference may be made to the following table 1:
TABLE 1
It should be noted that, when the user refreshes the test page on the terminal device, the terminal device sends a resource request to the test server, and the test server receives the resource request and parses the resource request to obtain a uniform resource locator (URL, uniform Resource Locator) path of the target static resource file and the first branch identifier selected by the user. The branch identification of at least three branches can be displayed on the terminal equipment, the at least three branches comprise a main branch and a created demand branch, the main branch is a default branch, and codes on the main branch are generally consistent with the latest version on line. The demand branches are branches planned according to project demands, the demand branches are cloned from main branches, and after the demand branches are created, users (developers) can update or add functional codes of the demand branches. For example, the new function code may enable, for example, changing a photo of a property broker from square to circular.
Different users can create branches on respective terminal devices, each branch corresponds to a branch identifier, and static resource files of each branch correspond to a URL path. If there are two user-created demand branches in total, then at least two branches include a main branch and two demand branches in total. Three branch identifiers can be displayed on the terminal device, so that a user can select an identifier corresponding to a first branch (a first branch identifier) from the displayed three branch identifiers.
Step 102, determining the physical path of the target static resource file according to the URL path and the first branch identifier.
Because the branch identification of each branch is unique, that is, the branch identifications of each branch are different from each other, the physical paths of the target static resource files of the first branch are different from the physical paths of the static resource files of other branches according to the URL path and the first branch identification, that is, the physical paths of each branch are different from each other, so that the static resource files of each branch are not affected by each other, the static resource files of the branches created by one person do not cover the static resource files of the branches created by other persons, and therefore, the simultaneous test of new function codes of the branches responsible for the different persons can be supported.
Step 103, obtaining a target static resource file according to the physical path, and sending the target static resource file to the target terminal equipment, so that the target terminal equipment tests the new function code of the first branch according to the target static resource file.
After the target terminal device obtains the target static resource file, the function code updated by the first branch can be tested according to the target static resource file, namely, the page is rendered according to the target static resource file, and the rendered page is displayed, so that a developer can check whether a new function corresponding to the updated function code is normally realized through the rendered page. For example, the new function code is the new function code a1, the photo of the property broker can be changed from square to round, if the rendered page can realize the function and has no abnormality, the user 1 can determine that the function of the function code tested at this time has been realized, and then if the user 1 retests the function, the steps 101 to 103 can be continuously executed to test the function for multiple times.
It should be noted that, when the user 1 tests the new function code a1, since the static resource file of the branch 1 and the static resource file of the branch 2 do not affect each other, the user 2 can test the new function code b1 of the user at the same time, so that different users can test the new function codes of different branches at the same time.
According to the code testing method provided by the embodiment, as different users can create branches on respective terminal equipment, each branch corresponds to one branch identifier, each static resource file of each branch corresponds to one URL path, after the user selects a first branch identifier on target terminal equipment, the user can send a resource request to a testing server through refreshing a page, so that the testing server receives the resource request and analyzes the resource request to obtain the URL path corresponding to the target static resource file of the first branch and the first branch identifier. And because the branch identification of each branch is different, the determined physical path is different from the physical paths of the static resource files of other branches according to the URL path and the first branch identification, namely the URL path and the branch identification corresponding to the static resource file of each branch are respectively corresponding to different physical paths, so that the static resource files under each physical path are not affected by each other, namely the static resource file of the branch created by one person cannot cover the static resource file of the branch created by other person, thereby supporting the simultaneous test of new function codes of the branches responsible by different persons, and improving the code test efficiency.
Referring to fig. 2, fig. 2 is a flowchart illustrating steps of another code testing method according to an embodiment of the present invention, where the method includes the following steps:
step 201, the terminal device creates a first branch.
For example, user 1 may create branch 1 through terminal device 1 and user 2 may create branch 2 through terminal device 2.
Step 202, the terminal device pushes files corresponding to the function codes of the first branch to the code server.
Wherein each function code of the first branch includes a new function code and an original function code of the first branch. The new function code is updated function code or newly added function code, and the original function code is the function code of the first branch which is not updated.
It should be noted that after the developer passes the test of the new branch code on the own terminal device, the developer may modify the configuration file in the terminal device, and modify the IP in the configuration file to the IP address of the test server, so that the file corresponding to the new branch code may be pushed to the test server. In connection with the above description of the embodiment by way of example, if the user 1 updates the function code a of the branch 1, the updated function code a is updated, for example, to a new function code a1, the new function code a1 corresponding to the static resource file a1. The user 2 updates the function code b of the branch 2, and the updated function code b is updated to a new function code b1, for example, and the new function code b1 corresponds to the static resource file b1. The terminal device 1 pushes the file corresponding to the new function code a1 to the code server and at the same time the terminal device 2 can push the file corresponding to the new function code b1 to the code server. After pushing the file corresponding to the new function code to the code server, the code server sends a notification message to the test server to notify the test server to acquire the file corresponding to each branched function code from the code server. For example, in step 203, the test server obtains files corresponding to the function codes of the first branch from the code server (e.g., the test server may obtain static resource file 1 of branch 1 and static resource file 2 of branch 2, each function code of branch 1 including new function code a1 and original function code b, and each function code of branch 2 including original function code a and new function code b 1).
Step 203, when the terminal device pushes the file corresponding to the new function code of the first branch to the code server, the test server obtains the file corresponding to each function code of the first branch from the code server, generates a branch folder corresponding to the first branch identifier, and stores the files corresponding to each function code of the first branch in the branch folder.
When each terminal device pushes a file corresponding to a new function code of each branch to a code server, the file corresponding to each function code of each branch is obtained from the code server, a branch folder corresponding to each branch identifier is generated, and the files corresponding to each function code of each branch are stored in the corresponding branch folder. That is, the static resource files of each demand branch are managed respectively, and the static resource files of each demand branch do not affect each other.
For example, when the terminal device 1 pushes a file (static resource file a 1) corresponding to the new function code a1 of the branch 1 to the code server and the terminal device 2 pushes a file (static resource file b 1) corresponding to the new function code b1 of the branch 2 to the code server, the test server acquires the files corresponding to the respective function codes of the branch 1 from the code server, generates a branch folder 1 corresponding to the branch identification (identification of the branch 1), and stores the files corresponding to the respective function codes of the branch 1 in the branch folder 1. The test server acquires the files corresponding to the respective function codes of the branch 2 from the code server, generates the branch folder 2 corresponding to the branch identification (the identification of the branch 2), and stores the files corresponding to the respective function codes of the branch 2 in the branch folder 2. Because the static resource files corresponding to different branches are stored in different branch folders, even if different terminal devices push the files corresponding to the new function codes of the created branches to the code server at the same time, the test server cannot cover the acquired files corresponding to the function codes of one branch with the files corresponding to the function codes of the other branch. Or when the terminal equipment 1 is later than the terminal equipment 2 and pushes the file corresponding to the new function code a1 of the branch 1 to the test server, the test server cannot cover the file corresponding to each function code of the branch 1 with the file corresponding to each function code of the branch 2, so that different personnel can be supported to test the new function codes of different branches at the same time, and the code test efficiency is improved.
And 204, the terminal equipment sends a resource request to the test server.
It should be noted that, for step 204, if the user opens the test page for the first time, the storage container (Cookie) included in the resource request sent in step 204 may be empty or a default branch identifier (main branch identifier). If the storage container in step 204 is empty or identified for a default branch, the target static resource file includes the static resource file of the default branch. I.e. the user opens the test page for the first time, the first branch identification has not been selected from the displayed branch information, i.e. the user has not yet started testing the created first branch.
For step 204, if it is the user that refreshes the test page, i.e., the user selects the created first branch identification from the displayed branch information, the branch identification in the storage container is the first branch identification. The resource request sent by the terminal equipment to the test server comprises a storage container, namely the terminal equipment sends the first branch identifier to the test server. The following step is illustrated with the first branch identification created included in the storage container as an example.
Step 205, the test server receives the resource request sent by the terminal device, and parses the resource request to obtain the URL path corresponding to the created target static resource file of the first branch and the first branch identifier.
The first branch identifier is an identifier corresponding to the first branch selected by a user from the displayed at least three branch identifiers, and the target static resource file comprises a file corresponding to a new function code of the first branch and a file corresponding to an original function code.
Step 206, the test server determines the physical path of the target static resource file according to the URL path and the first branch identifier.
Wherein, according to the URL path and the first branch identifier, determining the physical path of the target static resource file can be realized by the following steps:
judging whether the target static resource file is stored in the test server according to the URL path;
and under the condition that the target static resource file is stored in the test server, determining the physical path of the target static resource file according to the URL path and the first branch identifier.
Alternatively, in the case where the target static resource file is not stored in the test server, the target static resource file is acquired from the online server according to the URL path. Because some test pages can refer to static resource files of a third party platform (an online server), if the static resource files of the third party platform are not synchronized with the latest codes to the test server, or the static resource files of the third party platform are not uploaded to the test server at all, the test pages cannot be tested, the test flow is influenced, and the test efficiency is reduced.
In this embodiment, whether the target static resource file is stored in the test server may be determined according to the URL path, and if the target static resource file is not stored in the test server, the target static resource file may be obtained from the online server according to the URL path, so that the obtained target static resource file may be guaranteed to be the latest static resource file, and normal test on the test page may be guaranteed.
Step 207, the test server obtains the target static resource file according to the physical path, and sends the target static resource file to the target terminal device.
And step 208, the terminal equipment receives the target static resource file sent by the test server.
It should be noted that, if the user opens the test page for the first time, the storage container in the resource request sent by the terminal device to the test server is empty or is a default branch identifier, the test server determines the physical path of the static resource file of the default branch according to the URL path and the default branch identifier corresponding to the static resource file of the default branch, obtains the static resource file of the default branch according to the physical path of the static resource file of the default branch, and sends the static resource file of the default branch to the terminal device, and after receiving the static resource file of the default branch, the terminal device still displays the test page when opening for the first time, that is, in this case, the test is not started to test the new function code of the first branch yet.
If the test page is opened for the first time, after the test server sends the static resource file of the default branch to the terminal device, the method further comprises the following steps:
the test server sends a script file to the terminal equipment;
the terminal equipment receives a script file sent by a test server;
the terminal device executes the script file to send a branch information request to the test server and generate a panel.
The test server responds to the branch information request and sends the branch information to the target terminal equipment.
And the terminal equipment receives the branch information sent by the test server and displays the branch information on the panel.
The branch information comprises at least one item name of the test page and at least one branch identifier, and each item name corresponds to at least one branch identifier;
it should be noted that, the script file may be a JS script file, and the terminal device may display the branch information on the panel by executing the JS script file, so that the user may select the branch to be tested from the branch information displayed on the panel, that is, select which branch identifier may test the new function code of the branch corresponding to the branch identifier under which item.
Step 209, testing the new function code of the first branch according to the target static resource file.
Step 210, the terminal device sends a switching branch request to the test server, where the switching branch request includes a second branch identifier selected by the user.
Step 211, the test server responds to the switching branch request and sends a switching branch response to the target terminal equipment.
Correspondingly, the terminal equipment receives a switching branch response sent by the test server and writes the second branch identifier into the storage container, wherein the switching branch response comprises the second branch identifier. After the terminal device writes the second branch identification into the storage container, steps 204 to 209 may be continued by refreshing the page, so that the new function code of the second branch may be tested.
Referring to fig. 3, fig. 3 is a schematic structural diagram of a code testing device according to an embodiment of the present invention, where the device 300 is disposed on a testing server, and may include:
a receiving module 310, configured to receive a resource request sent by a target terminal device, and parse the resource request to obtain a URL path corresponding to a target static resource file of a created first branch, and a first branch identifier, where the first branch identifier is an identifier corresponding to the first branch selected by a user from at least three displayed branch identifiers, and the target static resource file includes a file corresponding to an updated or newly added new function code of the first branch and a file corresponding to an unexplored original function code;
A determining module 320, configured to determine a physical path of the target static resource file according to the URL path and the first branch identifier;
and the sending module 330 is configured to obtain the target static resource file according to the physical path, and send the target static resource file to the target terminal device, so that the target terminal device tests the new function code of the first branch according to the target static resource file.
Optionally, the method further comprises:
and the generation module is used for acquiring the files corresponding to the function codes of each branch from the code server when each terminal device pushes the files corresponding to the function codes of each branch to the code server, generating a branch folder corresponding to each branch identifier, and storing the files corresponding to the function codes of each branch in the corresponding branch folder respectively, wherein each function code comprises a new function code and an original function code of each branch.
Optionally, the sending module 330 is further configured to send a script file to the target terminal device, so that the target terminal device sends a branch information request to the test server by executing the script file;
The receiving module 310 is further configured to receive the branch information request sent by the target terminal device;
the sending module 330 is further configured to send, in response to the request for branch information, branch information to the target terminal device, so that the target terminal device displays the branch information, where the branch information includes at least one item name of the test page and at least one branch identifier, and each item name corresponds to at least one branch identifier.
Optionally, the receiving module 310 is further configured to receive a handover branch request sent by the target terminal device, where the handover branch request includes the second branch identifier selected by the user;
the sending module 330 is further configured to send a switch branch response to the target terminal device in response to the switch branch request, so that the target terminal device writes the second branch identifier into a storage container, where the switch branch response includes the second branch identifier.
Optionally, the determining module is specifically configured to determine, according to the URL path, whether the target static resource file is stored in the test server;
And under the condition that the target static resource file is stored in the test server, determining a physical path of the target static resource file according to the URL path and the first branch identifier.
Optionally, the obtaining module 330 is further configured to obtain, according to the URL path, the target static resource file from an online server if the target static resource file is not stored in the test server.
Optionally, the URL path includes an item identifier of the page, a version identifier of an item corresponding to the item identifier, and a file identifier, and the physical path includes the item identifier, the version identifier, the first branch identifier, and the file identifier.
Referring to fig. 4, fig. 3 is a schematic structural diagram of another code testing apparatus according to an embodiment of the present invention, where the apparatus 400 is disposed in a terminal device, and includes:
a sending module 410, configured to send a resource request to a test server, where the resource request includes a URL path corresponding to a target static resource file of a first branch, and a first branch identifier, where the first branch identifier is an identifier corresponding to the first branch selected by a user from at least three displayed branch identifiers, and the target static resource file includes a file corresponding to a new function code of the first branch and a file corresponding to an original function code;
A receiving module 420, configured to receive the target static resource file sent by the test server;
and the test module 430 is configured to test the new function code of the first branch according to the target static resource file.
Optionally, the method further comprises:
a creating module, configured to create the first branch;
and the pushing module is used for pushing the file corresponding to the new function code of the first branch to the code server so that the test server obtains the file corresponding to each function code of the first branch from the code server, generates a branch folder corresponding to the first branch identifier, and stores the file corresponding to each function code of the first branch in the branch folder.
Optionally, the method further comprises:
the script file receiving module is used for receiving the script file sent by the test server;
the execution module is used for executing the script file to send a branch information request to the test server and generate a panel, wherein the branch information request is used for requesting branch information of a test page, the branch information comprises at least one project name and at least one branch identifier of the test page, and each project name corresponds to at least one branch identifier;
And the display module is used for displaying the branch information on the panel.
Optionally, the sending module 410 is further configured to send a switch branch request to the test server, where the switch branch request includes the second branch identifier selected by the user;
the receiving module 420 is further configured to receive a switch branch response sent by the test server, and write a second branch identifier into a storage container, where the switch branch response includes the second branch identifier.
In addition, the embodiment of the invention also provides a code testing device, which comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein the computer program realizes the processes of the code testing method embodiment of the embodiment when being executed by the processor, and can achieve the same technical effects, and the repetition is avoided, so that the description is omitted.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the processes of the code testing method embodiment described above, and can achieve the same technical effects, and in order to avoid repetition, the description is omitted here. The computer readable storage medium may be a Read-Only Memory (ROM), a random access Memory (RandomAccess Memory, RAM), a magnetic disk, an optical disk, or the like.
The embodiment of the invention also provides a computer program which can be stored on a cloud or local storage medium. Which when executed by a computer or processor is adapted to carry out the respective steps of the code testing method of an embodiment of the invention and to carry out the respective modules in the code testing device according to an embodiment of the invention.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
As will be readily appreciated by those skilled in the art: any combination of the above embodiments is possible, and thus is an embodiment of the present invention, but the present specification is not limited by the text.
The code testing methods provided herein are not inherently related to any particular computer, virtual system, or other apparatus. Various general-purpose systems may also be used with the teachings herein. The required structure for a system constructed with aspects of the present invention will be apparent from the description above. In addition, the present invention is not directed to any particular programming language. It will be appreciated that the teachings of the present invention described herein may be implemented in a variety of programming languages, and the above description of specific languages is provided for disclosure of enablement and best mode of the present invention.
In the description provided herein, numerous specific details are set forth. However, it is understood that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.
Similarly, it should be appreciated that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various inventive aspects. However, the disclosed method should not be construed as reflecting the intention that: i.e., the claimed invention requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this invention.
Those skilled in the art will appreciate that the modules in the apparatus of the embodiments may be adaptively changed and disposed in one or more apparatuses different from the embodiments. The modules or units or components of the embodiments may be combined into one module or unit or component and, furthermore, they may be divided into a plurality of sub-modules or sub-units or sub-components. Any combination of all features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or units of any method or apparatus so disclosed, may be used in combination, except insofar as at least some of such features and/or processes or units are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings), may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Furthermore, those skilled in the art will appreciate that while some embodiments described herein include some features but not others included in other embodiments, combinations of features of different embodiments are meant to be within the scope of the invention and form different embodiments. For example, in the claims, any of the claimed embodiments may be used in any combination.
Various component embodiments of the invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art will appreciate that some or all of the functions of some or all of the components in a code testing method according to an embodiment of the present invention may be implemented in practice using a microprocessor or Digital Signal Processor (DSP). The present invention can also be implemented as an apparatus or device program (e.g., a computer program and a computer program product) for performing a portion or all of the methods described herein. Such a program embodying the present invention may be stored on a computer readable medium, or may have the form of one or more signals. Such signals may be downloaded from an internet website, provided on a carrier signal, or provided in any other form.
It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention may be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the unit claims enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, third, etc. do not denote any order. These words may be interpreted as names.
Claims (16)
1. A code testing method, executed in a test server, comprising:
when each terminal device pushes a file corresponding to each function code of each branch to a code server, acquiring the file corresponding to each function code of each branch from the code server, generating a branch folder corresponding to each branch identifier, and storing the file corresponding to each function code of each branch in the corresponding branch folder, wherein each function code comprises a new function code and an original function code of each branch;
Receiving a resource request sent by target terminal equipment, and analyzing the resource request to obtain a Uniform Resource Locator (URL) path corresponding to a target static resource file of a first created branch and a first branch identifier, wherein the first branch identifier is an identifier corresponding to the first branch, selected by a user from at least three displayed branch identifiers, the target static resource file comprises a file corresponding to an updated or newly-added new function code of the first branch and a file corresponding to an unexplored original function code, the at least three branches comprise a main branch and a demand branch, the main branch is a default branch consistent with the latest version on line, the demand branch is a branch created by different users on respective terminal equipment, the main branch is used for providing a clone branch for the demand branch, and the demand branch is used for updating or newly-adding the function code of the clone branch according to user demands;
determining a physical path of the target static resource file according to the URL path and the first branch identifier, wherein the branch identifier of each branch is unique, and the static resource files of each branch do not affect each other;
According to the physical path, acquiring the target static resource file, and sending the target static resource file to the target terminal equipment, so that the target terminal equipment tests the new function code of the first branch according to the target static resource file;
transmitting a script file to the target terminal equipment so that the target terminal equipment transmits a branch information request to the test server by executing the script file;
receiving the branch information request sent by the target terminal equipment;
and sending branch information to the target terminal equipment in response to the branch information request so as to enable the target terminal equipment to display the branch information, wherein the branch information comprises at least one item name of the test page and at least one branch identifier, and each item name corresponds to at least one branch identifier.
2. The method according to claim 1, further comprising, after said sending of the branch information to the target terminal device:
receiving a switching branch request sent by the target terminal equipment, wherein the switching branch request comprises a second branch identifier selected by the user;
And responding to the switching branch request, sending a switching branch response to the target terminal equipment so that the target terminal equipment writes the second branch identifier into a storage container, wherein the switching branch response comprises the second branch identifier.
3. The method of claim 1, wherein the determining the physical path of the target static resource file based on the URL path and the first branch identification comprises:
judging whether the target static resource file is stored in the test server according to the URL path;
and under the condition that the target static resource file is stored in the test server, determining a physical path of the target static resource file according to the URL path and the first branch identifier.
4. A method according to claim 3, further comprising:
and under the condition that the target static resource file is not stored in the test server, acquiring the target static resource file from an online server according to the URL path.
5. The method of claim 1, wherein the URL path includes an item identification of a page, a version identification of an item to which the item identification corresponds, and a file identification, and wherein the physical path includes the item identification, the version identification, the first branch identification, and the file identification.
6. A code testing method, which is executed in a terminal device, comprising:
creating a first branch;
pushing a file corresponding to the new function code of the first branch to a code server, so that a test server obtains the file corresponding to each function code of the first branch from the code server, generates a branch folder corresponding to a first branch identifier, and stores the files corresponding to each function code of the first branch in the branch folder;
a resource request is sent to a test server, wherein the resource request comprises a Uniform Resource Locator (URL) path corresponding to a target static resource file of a first branch and a first branch identifier, the first branch identifier is an identifier corresponding to the first branch, which is selected by a user from at least three displayed branch identifiers, the target static resource file comprises a file corresponding to a new function code of the first branch and a file corresponding to an original function code, the at least three branches comprise a main branch and a demand branch, the main branch is a default branch consistent with the latest version on line, the demand branch is a branch created by different users on respective terminal equipment, the main branch is used for providing a clone branch for the demand branch, and the demand branch is used for updating or adding the function code of the clone branch according to user demands;
Receiving the target static resource file sent by the test server;
testing the new function code of the first branch according to the target static resource file; receiving a script file sent by the test server;
executing the script file to send a branch information request to the test server and generate a panel, wherein the branch information request is used for requesting branch information of a test page, the branch information comprises at least one project name and at least one branch identifier of the test page, and each project name corresponds to at least one branch identifier;
the branching information is displayed on the panel.
7. The method of claim 6, further comprising, after said testing the new function code of the first branch based on the target static resource file:
sending a switching branch request to the test server, wherein the switching branch request comprises a second branch identifier selected by the user;
and receiving a switching branch response sent by the test server, and writing a second branch identifier into a storage container, wherein the switching branch response comprises the second branch identifier.
8. A code testing device, characterized in that it is provided in a test server, comprising:
the generating module is used for acquiring the files corresponding to the function codes of each branch from the code server when each terminal device pushes the files corresponding to the function codes of each branch to the code server, generating a branch folder corresponding to each branch identifier, and storing the files corresponding to the function codes of each branch in the corresponding branch folder respectively, wherein each function code comprises a new function code and an original function code of each branch;
the system comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a resource request sent by target terminal equipment and analyzing the resource request to obtain a uniform resource locator URL path corresponding to a target static resource file of a first created branch and a first branch identifier, wherein the first branch identifier is an identifier corresponding to the first branch, selected by a user from at least three displayed branch identifiers, the target static resource file comprises a file corresponding to an updated or newly added new function code of the first branch and a file corresponding to an un-updated original function code, the at least three branches comprise a main branch and a demand branch, the main branch is a default branch consistent with the latest version on line, the demand branch is a branch created by different users on respective terminal equipment, and the main branch is used for providing a clone branch for the demand branch;
The determining module is used for determining the physical path of the target static resource file according to the URL path and the first branch identifier, the branch identifier of each branch is unique, and the static resource files of each branch do not affect each other;
the sending module is used for acquiring the target static resource file according to the physical path and sending the target static resource file to the target terminal equipment so that the target terminal equipment tests the new function code of the first branch according to the target static resource file;
the sending module is further configured to send a script file to the target terminal device, so that the target terminal device sends a branch information request to the test server by executing the script file;
the receiving module is further configured to receive the branch information request sent by the target terminal device;
the sending module is further configured to send, in response to the branch information request, branch information to the target terminal device, so that the target terminal device displays the branch information, where the branch information includes at least one item name of the test page and at least one branch identifier, and each item name corresponds to at least one branch identifier.
9. The apparatus of claim 8, wherein the device comprises a plurality of sensors,
the receiving module is further configured to receive a switch branch request sent by the target terminal device, where the switch branch request includes a second branch identifier selected by the user;
the sending module is further configured to send a switch branch response to the target terminal device in response to the switch branch request, so that the target terminal device writes the second branch identifier into a storage container, where the switch branch response includes the second branch identifier.
10. The apparatus of claim 8, wherein the determining module is specifically configured to determine, according to the URL path, whether the target static resource file is stored in the test server;
and under the condition that the target static resource file is stored in the test server, determining a physical path of the target static resource file according to the URL path and the first branch identifier.
11. The apparatus of claim 10, wherein the obtaining module is further configured to obtain the target static resource file from an online server according to the URL path if the target static resource file is not stored in the test server.
12. The apparatus of claim 8, wherein the URL path includes an item identification of a page, a version identification of an item to which the item identification corresponds, and a file identification, and wherein the physical path includes the item identification, the version identification, the first branch identification, and the file identification.
13. A code testing device, characterized in that it is provided in a terminal device, comprising:
the creation module is used for creating a first branch;
the pushing module is used for pushing the file corresponding to the new function code of the first branch to the code server so that the test server obtains the file corresponding to each function code of the first branch from the code server, generates a branch folder corresponding to the first branch identifier, and stores the file corresponding to each function code of the first branch in the branch folder;
a sending module, configured to send a resource request to a test server, where the resource request includes a uniform resource locator URL path corresponding to a target static resource file of a first branch, and a first branch identifier, where the first branch identifier is an identifier corresponding to the first branch, selected by a user from at least three displayed branch identifiers, the target static resource file includes a file corresponding to a new function code of the first branch and a file corresponding to an original function code, the at least three branches include a main branch and a required branch, the main branch is a default branch consistent with a latest version on line, the required branch is a branch created by a different user on a respective terminal device, and the main branch is used to provide a clone branch for the required branch, and the required branch is used to update or add a function code of the clone branch according to a user requirement;
The receiving module is used for receiving the target static resource file sent by the test server;
the testing module is used for testing the new function codes of the first branch according to the target static resource file;
the script file receiving module is used for receiving the script file sent by the test server;
the execution module is used for executing the script file to send a branch information request to the test server and generate a panel, wherein the branch information request is used for requesting branch information of a test page, the branch information comprises at least one project name and at least one branch identifier of the test page, and each project name corresponds to at least one branch identifier;
and the display module is used for displaying the branch information on the panel.
14. The apparatus of claim 13, wherein the device comprises a plurality of sensors,
the sending module is further configured to send a switching branch request to the test server, where the switching branch request includes the second branch identifier selected by the user;
the receiving module is further configured to receive a switching branch response sent by the test server, and write a second branch identifier into the storage container, where the switching branch response includes the second branch identifier.
15. A computer-readable storage medium, on which a computer program is stored, which computer program, when being executed by a processor, implements the code testing method of any one of claims 1 to 5 or the code testing method of any one of claims 6, 7.
16. A data packet presentation device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program when executed by the processor implementing the steps of the code testing method of any one of claims 1 to 5 or the code testing method of any one of claims 6 and 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010335495.9A CN111639019B (en) | 2020-04-24 | 2020-04-24 | Code testing method, device and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010335495.9A CN111639019B (en) | 2020-04-24 | 2020-04-24 | Code testing method, device and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111639019A CN111639019A (en) | 2020-09-08 |
| CN111639019B true CN111639019B (en) | 2023-08-25 |
Family
ID=72333226
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010335495.9A Active CN111639019B (en) | 2020-04-24 | 2020-04-24 | Code testing method, device and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111639019B (en) |
Families Citing this family (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112148354B (en) * | 2020-09-27 | 2023-07-25 | 网易（杭州）网络有限公司 | Game starting method and device |
| CN112214413B (en) * | 2020-10-27 | 2024-01-16 | 北京字节跳动网络技术有限公司 | Application program testing method, device, equipment and storage medium |
| CN112433721B (en) * | 2020-11-27 | 2022-03-04 | 北京五八信息技术有限公司 | Application modularization processing method and device, electronic equipment and storage medium |
| CN112631894B (en) * | 2020-12-02 | 2024-07-23 | 北京水滴科技集团有限公司 | Code detection method, device, storage medium and computer equipment |
| CN112817848B (en) * | 2021-01-28 | 2024-03-12 | 北京达佳互联信息技术有限公司 | Test information display method and device, electronic equipment and storage medium |
| CN112817849B (en) * | 2021-01-28 | 2024-06-04 | 北京达佳互联信息技术有限公司 | Test data processing method, device, equipment and storage medium |
| CN112988584A (en) * | 2021-03-22 | 2021-06-18 | 深圳云之家网络有限公司 | Service testing method, device, computer equipment and storage medium |
| CN115485657A (en) * | 2021-03-30 | 2022-12-16 | 京东方科技集团股份有限公司 | Program data packet generation method, device, equipment and storage medium |
| CN113568620B (en) * | 2021-06-16 | 2023-08-22 | 杭州华橙软件技术有限公司 | Code file processing method, device, equipment and medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105404519A (en) * | 2015-12-07 | 2016-03-16 | 青岛海信电器股份有限公司 | Version control method, code testing method and system |
| CN105867903A (en) * | 2015-12-29 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Method and device or splitting code library |
| CN106708740A (en) * | 2017-01-10 | 2017-05-24 | 网易（杭州）网络有限公司 | Script testing method and device |
| CN106886445A (en) * | 2016-06-23 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Java packets generation method and equipment and information extracting method and equipment |
| CN108255509A (en) * | 2018-02-07 | 2018-07-06 | 平安好房（上海）电子商务有限公司 | Using dispositions method, device, equipment and readable storage medium storing program for executing |
| CN109002295A (en) * | 2018-10-19 | 2018-12-14 | 武汉斗鱼网络科技有限公司 | A kind of static code scan method, system, server and storage medium |
| CN109960643A (en) * | 2017-12-22 | 2019-07-02 | 网宿科技股份有限公司 | A kind of code test method and device |
| CN110532029A (en) * | 2019-09-04 | 2019-12-03 | 深圳前海微众银行股份有限公司 | Small routine generation method, device, equipment and computer readable storage medium |
| US10534701B1 (en) * | 2019-06-17 | 2020-01-14 | Capital One Services, Llc | API driven continuous testing systems for testing disparate software |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8099721B2 (en) * | 2008-06-17 | 2012-01-17 | Microsoft Corporation | Parsing of declarations in all branches of preprocessor conditionals |
| US8839203B2 (en) * | 2011-05-25 | 2014-09-16 | Microsoft Corporation | Code coverage-based taint perimeter detection |
-
2020
- 2020-04-24 CN CN202010335495.9A patent/CN111639019B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105404519A (en) * | 2015-12-07 | 2016-03-16 | 青岛海信电器股份有限公司 | Version control method, code testing method and system |
| CN105867903A (en) * | 2015-12-29 | 2016-08-17 | 乐视致新电子科技（天津）有限公司 | Method and device or splitting code library |
| CN106886445A (en) * | 2016-06-23 | 2017-06-23 | 阿里巴巴集团控股有限公司 | Java packets generation method and equipment and information extracting method and equipment |
| CN106708740A (en) * | 2017-01-10 | 2017-05-24 | 网易（杭州）网络有限公司 | Script testing method and device |
| CN109960643A (en) * | 2017-12-22 | 2019-07-02 | 网宿科技股份有限公司 | A kind of code test method and device |
| CN108255509A (en) * | 2018-02-07 | 2018-07-06 | 平安好房（上海）电子商务有限公司 | Using dispositions method, device, equipment and readable storage medium storing program for executing |
| CN109002295A (en) * | 2018-10-19 | 2018-12-14 | 武汉斗鱼网络科技有限公司 | A kind of static code scan method, system, server and storage medium |
| US10534701B1 (en) * | 2019-06-17 | 2020-01-14 | Capital One Services, Llc | API driven continuous testing systems for testing disparate software |
| CN110532029A (en) * | 2019-09-04 | 2019-12-03 | 深圳前海微众银行股份有限公司 | Small routine generation method, device, equipment and computer readable storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 一种抵抗符号执行的路径分支混淆技术;王志 等;《电子学报》(第05期);870-878 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111639019A (en) | 2020-09-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111639019B (en) | Code testing method, device and readable storage medium | |
| CN111240653B (en) | Interface document generation method, device and readable storage medium | |
| US10180833B2 (en) | Cooperative web-assisted deep link redirection | |
| CN106484383A (en) | page rendering method, device and equipment | |
| JP2019032883A (en) | Method, apparatus, server and system for implementing web application | |
| US20130036413A1 (en) | Methods and apparatus for bug-fix notifications | |
| US9417992B2 (en) | Web portal API test report generation | |
| CN104699612A (en) | Processing method, equipment and system used in software testing | |
| CN104798094B (en) | Determine the configuration of content item display environment | |
| CN110442815B (en) | Page generation method, system, device and computer readable storage medium | |
| CN101571809A (en) | Implementation method of plug-in registration and device thereof | |
| CN101853152B (en) | Method and system for generating graphical user interface | |
| US9304894B2 (en) | Code-free testing framework | |
| CN111913738A (en) | Access request processing method, device, computing equipment and medium | |
| US9292252B2 (en) | Methods and apparatus for voiced-enabling a web application | |
| CN115065652B (en) | Message reply method and device, storage medium and computer equipment | |
| CN109871217A (en) | Application program installation method and device based on application shop | |
| CN110020242A (en) | A kind of document reading progress synchronous method and device based on Web | |
| CN111859077A (en) | Data processing method, device, system and computer readable storage medium | |
| CN107229565B (en) | Test method and device | |
| CN104217021B (en) | Reading server, terminal device and its method for showing reading content | |
| US8631008B1 (en) | Systems and methods for indexing electronic content that involves external interaction | |
| CN109614230A (en) | Resource virtualizing method, apparatus and electronic equipment | |
| CN115080109A (en) | Multi-cloud-end environment joint debugging method, device, system and equipment based on hybrid development | |
| CN103023910B (en) | Data transmission method between mobile device and computing device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |