CN112224246A - Test report generation method and device based on interface test - Google Patents
Test report generation method and device based on interface test Download PDFInfo
- Publication number
- CN112224246A CN112224246A CN202011468385.6A CN202011468385A CN112224246A CN 112224246 A CN112224246 A CN 112224246A CN 202011468385 A CN202011468385 A CN 202011468385A CN 112224246 A CN112224246 A CN 112224246A
- Authority
- CN
- China
- Prior art keywords
- test
- interface
- report
- conclusion
- test report
- 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.)
- Granted
Links
Images
Classifications
-
- B—PERFORMING OPERATIONS; TRANSPORTING
- B61—RAILWAYS
- B61L—GUIDING RAILWAY TRAFFIC; ENSURING THE SAFETY OF RAILWAY TRAFFIC
- B61L27/00—Central railway traffic control systems; Trackside control; Communication systems specially adapted therefor
- B61L27/60—Testing or simulation
Landscapes
- Engineering & Computer Science (AREA)
- Mechanical Engineering (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a test report generation method and device based on interface test, relates to the technical field of railway signal system test, and mainly aims to summarize test results of multiple rounds of interface test and determine a final test conclusion of interface code bits in a test report. The main technical scheme of the invention is as follows: acquiring a test result and test task information of the interface test of the current round, wherein the test task information at least comprises identification information and interface types of whether the interface test of the current round is the first round; judging whether the interface test of the current round is the first round test or not according to the identification information; if the test is the first round of test, generating a test report according to a test report template corresponding to the interface type and a test result, and recording a test conclusion of the interface code bit in the test report; and if the test is not the first round of test, updating the old version of test report of the interface test by using the test result, and generating a new version of test report, wherein the test conclusion of the interface code bit in the new version of test report is obtained by calculating the test result based on a preset strategy.
Description
Technical Field
The invention relates to the technical field of railway signal system testing, in particular to a test report generation method and device based on interface testing.
Background
In the field of the current railway signal system, due to the particularity of the industry, the complexity of the scene and the variability of the system expression mode, the related work such as the summary statistics of the interface test results of the project level and the like is still processed in a manual mode. No specific tool in the current actual test activities can effectively realize automatic summarization of interface test results and automatic determination of final conclusions in test reports.
Disclosure of Invention
In view of the above problems, the present invention provides a method and an apparatus for generating a test report based on interface tests, and mainly aims to summarize test results of multiple rounds of interface tests and determine a final test conclusion of interface code bits in a test report.
In order to achieve the purpose, the invention mainly provides the following technical scheme:
in a first aspect, the present invention provides a test report generation method based on interface testing, including:
acquiring a test result and test task information of the interface test of the current round, wherein the test task information at least comprises identification information and interface types of whether the interface test of the current round is the first round;
judging whether the interface test of the current round is the first round test or not according to the identification information;
if the interface test of the current round is the first round, generating a test report according to a test report template corresponding to the interface type and the test result, wherein the test report records a test conclusion of interface code bits;
and if the interface test of the current round is not the first round, updating the old version test report of the interface test by using the test result to generate a new version test report, wherein the test conclusion of the interface code bit in the new version test report is obtained by calculating the test result based on a preset strategy.
Preferably, generating a test report according to the test report template corresponding to the interface type and the test result includes:
acquiring a test report template of a corresponding interface according to the interface type;
determining a test record page added in the test report template according to the test result;
and adding the test result and the corresponding test data version into the test record page to generate a test report.
Preferably, the updating the old version test report of the interface test by using the test result to generate a new version test report includes:
acquiring position information of an old version test report in the test task information;
acquiring an old version test report according to the position information;
comparing the test result in the old version test report with the test result of the interface test of the current round, and determining a test record page list which needs to be updated in the old version test report;
adding the test result of the interface test of the current round in the old version test report according to the test record page list;
and calculating the test conclusion of the interface code bit according to the increased test result and a preset strategy to generate a new version of test report.
Preferably, obtaining an old version test report according to the location information includes:
judging whether the old version test report is stored in the local equipment according to the position information;
if so, searching an old version test report corresponding to the interface type in the local equipment;
if not, searching an old version test report corresponding to the interface type in a preset server according to the position information.
Preferably, adding the test result of the interface test of the current round in the old version test report according to the test record page list includes:
adding a new test record page in the old test report, and/or adding a new test record column in the test record page of the old test report;
and adding the test result of the interface test of the current round into the corresponding new test record page and/or new test record column.
Preferably, the method further comprises:
and determining the test conclusion of each interface code bit one by one according to the test result of the interface test in the new test report.
Preferably, determining the test conclusion of each interface code bit one by one according to the test result of the interface test in the new test report includes:
obtaining a test result of the interface test of the current round corresponding to the target interface code bit and a test conclusion in an old version test report;
judging whether a test conclusion corresponding to the test result of the interface test of the current round is a specified value or not;
if yes, updating the test conclusion in the old version test report according to the specified value;
if not, generating error reporting information and keeping the test conclusion in the old version test report.
Preferably, updating the test conclusion in the old version test report according to the specified value includes:
when the specified value is any one of OK, NOK and Reserved, updating the test conclusion in the old version test report to the specified value;
and when the specified value is a No Run or a null value, if the test conclusion in the old version test report is the null value, determining that the test conclusion of the interface code bit is the No Run, otherwise, determining that the test conclusion of the interface code bit is the test conclusion in the old version test report.
In a second aspect, the present invention provides an interface test-based test report generation apparatus, including:
the acquisition unit is used for acquiring a test result of the interface test of the current round and test task information, wherein the test task information at least comprises identification information and interface types of whether the current round of the test is the first round;
the judging unit is used for judging whether the interface test of the current round is the first round test according to the identification information obtained by the obtaining unit;
the first generation unit is used for generating a test report according to a test report template corresponding to the interface type and the test result if the judgment unit determines that the interface test in the current round is the first round of test, and the test report records the test conclusion of the interface code bit;
and the second generation unit is used for updating an old version test report of the interface test by using the test result and generating a new version test report if the judgment unit determines that the current round of interface test is not the first round of test, wherein the test conclusion of the interface code bit in the new version test report is obtained by calculating the test result based on a preset strategy.
Preferably, the first generating unit includes:
the acquisition module is used for acquiring a test report template of a corresponding interface according to the interface type;
the determining module is used for determining the test record pages added in the test report template obtained by the obtaining module according to the test result;
and the adding module is used for adding the test result and the corresponding test data version into the test record page determined by the determining module to generate a test report.
Preferably, the second generating unit includes:
the acquisition module is used for acquiring the position information of the old version test report in the test task information;
the reading module is used for acquiring an old version test report according to the position information acquired by the acquisition module;
the determining module is used for comparing the test result of the interface test of the current round with the test result of the old version test report obtained by the reading module, and determining a test record page list which needs to be updated in the old version test report;
the adding module is used for adding the test result of the interface test of the current round in the old version test report according to the test record page list determined by the determining module;
and the generating module is used for calculating the test conclusion of the interface code bit according to the test result added by the adding module and a preset strategy and generating a new version of test report.
Preferably, the reading module is further configured to: judging whether the old version test report is stored in the local equipment according to the position information; if so, searching an old version test report corresponding to the interface type in the local equipment; if not, searching an old version test report corresponding to the interface type in a preset server according to the position information.
Preferably, the adding module is further configured to: adding a new test record page in the old test report, and/or adding a new test record column in the test record page of the old test report; and adding the test result of the interface test of the current round into the corresponding new test record page and/or new test record column.
Preferably, the apparatus further comprises:
and the determining unit is used for determining the test conclusion of each interface code bit one by one according to the test result of the interface test in the new version test report generated by the second generating unit.
Preferably, the determination unit includes:
the acquisition module is used for acquiring the test result of the interface test of the current round corresponding to the target interface code bit and the test conclusion in the old version test report;
the judging module is used for judging whether a test conclusion corresponding to the test result of the current round of interface test is a specified value;
the updating module is used for updating the test conclusion in the old version test report according to the specified value if the judging module determines that the specified value is the specified value;
and the alarm module is used for generating error reporting information and reserving the test conclusion in the old version test report if the judgment module determines that the test result is not the specified value.
Preferably, the update module is further configured to:
when the specified value is any one of OK, NOK and Reserved, updating the test conclusion in the old version test report to the specified value;
and when the specified value is a No Run or a null value, if the test conclusion in the old version test report is the null value, determining that the test conclusion of the interface code bit is the No Run, otherwise, determining that the test conclusion of the interface code bit is the test conclusion in the old version test report.
In another aspect, the present invention further provides a processor, where the processor is configured to execute a program, where the program executes the method for generating a test report based on an interface test according to the first aspect.
In another aspect, the present invention further provides a storage medium, where the storage medium is used to store a computer program, where the computer program controls, when running, a device on which the storage medium is located to execute the method for generating a test report based on an interface test according to the first aspect.
By means of the technical scheme, the method and the device for generating the test report based on the interface test provided by the invention have the advantages that whether the current round of the interface test is the first round of test is identified through obtaining the test task information, the test report can be directly generated for the first round of test, the test conclusion corresponding to each interface code bit is determined according to the test result, and for the non-first round of test, the test result of the current round and the test result in the test report of the old version are summarized to obtain the test report of the new version, and the test conclusion corresponding to each interface code bit is updated in the test report by using the summarized test result. According to the embodiment of the invention, the process of summarizing the interface test results of the testers and the judgment of the final conclusion are delivered to the computer to be automatically executed to the greatest extent, so that the summarizing of the interface test records and the judgment of the final conclusion can be more efficiently and quickly realized, the test labor is liberated, and the working efficiency is improved.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
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 refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart illustrating a test report generation method based on interface testing according to an embodiment of the present invention;
FIG. 2 is a flow chart illustrating another method for generating a test report based on interface testing according to an embodiment of the present invention;
FIG. 3 is a flow chart of another method for generating a test report based on interface testing according to an embodiment of the present invention;
FIG. 4 is a flow chart illustrating another method for generating a test report based on interface testing according to an embodiment of the present invention;
fig. 5 is a flowchart illustrating a step of summarizing test results in the test report generation method based on interface testing according to the embodiment of the present invention;
fig. 6 shows a flow chart of the determination steps of the interface code bit test conclusion in the test report generation method based on the interface test according to the embodiment of the present invention;
fig. 7 is a schematic structural diagram illustrating a test report generation apparatus based on interface testing according to an embodiment of the present invention;
fig. 8 is a schematic structural diagram of another test report generation apparatus based on interface testing according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
The embodiment of the invention provides a test report generation method based on interface test, which specifically executes the steps as shown in figure 1 and comprises the following steps:
101. and obtaining the test result and the test task information of the interface test of the round.
The interface test of the railway system means that in the railway signal system, different subsystems need to exchange data information through corresponding interfaces, and the system interface needs to be tested if the interfaces can effectively and correctly exchange the data information. In this embodiment, different items have different test contents for system interfaces, and the obtained test results are also different, so the test task information in this step refers to the relevant parameter information of the specific test performed on the interface, and mainly includes: the interface types are different, and the interfaces of different types have corresponding test modes and test results; the item identification is used for distinguishing specific items, and the identification is mostly the item name; whether the item is the identification information of the first round or not is marked, namely, whether the interface test of the current round is the first test or not is marked; the data version information indicates which version of software is used for testing the interface test result of the round, and so on, because the interface test of different rounds may have different versions of the applied testing software.
The test result and the test task information in this step are obtained from the preset storage position after the interface test of this round is completed.
102. And judging whether the interface test of the current round is the first round test or not according to the identification information.
The identification information is the identification information of whether the test task information contains the first round or not. Whether the test result of the interface test of the current round needs to be summarized or not can be determined by identifying whether the first round of test is performed, if the first round of test is performed, the summarization is not needed, and the step 103 is executed to generate a test report; if the test is not the first round, the test result of the current round and the previous test result need to be aggregated, and then a test report is generated, that is, step 104 is executed.
103. And generating a test report according to the test report template corresponding to the interface type and the test result.
In this embodiment, corresponding test report templates are set for different interface types, so that the corresponding test report templates can be called according to the interface types included in the test task information, and the test results are generated into test reports according to the format specified by the test report templates.
It should be noted that, in the test report, the recorded test result only represents the data result of the functional test process performed on the interface, and the data result is not equivalent to the evaluation conclusion on the interface function. That is, the test result records the specific data received and sent corresponding to each interface code bit, but the test result does not give a conclusion whether each interface code bit is normal. In the prior art, the conclusion generally needs to be manually determined according to the result of the test data recorded in the test report, but in the embodiment, the test conclusion of each interface code bit is automatically generated according to the test result in the process of generating the test report, and therefore, a corresponding evaluation rule needs to be set in a test report template, and the test conclusion is determined according to the evaluation rule, so that manual processing is replaced, and the test efficiency is improved.
104. And updating the old version test report of the interface test by using the test result to generate a new version test report.
The step is executed when the current round of interface test is determined not to be the first round of test, because the first round of test is not, it can be determined that the corresponding test is generated in the previous interface test, namely the old version test report, and the format of the new version test report to be generated is also determined by obtaining the old version test report, namely the new version test report is obtained by adding the test result of the current round of interface test based on the content of the old version test report, therefore, the test result in the generated new version test report can be regarded as the summary of the test results of the previous round of interface test, and the test conclusion in the new version test report is calculated according to the preset strategy based on the test result of the current round of interface test and the test conclusion in the old version test report, therefore, the preset strategy is also needed to be set for summarizing the test report generated by the test result of the multiple round of interface test, to calculate the final test conclusion for the interface code bits in the new version of the test report.
As can be seen from the above steps 103 and 104, for the test of the same interface in the same project, a corresponding test report is generated from the first round of test, and each time an interface test is performed again, the test result of this time is summarized into the previous test report, and the test conclusion of the interface code bit is calculated to generate the latest test report. And recording the test results of all rounds in the test report, and automatically calculating the test conclusion of each interface code bit after the latest round of interface test.
Based on the implementation manner shown in fig. 1, it can be seen that the test report generation method based on interface testing provided in the embodiment of the present invention identifies whether a current round of interface testing is a first round of testing by obtaining the test task information, and for the first round of testing, the test report can be directly generated, and the test conclusion corresponding to each interface code bit is determined according to the test result, whereas for the non-first round of testing, the test result of the current round and the test result in the test report of the old version are summarized to obtain a test report of a new version, and the test conclusion corresponding to each interface code bit is updated in the test report by using the summarized test result. According to the embodiment of the invention, the process of summarizing the interface test results of the testers and the judgment of the final conclusion are delivered to the computer to be automatically executed to the greatest extent, so that the summarizing of the interface test records and the judgment of the final conclusion can be more efficiently and quickly realized, the test labor is liberated, and the working efficiency is improved.
Further, in a preferred embodiment of the present invention, on the basis of fig. 1, a specific process of generating a test report of a test result including test results corresponding to interface code bits generated by a first test is described in detail with respect to step 103, where the steps are shown in fig. 2, and include:
1031. and acquiring a test report template of the corresponding interface according to the interface type.
The information of the interface type is obtained from the test task information, different interface types correspond to different test report templates, the display format of the test result of the interface is specified in the test report template, and meanwhile, corresponding evaluation rules are set for determining the test conclusion of the interface code bit according to the test result.
1032. And determining the test record pages added in the test report template according to the test result.
Because the test is the first round of test, no other test results exist in the test report template, and therefore, based on the test report template, corresponding test record pages are added for recording the test results. The test record page is divided according to a specific test result, the specific dividing manner is not particularly limited, and the test record page may be divided based on a specific test parameter or divided based on a tested function.
1033. And adding the test result and the corresponding test data version into the test record page to generate a test report.
The added information of the test data version in this step obtains self-test task information for marking version information of the test software used by the test result in this round. The test report of the first round of interface test is stored in the local device or the server, so that the test result can be summarized and counted according to the test data version after the subsequent rounds of interface tests, and therefore, the test data version needs to be added to the generated test report.
Meanwhile, because the test in the current round is the first round, the test conclusion of the interface code bit can be directly determined in the generated test report according to the test result and the corresponding evaluation rule, and the test conclusion is added to the specified position of the test report.
Further, in a preferred embodiment of the present invention, on the basis of fig. 1, a specific process of generating a test report of a test result including test results corresponding to interface code bits, which is generated by a non-first-round test, in step 104 is described in detail, and the steps are as shown in fig. 3, and include:
1041. and acquiring the position information of the old version test report in the test task information.
Because the interface test of the current round is not the first round, the test report generated by the interface test of the previous round can be stored in the designated position, and the position information is carried in the test task information of the interface test of the current round, so that the embodiment can extract the position information of the old version of test report from the test task information.
1042. And acquiring an old version test report according to the position information.
In this embodiment, the locations where the old version of the test report specified by the location information is stored may be classified into two types, one type being in the local device and the other type being the non-local device. Therefore, in this step, it can be determined whether the old version test report is stored in the local device according to the location information and the storage path of the local device. If so, searching an old version test report which corresponds to the interface type and belongs to the same item in the local equipment according to the position information, and summarizing test results of all round interface tests and test conclusions of interface code bits in the old version test report before the round of interface test. If not, the step searches for an old version test report of the corresponding interface type and belonging to the same project in a preset server according to the position information. The preset server is used for storing relevant data of system interface test, and a corresponding preset instruction is set in the preset server and used for searching corresponding system interface test data in the preset server. For example, when the location information determines that the old version test report is stored in the preset server, the old version test report fed back by the preset server may be received by sending a preset query instruction including an interface type and an item identifier to the preset server.
1043. And determining a test record page list needing to be updated in the old version test report according to the test result in the old version test report and the test result of the interface test of the current round.
Wherein the test record page list comprises the test record pages which already exist in the old version test report and the test record pages which need to be newly created in the old version test report.
1044. And adding the test result of the interface test in the current round in the old version of test report according to the test record page list.
Summarizing the test results of the interface test of the current round and the test results of the interface test of the previous round, and according to the determined test record page list, adding a corresponding new test record column in the test record page for the test record page existing in the old version of test report so as to increase the test results of the interface test of the current round; for the newly added test record page in the old version of test report, the test result of the corresponding interface test of the current round can be directly added into the test record page.
1045. And calculating the test conclusion of the interface code bit according to the increased test result and a preset strategy to generate a new version of test report.
Because the old version test report contains the test conclusion of the interface code bit, the step is to judge whether the test conclusion of the interface code bit in the old version test report needs to be updated according to a preset strategy aiming at each interface code bit based on the test result of the interface test in the current round, and record the updated test conclusion in the new version test report.
Further, on the basis of the embodiments of fig. 1 to 3, a specific implementation manner of determining a test conclusion of each interface code bit in a new test report will be described in detail in a preferred embodiment of the present invention, and specific steps of the specific implementation manner are shown in fig. 4, and include:
401. and obtaining the test result of the interface test of the current round corresponding to the target interface code bit and the test conclusion in the old version test report.
The data content obtained in the step can be obtained from the summarized new version test report.
402. And judging whether the test conclusion corresponding to the test result of the interface test in the current round is a specified value.
Specifically, when the interface code bits are judged, the test conclusion of each interface code bit needs to be judged one by one according to the interface code bits, that is, whether the test result corresponding to the interface code bit in the current round of interface test is a specified value or not. Different specified values correspond to different test conclusions. If the test result is the specified value, step 403 is executed, otherwise, step 404 is executed.
403. And updating the test conclusion in the old version test report according to the specified value.
In the embodiment, the specified values include OK, NOK, Reserved, No Run and null values, which respectively represent test pass, test fail, Reserved, untested and No-data test states of the interface code bits.
In this step, the final test conclusion determined for different specified values is different:
when the specified value is any one of OK, NOK and Reserved, updating the test conclusion in the old version test report to the specified value;
when the specified value is No Run or null value, the further judgment needs to be made by combining the test conclusion in the old version test report: and if the test conclusion in the old version test report is a null value, determining that the test conclusion of the interface code bit is No Run, and otherwise, determining that the test conclusion of the interface code bit is the test conclusion in the old version test report.
404. And generating error reporting information and reserving the test conclusion in the old version test report.
In this step, when the test result corresponding to the test result is not the specified value, it indicates that which test conclusion the interface code bit belongs to cannot be determined by the test result. In the actual testing process, the testing result may be a fault, so for the testing result, biochemical error information is needed, and the testing result is recorded for the analysis of the testing personnel. And meanwhile, for the test conclusion of the interface code bit, the test conclusion in the old version test report is kept.
In this embodiment, the step 402-404 may be regarded as a loop step executed for the interface code bits, and the test interfaces of each interface code bit are determined one by one according to the order of the interface code bits until the loop is skipped after the test conclusion of all the interface code bits is determined.
With reference to the interface test-based test report generation method shown in the embodiments of fig. 1 to 3, a test report generation process of an interface test of an automatic train monitoring subsystem and an interlocking subsystem of a certain project and a test report generation process in different application scenarios will be specifically described below with reference to a flowchart of test result summarizing steps shown in fig. 5. The specific steps are shown in fig. 5, and include:
scene 1: the case of the first round of testing corresponds to the embodiment shown in fig. 2 described above.
In step 101, it is determined that the interface test task executed in this round is the first round test condition according to the parameter information of the interface test in this round, and the process goes to step 102.
In step 102, according to the position information in the parameter information, a test report template corresponding to the interface test of the automatic train monitoring subsystem and the interlocking subsystem is automatically obtained in the specified path.
In step 103, the test results of the interface test of the current round are automatically analyzed, record pages with test result records existing on the interface code bits are determined, and corresponding record pages are newly built in the test report template.
In step 104, the test results of the interface test of this round are filled into the test result columns of this round in the corresponding record pages in the test report template according to the data content recorded by the test results of the interface test.
In step 111, according to the test result determination algorithm logic, the final conclusion determination of the record page in the test report template is executed and the final conclusion is updated, so as to obtain the test conclusion of each interface code bit.
Scene 2: the case of a non-first round test, local old version test report, corresponds to the embodiment shown in fig. 3 described above.
In step 101, it is determined that the interface test task executed in this round is a non-first-round test condition according to the parameter information of the interface test in this round, and the process goes to step 105.
In step 105, it is determined from the location information in the parameter information that the old version test report corresponding to the interface test task executed in the current round is stored in the local device, and the process goes to step 107.
In step 107, the test result records of the interface test of the current round and the content of the old version test report in the local device are read.
In step 108, the test result records of the current round are analyzed, and a record page with the test result records is obtained. In this step, the test results of the interface test of the current round need to be preprocessed, and the record pages with valid records are screened and obtained from the whole test record, that is, the test results in each record page are checked in advance, the record pages with the results are obtained, and the record pages with empty test results in the current round are ignored.
In step 109, according to the record page condition with the result record, the corresponding record page in the old version test report is inserted into the record column of the latest version, or when there is no corresponding record page in the old version test report, the corresponding record page is newly created.
In step 110, the test result of the current round is filled into the record column corresponding to the test result of the current round in the corresponding record page in the test report of the old version according to the content of the record of the test result of the current round of interface test.
In step 111, according to the test result determination algorithm logic, the final conclusion determination of the record page in the test report template is executed and the final conclusion is updated, so as to obtain the test conclusion of each interface code bit.
Scene 3: the case of a non-first round test, non-local old version test report, corresponds to the embodiment shown in fig. 3 described above.
In step 101, it is determined that the interface test task executed in this round is a non-first-round test condition according to the parameter information of the interface test in this round, and the process goes to step 105.
In step 105, it is determined that the old version test report corresponding to the interface test task executed in this round is not stored in the local device according to the location information in the parameter information, and the process goes to step 106.
In step 106, the old version test report corresponding to the item and the interface type is downloaded from the preset server to a specific path of the local device.
In step 107, the test result records of the interface test of the current round and the content of the old version test report in the local device are read.
In step 108, the test result records of the current round are analyzed, and a record page with the test result records is obtained. In this step, the test results of the interface test of the current round need to be preprocessed, and the record pages with valid records are screened and obtained from the whole test record, that is, the test results in each record page are checked in advance, the record pages with the results are obtained, and the record pages with empty test results in the current round are ignored.
In step 109, according to the record page condition with the result record, the corresponding record page in the old version test report is inserted into the record column of the latest version, or when there is no corresponding record page in the old version test report, the corresponding record page is newly created.
In step 110, the test result of the current round is filled into the record column corresponding to the test result of the current round in the corresponding record page in the test report of the old version according to the content of the record of the test result of the current round of interface test.
In step 111, according to the test result determination algorithm logic, the final conclusion determination of the record page in the test report template is executed and the final conclusion is updated, so as to obtain the test conclusion of each interface code bit.
For the method for generating a test report based on interface testing shown in the embodiment of fig. 4, the following specifically describes, with reference to the flowchart of the step of determining the test conclusion of the interface code bit shown in fig. 6, a determination process of a test conclusion in a test report of an interface test of an automatic train monitoring subsystem and an interlocking subsystem of a certain project, and a test report generation process in different application scenarios. The specific steps are shown in fig. 6, and include:
scene 4: the test results of the current round of 4 continuous code bits are OK, NOK, Reserved and AAA respectively, and the final conclusions of the corresponding code bits in the test report of the old version are NOK, OK and OK respectively:
in step 201, the test conclusion of the current round and the test conclusion in the old version test report are obtained.
In step 202, the current code bit is obtained with OK and NOK in the old version.
In step 203, it is determined that the test result of the current round is OK, and the process proceeds to step 204.
In step 204, the final test result of the current code bit is updated to OK, and the process continues to step 214.
In step 214, the determination that all code bits are currently not completed is performed, and the process jumps to step 215.
In step 215, loop to the next code bit and continue to step 202.
In step 202, the current code bit is obtained with the test result of NOK in the current round and the test result of the old version is OK.
In step 203, it is determined that the test result of the present round is not OK, and the process proceeds to step 205.
In step 205, it is determined that the test result of the current round is NOK, and the process proceeds to step 206.
In step 206, the program updates the final test conclusion for the current code bit to NOK and proceeds to step 214.
In step 214, the determination that all code bits are currently not completed is performed, and the process jumps to step 215.
In step 215, loop to the next code bit and continue to step 202.
In step 202, the program obtains that the current code bit is Reserved in the current round of test and that the old version is OK.
In step 203, it is determined that the test result of the present round is not OK, and the process proceeds to step 205.
In step 205, it is determined that the test result of the present round is not NOK, and the process proceeds to step 207.
In step 207, the current round test result is determined to be Reserved, and the process jumps to step 208.
In step 208, the final test conclusion of the current code bit is updated to Reserved, and the process continues to step 214.
In step 214, the determination that all code bits are currently not completed is performed, and the process jumps to step 215.
In step 215, loop to the next code bit and continue to step 202.
In step 202, the current round of test conclusion of the current code bit is AAA and the test conclusion of the old version is OK.
In step 203, it is determined that the test result of the current round is not OK, and the process proceeds to step 205.
In step 205, it is determined that the result of the test of this round is not NOK, and the process proceeds to step 207.
In step 207, it is determined that the current round of test results are not Reserved, and the process jumps to step 209.
In step 209, it is determined that the test result of this round is not No Run or null, and the process jumps to step 213.
In step 213, reporting that the test conclusion record of the current code bit in the current round is abnormal, and continuing to execute step 214 if the final test conclusion of the current code bit is not updated.
In step 214, it is determined that the execution of determination of all code bits is currently completed, and the determination process of the test conclusion of the interface code bits is ended.
Scene 5: the test results of the current round of 2 continuous code bits are No Run and null respectively, and the final conclusions of the corresponding code bits in the test report of the old version are OK and null respectively:
in step 201, the test conclusion of the current round and the test conclusion in the old version test report are obtained.
In step 202, the current code bit is obtained with test result No Run and the old version is obtained with test result OK.
In step 203, it is determined that the test tie round is not OK, and the process proceeds to step 205.
In step 205, it is determined that the test node turn of the current round is not NOK, and the process proceeds to step 207.
In step 207, it is determined that the current round of test results are not Reserved, and the process jumps to step 209.
In step 209, the test node turns to No Run or null in the current round, and the process skips to step 210.
In step 210, it is determined that the test result of the old version test report is not null, and the process jumps to step 212.
In step 212, the test conclusion for the current code bit is not updated, and execution continues at step 214.
In step 214, the determination that all code bits are currently not completed is performed, and the process jumps to step 215.
In step 215, loop to the next code bit and continue to step 202.
In step 202, the current code bit is obtained with a null test result in the current round and a null test result in the old version.
In step 203, it is determined that the test tie round is not OK, and the process proceeds to step 205.
In step 205, it is determined that the test node turn of the current round is not NOK, and the process proceeds to step 207.
In step 207, it is determined that the test node round of this round is not Reserved, and the process jumps to step 209.
In step 209, the test node turns to No Run or null in the current round, and the process skips to step 210.
In step 210, the program determines that the test result of the old version test report is null, and jumps to step 211.
In step 211, the final test conclusion of the current code bit is updated to No Run, and the process continues to step 214.
In step 214, it is determined that the execution of determination of all code bits is currently completed, and the determination process of the test conclusion of the interface code bits is ended.
Further, as an implementation of the method embodiments shown in fig. 1 to 4, an embodiment of the present invention provides a test report generation device based on interface tests, where the device is configured to summarize test results of multiple rounds of interface tests, show a final test conclusion of an interface in a test report, and improve test efficiency of the interface tests. The embodiment of the apparatus corresponds to the foregoing method embodiment, and details in the foregoing method embodiment are not repeated in this embodiment for convenience of reading, but it should be clear that the apparatus in this embodiment can correspondingly implement all the contents in the foregoing method embodiment. As shown in fig. 7 in detail, the apparatus includes:
an obtaining unit 51, configured to obtain a test result of a current round of interface test and test task information, where the test task information at least includes identification information of whether the current round of interface test is a first round and an interface type;
a determining unit 52, configured to determine whether the current round of interface test is the first round of test according to the identification information obtained by the obtaining unit 51;
the first generating unit 53 is configured to generate a test report according to the test report template corresponding to the interface type and the test result if the determining unit 52 determines that the interface test in the current round is the first round, where test results of interface code bits are recorded in the test report;
a second generating unit 54, configured to update an old version test report of the interface test with the test result and generate a new version test report if the determining unit 52 determines that the current round of interface test is not the first round of test, where test results of interface code bits in the new version test report are obtained by calculating the test result based on a preset policy.
Further, as shown in fig. 8, the first generating unit 53 includes:
an obtaining module 531, configured to obtain a test report template of a corresponding interface according to the interface type;
a determining module 532, configured to determine, according to the test result, a test record page added to the test report template obtained by the obtaining module 531;
the adding module 533 is configured to add the test result and the corresponding test data version to the test record page determined by the determining module 532, so as to generate a test report.
Further, as shown in fig. 8, the second generating unit 54 includes:
an obtaining module 541, configured to obtain location information of an old version test report in the test task information;
a reading module 542, configured to obtain an old version test report according to the position information obtained by the obtaining module 541;
a determining module 543, configured to compare the test result in the old test report obtained by the reading module 542 with the test result of the interface test in the current round, and determine a test record page list that needs to be updated in the old test report;
an adding module 544, configured to add, according to the test record page list determined by the determining module 543, the test result of the current round of interface test in the old version test report;
the generating module 545 is configured to calculate a test conclusion of the interface code bits according to a preset policy according to the test result added by the adding module 544, and generate a new version of test report.
Further, the reading module 542 is further configured to: judging whether the old version test report is stored in the local equipment according to the position information; if so, searching an old version test report corresponding to the interface type in the local equipment; if not, searching an old version test report corresponding to the interface type in a preset server according to the position information.
Further, the adding module 544 is further configured to: adding a new test record page in the old test report, and/or adding a new test record column in the test record page of the old test report; and adding the test result of the interface test of the current round into the corresponding new test record page and/or new test record column.
Further, as shown in fig. 8, the apparatus further includes:
the determining unit 55 is configured to determine the test conclusion of each interface code bit one by one according to the test result of the interface test in the new version test report generated by the second generating unit 54.
Further, as shown in fig. 8, the determining unit 55 includes:
the obtaining module 551 is configured to obtain a test result of the interface test of the current round corresponding to the target interface code bit and a test conclusion in the old version test report;
a determining module 552, configured to determine whether a test conclusion corresponding to the test result of the current round of interface test obtained by the obtaining module 551 is a specified value;
an updating module 553, configured to update the test conclusion in the old version test report according to the specified value if the determining module 552 determines that the specified value is the specified value;
an alarm module 554, configured to generate an error report message and retain the test conclusion in the old version of test report if the determination module 552 determines that the test result is not the specified value.
Further, the update module 553 is further configured to:
when the specified value is any one of OK, NOK and Reserved, updating the test conclusion in the old version test report to the specified value;
and when the specified value is a No Run or a null value, if the test conclusion in the old version test report is the null value, determining that the test conclusion of the interface code bit is the No Run, otherwise, determining that the test conclusion of the interface code bit is the test conclusion in the old version test report.
Further, an embodiment of the present invention further provides a processor, where the processor is configured to execute a program, where the program executes the method for generating a test report based on an interface test described in fig. 1 to 4 when running.
Further, an embodiment of the present invention further provides a storage medium, where the storage medium is used to store a computer program, where the computer program controls, when running, a device in which the storage medium is located to execute the test report generation method based on the interface test described in fig. 1 to 4.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
It will be appreciated that the relevant features of the method and apparatus described above are referred to one another. In addition, "first", "second", and the like in the above embodiments are for distinguishing the embodiments, and do not represent merits of the embodiments.
It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The algorithms and displays presented herein are not inherently related to any particular computer, virtual machine, or other apparatus. Various general purpose systems may also be used with the teachings herein. The required structure for constructing such a system will be apparent from the description above. Moreover, the present invention is not directed to any particular programming language. It is appreciated that a variety of programming languages may be used to implement the teachings of the present invention as described herein, and any descriptions of specific languages are provided above to disclose the best mode of the invention.
In addition, the memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (11)
1. A method for generating a test report based on an interface test, the method comprising:
acquiring a test result and test task information of the interface test of the current round, wherein the test task information at least comprises identification information and interface types of whether the interface test of the current round is the first round;
judging whether the interface test of the current round is the first round test or not according to the identification information;
if the interface test of the current round is the first round, generating a test report according to a test report template corresponding to the interface type and the test result, wherein the test report records a test conclusion of interface code bits;
and if the interface test of the current round is not the first round, updating the old version test report of the interface test by using the test result to generate a new version test report, wherein the test conclusion of the interface code bit in the new version test report is obtained by calculating the test result based on a preset strategy.
2. The method of claim 1, wherein generating a test report according to the test report template corresponding to the interface type and the test result comprises:
acquiring a test report template of a corresponding interface according to the interface type;
determining a test record page added in the test report template according to the test result;
and adding the test result and the corresponding test data version into the test record page to generate a test report.
3. The method of claim 1, wherein updating the old version test report of the interface test with the test result to generate a new version test report comprises:
acquiring position information of an old version test report in the test task information;
acquiring an old version test report according to the position information;
comparing the test result in the old version test report with the test result of the interface test of the current round, and determining a test record page list which needs to be updated in the old version test report;
adding the test result of the interface test of the current round in the old version test report according to the test record page list;
and calculating the test conclusion of the interface code bit according to the increased test result and a preset strategy to generate a new version of test report.
4. The method of claim 3, wherein obtaining a legacy test report based on the location information comprises:
judging whether the old version test report is stored in the local equipment according to the position information;
if so, searching an old version test report corresponding to the interface type in the local equipment;
if not, searching an old version test report corresponding to the interface type in a preset server according to the position information.
5. The method of claim 3, wherein adding the test results of the current round of interface testing to the old version of test report according to the list of test log pages comprises:
adding a new test record page in the old test report, and/or adding a new test record column in the test record page of the old test report;
and adding the test result of the interface test of the current round into the corresponding new test record page and/or new test record column.
6. The method according to any one of claims 1-5, further comprising:
and determining the test conclusion of each interface code bit one by one according to the test result of the interface test in the new test report.
7. The method of claim 6, wherein determining the test conclusion of each interface code bit one by one according to the test result of the interface test in the new test report comprises:
obtaining a test result of the interface test of the current round corresponding to the target interface code bit and a test conclusion in an old version test report;
judging whether a test conclusion corresponding to the test result of the interface test of the current round is a specified value or not;
if yes, updating the test conclusion in the old version test report according to the specified value;
if not, generating error reporting information and keeping the test conclusion in the old version test report.
8. The method of claim 7, wherein updating the test conclusion in the legacy test report based on the specified value comprises:
when the specified value is any one of OK, NOK and Reserved, updating the test conclusion in the old version test report to the specified value;
and when the specified value is a No Run or a null value, if the test conclusion in the old version test report is the null value, determining that the test conclusion of the interface code bit is the No Run, otherwise, determining that the test conclusion of the interface code bit is the test conclusion in the old version test report.
9. An interface test based test report generation apparatus, the apparatus comprising:
the acquisition unit is used for acquiring a test result of the interface test of the current round and test task information, wherein the test task information at least comprises identification information and interface types of whether the current round of the test is the first round;
the judging unit is used for judging whether the interface test of the current round is the first round test according to the identification information obtained by the obtaining unit;
the first generation unit is used for generating a test report according to a test report template corresponding to the interface type and the test result if the judgment unit determines that the interface test in the current round is the first round of test, and the test report records the test conclusion of the interface code bit;
and the second generation unit is used for updating an old version test report of the interface test by using the test result and generating a new version test report if the judgment unit determines that the current round of interface test is not the first round of test, wherein the test conclusion of the interface code bit in the new version test report is obtained by calculating the test result based on a preset strategy.
10. A processor, configured to run a program, wherein the program runs to perform the method for generating a test report based on an interface test according to any one of claims 1 to 8.
11. A storage medium for storing a computer program, wherein the computer program controls a device in which the storage medium is located to execute the method for generating a test report based on an interface test according to any one of claims 1 to 8 when the computer program runs.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011468385.6A CN112224246B (en) | 2020-12-15 | 2020-12-15 | Test report generation method and device based on interface test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011468385.6A CN112224246B (en) | 2020-12-15 | 2020-12-15 | Test report generation method and device based on interface test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112224246A true CN112224246A (en) | 2021-01-15 |
| CN112224246B CN112224246B (en) | 2021-03-26 |
Family
ID=74124872
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011468385.6A Active CN112224246B (en) | 2020-12-15 | 2020-12-15 | Test report generation method and device based on interface test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112224246B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113110998A (en) * | 2021-04-23 | 2021-07-13 | 中国邮政储蓄银行股份有限公司 | Interface test report generation method and generation device |
| CN115123339A (en) * | 2022-07-15 | 2022-09-30 | 中国铁道科学研究院集团有限公司 | Coding unit for station ground control system |
| CN115195814A (en) * | 2022-07-15 | 2022-10-18 | 中国铁道科学研究院集团有限公司 | Station ground control system and coding unit control method |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107423208A (en) * | 2017-03-03 | 2017-12-01 | 上海斐讯数据通信技术有限公司 | A kind of Android compatibility test methods, apparatus and system |
| CN109558330A (en) * | 2018-12-13 | 2019-04-02 | 郑州云海信息技术有限公司 | A kind of automated testing method and device |
| CN110765018A (en) * | 2019-10-25 | 2020-02-07 | 上海中通吉网络技术有限公司 | Automatic interface testing method and equipment |
| JP2020087071A (en) * | 2018-11-28 | 2020-06-04 | 株式会社日立製作所 | Form scale calculation device |
| CN112035308A (en) * | 2020-11-03 | 2020-12-04 | 卡斯柯信号(北京)有限公司 | Method and device for generating system interface test table |
-
2020
- 2020-12-15 CN CN202011468385.6A patent/CN112224246B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107423208A (en) * | 2017-03-03 | 2017-12-01 | 上海斐讯数据通信技术有限公司 | A kind of Android compatibility test methods, apparatus and system |
| JP2020087071A (en) * | 2018-11-28 | 2020-06-04 | 株式会社日立製作所 | Form scale calculation device |
| CN109558330A (en) * | 2018-12-13 | 2019-04-02 | 郑州云海信息技术有限公司 | A kind of automated testing method and device |
| CN110765018A (en) * | 2019-10-25 | 2020-02-07 | 上海中通吉网络技术有限公司 | Automatic interface testing method and equipment |
| CN112035308A (en) * | 2020-11-03 | 2020-12-04 | 卡斯柯信号(北京)有限公司 | Method and device for generating system interface test table |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113110998A (en) * | 2021-04-23 | 2021-07-13 | 中国邮政储蓄银行股份有限公司 | Interface test report generation method and generation device |
| CN115123339A (en) * | 2022-07-15 | 2022-09-30 | 中国铁道科学研究院集团有限公司 | Coding unit for station ground control system |
| CN115195814A (en) * | 2022-07-15 | 2022-10-18 | 中国铁道科学研究院集团有限公司 | Station ground control system and coding unit control method |
| CN115123339B (en) * | 2022-07-15 | 2024-01-12 | 中国铁道科学研究院集团有限公司 | Coding unit for station ground control system |
| CN115195814B (en) * | 2022-07-15 | 2024-01-12 | 中国铁道科学研究院集团有限公司 | Station ground control system and code unit control method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112224246B (en) | 2021-03-26 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112224246B (en) | Test report generation method and device based on interface test | |
| CN111209206B (en) | Automatic test method and system for software products | |
| CN111241073A (en) | Data quality inspection method and device | |
| CN111026663B (en) | Software defect detection method, device, computer equipment and storage medium | |
| CN111026080A (en) | Hardware-in-loop test method and device for controller | |
| CN115118627B (en) | Temporary speed limiting server testing method and device | |
| CN114443441B (en) | Storage system management method, device and equipment and readable storage medium | |
| CN117391306A (en) | Homeland space planning result examination method, device, equipment and storage medium | |
| CN114070737B (en) | Method and device for checking configuration data of equipment, storage medium and electronic equipment | |
| CN111427736B (en) | Log monitoring method, device, equipment and computer readable storage medium | |
| CN110674038A (en) | Method and device for classifying error information in software test | |
| CN115987821A (en) | Gateway routing test method and device | |
| CN112667523B (en) | Automatic test case filling method and device | |
| CN112035308A (en) | Method and device for generating system interface test table | |
| CN115186001A (en) | Patch processing method and device | |
| CN114500249A (en) | Root cause positioning method and device | |
| CN114416545A (en) | Method and device for determining test code coverage rate and electronic equipment | |
| CN111078239B (en) | Map data updating method and device | |
| CN107797915B (en) | Fault repairing method, device and system | |
| CN110717131A (en) | Page revising monitoring method and related system | |
| CN115134819B (en) | Test method and device for train control wireless block system | |
| CN105701002A (en) | Test based execution path recording method and apparatus | |
| CN113071541B (en) | Method and device for generating trackside configuration file | |
| CN116882968B (en) | Design and implementation method for fault defect overall process treatment | |
| CN115144678B (en) | Visual test condition configuration method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |