CN105512026A - Automatic batch testing method - Google Patents
Automatic batch testing method Download PDFInfo
- Publication number
- CN105512026A CN105512026A CN201510834003.XA CN201510834003A CN105512026A CN 105512026 A CN105512026 A CN 105512026A CN 201510834003 A CN201510834003 A CN 201510834003A CN 105512026 A CN105512026 A CN 105512026A
- Authority
- CN
- China
- Prior art keywords
- test
- client
- control end
- testing tool
- testing
- 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.)
- Pending
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
-
- 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
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Abstract
The invention discloses an automatic batch testing method, pertaining to the technical field of automatic testing. The method comprises following steps of: step S1, sequentially sending testing tools corresponding down to all clients by a control end and performing installation operation of operation systems by dependency correspondence; step S2, applying installed testing tools by each client to test compilation performance of the systems and monitoring in order to obtain testing data generated during testing processes; step S3, reporting all the testing data to the control end by each client in order to finish testing compilation performance of the systems and then quitting. The above technical scheme adopted by the automatic batch testing method has following beneficial effects: automatic batch testing problems of operation systems in different versions and types are solved; manual cost is reduced; and testing efficiency is improved.
Description
Technical field
The present invention relates to automatic test technology field, particularly relate to a kind of batch automatic test approach.
Background technology
In prior art, because various object is such as the support of different computer organization, or the demand of corresponding different application, or many-sided reason such as the demand for localization of different regions or language, there will be the operating system of all kinds of version, and dissimilar operating system.
Then in prior art, in the process of the operating system of dissimilar different editions being tested automatically to (especially the automatic test of System build aspect of performance), owing to not considering above-mentioned multiple test scene, therefore on each system under test (SUT), manually carry out testing tool installation, operation is usually needed, and the step such as the collection of test data, need the artificial operation performing a large amount of repetition, cause the waste of human resources and time resource.And the installation environment of testing tool in the operating system of dissimilar different editions also can be different, do not exist in prior art and can carry out testing tool installation and carry out the implementation method of test data collection by batch in different operating system.
Summary of the invention
According to problems of the prior art, now provide a kind of technical scheme of batch automatic test approach, the problem that the batch being intended to carry out System build performance for the operating system that different editions is dissimilar in solution prior art is tested automatically.
Technique scheme specifically comprises:
A kind of batch automatic test approach, wherein, comprise multiple client and control end, described control end connects each described client respectively, and for controlling the automatic testing process of each described client, each described client is normally run respectively under different operating system, also comprises:
Step S1, the testing tool of each for correspondence described client is issued to each described client and carries out relying on the installation operation of corresponding described operating system by described control end successively;
Step S2, each described client applies the test that mounted described testing tool carries out System build performance respectively, and monitoring obtains the test data produced in test process;
Step S3, described test data is reported to described control end by each described client respectively, to complete the test to described System build performance, with backed off after random.
Preferably, this batch automatic test approach, wherein, before performing described step S1, each described client is set up SSH mutual trust with described control end respectively and is connected.
Preferably, this batch automatic test approach, wherein, before performing described step S1, installs the described operating system of the correspondence needing test in each described client.
Preferably, this batch automatic test approach, wherein, described step S1 specifically comprises;
Step S11, described control end issues the dependence environment installation kit for arranging the test environment being associated with corresponding described operating system respectively to each described client;
Step S12, the described dependence environment installation kit that described client Auto-mounting receives, to arrange the test environment being associated with corresponding described operating system;
Step S13, described control end issues corresponding described testing tool respectively to each described client;
Step S14, the described testing tool that described client Auto-mounting receives, with step S2 described in rear steering.
Preferably, this batch automatic test approach, wherein, before the described step S1 of execution, in described control end, pre-set the address list comprising the IP address being associated with each described client, all described IP address in described address list is according to the order arrangement preset;
Then in described step S1, described testing tool, according to the described default order of the described IP address of preserving in described address list, is issued in each described client by described control end successively.
Preferably, this batch automatic test approach, wherein, pre-sets the test parameter being associated with each described client in described control end;
In described step S1, described control end, while issuing described testing tool, issues corresponding described test parameter respectively to each described client;
Then in described step S2, each described client applies corresponding described testing tool respectively, and the described test parameter according to correspondence carries out the test of System build performance.
Preferably, this batch automatic test approach, wherein, is all associated with in a test script corresponding to the described testing tool of each described client and described test parameter;
Then in described step S1, described control end starts the described test script being associated with each described client successively, respectively described testing tool and described test parameter are sent to each described client.
Preferably, this batch automatic test approach, wherein, described client is normally run on the (SuSE) Linux OS of different editions.
The beneficial effect of technique scheme is: provide a kind of batch automatic test approach, the problem that the batch that cannot carry out System build performance for the operating system that different editions is dissimilar in prior art is tested automatically can be solved, reduce cost of labor, promote testing efficiency.
Accompanying drawing explanation
Fig. 1 is in preferred embodiment of the present invention, a kind of overall procedure schematic diagram of batch automatic test approach;
Fig. 2 is in preferred embodiment of the present invention, and on the basis of Fig. 1, control end issues the schematic flow sheet of testing tool;
Fig. 3 is in preferred embodiment of the present invention, and above-mentioned batch automatic test approach realizes the general structure schematic diagram of the test macro relied on.
Embodiment
Below in conjunction with the accompanying drawing in the embodiment of the present invention, be clearly and completely described the technical scheme in the embodiment of the present invention, obviously, described embodiment is only the present invention's part embodiment, instead of whole embodiments.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art obtain under the prerequisite of not making creative work, all belongs to the scope of protection of the invention.
It should be noted that, when not conflicting, the embodiment in the present invention and the feature in embodiment can combine mutually.
Below in conjunction with the drawings and specific embodiments, the invention will be further described, but not as limiting to the invention.
In preferred embodiment of the present invention, based on the above-mentioned problems in the prior art, a kind of batch automatic test approach is now provided, the method be applicable to dissimilar and or the System build performance of operating system of different editions carry out batch and automatically test, therefore, the method depends on test macro as shown in Figure 3.This test macro comprises multiple customer end A and control end B, and control end B connects each customer end A respectively, and for controlling the automatic testing process of each customer end A, each customer end A is normally run respectively under different operating system.
In preferred embodiment of the present invention, arranging of above-mentioned client can be carried out according to the test case of reality, such as:
Need test S kind operating system, and in often kind of operating system, need the compilation performance testing C kind compiler, then (S*C) individual client can be set, and 1 control end is set.
As: need test 4 kinds of operating systems, all need the compilation performance of test a kind of compiler in often kind of operating system, then the quantity of above-mentioned client is 4*1=4, and arranges 1 control end, and the hardware device therefore in test macro is specially 5.
Again such as: need test 3 kinds of operating systems, in often kind of operating system, all need the compilation performance of test 2 kinds of compilers, then the quantity of above-mentioned client is 3*2=6, and arranges 1 control end, and the hardware device therefore in test macro is specially 7.
In preferred embodiment of the present invention, the hardware configuration of above-mentioned hardware device (comprising client and control end) should be consistent, and affects final test data to avoid unstable test environment.
Then in preferred embodiment of the present invention, based on building of above-mentioned test macro, the concrete steps of above-mentioned batch automatic test approach as shown in Figure 1, comprising:
Step S1, the testing tool of each for correspondence client is issued to each client and carries out relying on the installation operation of corresponding operating system by control end successively;
Step S2, each client applies the test that mounted testing tool carries out System build performance respectively, and monitoring obtains the test data produced in test process;
Step S3, test data is reported to control end by each client respectively, to complete the test to System build performance, with backed off after random.
In a specific embodiment, control end is first according to the operating system of each client, the testing tool of correspondence is issued to different clients successively, and carries out installation operation (testing tool can describe in detail hereinafter) relying on operating system in this client.
Subsequently, in this embodiment, each client applies above-mentioned mounted testing tool respectively, tests, monitor and obtain corresponding test data the compilation performance (i.e. System build performance) that it runs compilers different in the operating system relied on.The test that different compiler for different operating system carries out compilation performance can set in advance, and each client only needs to run corresponding testing tool can realize automatic test.
Finally, each client will be monitored in test process and the test data obtained, and subsequently test data is sent to control end and gathers, thus completes the process of the automatic test of this batch.
In preferred embodiment of the present invention, before performing above-mentioned steps S1, each client is set up SSH (SecureShell, safety shell protocol) mutual trust respectively and is connected with control end.Particularly, each client installs the different operating system needing to carry out testing first respectively, sets up SSH mutual trust respectively subsequently and is connected, to prepare automatically to test according to SSH agreement with above-mentioned control end.
In preferred embodiment of the present invention, as shown in Figure 2, above-mentioned steps S1 specifically comprises;
Step S11, control end issues the dependence environment installation kit for arranging the test environment being associated with corresponding operating system respectively to each client;
In prior art, for the operating system run under the operating system of dissimilar and/or different editions, the installation it being carried out to unified testing tool is obvious and unrealistic.Tester needs to coordinate operating system that is dissimilar and/or different editions respectively each client to be depended on to the installation operation of the testing tool of this operating system, then this process will be very complicated, and occupy a large amount of human resources and time resource.
Therefore, in preferred embodiment of the present invention, in above-mentioned steps S11, control end can be before testing begins, first issue should the type of operating system of client and/or the dependence environment installation kit of version respectively to each client, the testing tool installation environment to the operating system should installed in client is set for different clients.
Particularly, one driving file can be set at control end, the version information of the different operating system of Auto-matching can be realized in the setup function in this driving file and select corresponding bag way to manage, and carry out the series installation problems such as the installation of dependence bag.
Step S12, the dependence environment installation kit that client Auto-mounting receives, to arrange the test environment being associated with corresponding operating system;
Step S13, control end issues corresponding testing tool respectively to each client;
The compilation performance testing tool of a kind of PTS of being called as can be selected as the testing tool used in technical solution of the present invention in a preferred embodiment of the present invention, and adopt automated test frame (Autotest) to realize the main body frame of control end.
Therefore, in this embodiment, above-mentioned PTS testing tool can comprise basic test assembly and protos test suite PROTOS group.
Then in above-mentioned steps S13, consider that the distribution efficiency of the whole testing tool of PTS is lower, the defeated mode of control end inborn ability supplementary biography issues testing tool to client, namely after control end starts test, first respectively basic test assembly be issued to different clients and install, and after client terminal start-up test, more corresponding protos test suite PROTOS group is issued to different clients installs.
In preferred embodiment of the present invention, the distribution of above-mentioned basic test assembly mainly through the Autoserv process in Autotest framework, according to the IP address transfer of the operating system of the destination client of specifying to the destination client of specifying.And the distribution of protos test suite PROTOS group downloads to client mainly through wget from control end, be specially and build a FTP (FileTransferProtocol at control end, file transfer protocol (FTP)) server, and the protos test suite PROTOS group of having debugged is put in the download directory of correspondence, client is downloaded protos test suite PROTOS group according to these download directory set and installs subsequently.
Step S14, the testing tool that client Auto-mounting receives, with rear steering step S2.
In preferred embodiment of the present invention, after installing testing tool, the startup of test can be realized by the run_once function in Autotest framework.First this function realizes the registration of PTS testing tool, and it is mutual by what use shell and pexpect storehouse to realize in test process, then perform corresponding test command, the parameter of test command obtains from the control file (control documents) Autotest framework.In above-mentioned test process test result monitoring and collect then realized by postprocess function.The test result file that this function realizes PTS testing tool generates copies in specific result list, finally completes test result by Autotest framework and is back to control end.Above-mentioned control file is the configuration file of client terminal start-up test, realizes the control of test parameter and test execution number of times simultaneously.Control file realizes the transmission of calling of Test driver file and test parameter by the run_test method in Autotest framework.
In preferred embodiment of the present invention, before execution above-mentioned steps S1, in control end, first pre-set the address list comprising the IP address being associated with each client, all IP addresses in address list are according to the order arrangement preset;
Particularly, for the static ip address that each client sets, all these IP addresses are also kept in above-mentioned control end according in sequence integration to address list preset in advance;
Then in step S1, testing tool, according to the order preset of the IP address of preserving in address list, is issued in each client by control end successively.
In preferred embodiment of the present invention, in control end, pre-set the test parameter being associated with each client;
In step S1, control end, while issuing testing tool, issues corresponding test parameter respectively to each client;
Then in step S2, each client carries out the test of System build performance respectively according to the test parameter of correspondence.
In preferred embodiment of the present invention, be all associated with in a test script corresponding to the testing tool of each client and test parameter;
Then in step S1, control end starts the test script being associated with each client successively, respectively testing tool and test parameter are sent to each client.
Particularly, in preferred embodiment of the present invention, before performing the testing, each client needs to report its IP address to control end in advance, and all IP addresses be reported are incorporated in an address list (IPlist).Then carry out test starting function at control end just to be performed by following two files: iplist and above-mentioned test script (being named as compiler-test.sh in preferred embodiment of the present invention).The function of compiler-test.sh script is the IP address of reading each client in iplist successively, and starts each client successively according to IP address and test.After Autotest framework receives the test request being associated with and starting test, control end can issue PTS testing tool (comprising basic test assembly and protos test suite PROTOS group) to each client successively, client Auto-mounting relies on environment installation kit, and Auto-mounting PTS testing tool, the automatic test parameter according to setting in advance carries out the test of System build performance subsequently, and from trend control end passback test data.
In preferred embodiment of the present invention, above-mentioned each client is normally run on the (SuSE) Linux OS of different editions, namely it is the test carried out in (SuSE) Linux OS inside that the batch carried out in this embodiment is tested automatically, for comparing the quality of the System build performance of the (SuSE) Linux OS of different editions.In other embodiments of the present invention, above-mentioned different client can also operate in dissimilar operating system, such as operate in Windows operating system and (SuSE) Linux OS, then mean that above-mentioned batch is automatically tested the System build performance that may be used for equally dissimilar operating system and carried out batch testing.
The foregoing is only preferred embodiment of the present invention; not thereby embodiments of the present invention and protection domain is limited; to those skilled in the art; should recognize and all should be included in the scheme that equivalent replacement done by all utilizations instructions of the present invention and diagramatic content and apparent change obtain in protection scope of the present invention.
Claims (8)
1. a batch automatic test approach, it is characterized in that, comprise multiple client and control end, described control end connects each described client respectively, and for controlling the automatic testing process of each described client, each described client is normally run respectively under different operating system, also comprises:
Step S1, the testing tool of each for correspondence described client is issued to each described client and carries out relying on the installation operation of corresponding described operating system by described control end successively;
Step S2, each described client applies the test that mounted described testing tool carries out System build performance respectively, and monitoring obtains the test data produced in test process;
Step S3, described test data is reported to described control end by each described client respectively, to complete the test to described System build performance, with backed off after random.
2. batch automatic test approach as claimed in claim 1, it is characterized in that, before performing described step S1, each described client is set up SSH mutual trust with described control end respectively and is connected.
3. batch automatic test approach as claimed in claim 1, is characterized in that, before performing described step S1, installs the described operating system of the correspondence needing test in each described client.
4. batch automatic test approach as claimed in claim 1, is characterized in that,
Described step S1 specifically comprises;
Step S11, described control end issues the dependence environment installation kit for arranging the test environment being associated with corresponding described operating system respectively to each described client;
Step S12, the described dependence environment installation kit that described client Auto-mounting receives, to arrange the test environment being associated with corresponding described operating system;
Step S13, described control end issues corresponding described testing tool respectively to each described client;
Step S14, the described testing tool that described client Auto-mounting receives, with step S2 described in rear steering.
5. batch automatic test approach as claimed in claim 1, it is characterized in that, before the described step S1 of execution, in described control end, pre-set the address list comprising the IP address being associated with each described client, all described IP address in described address list is according to the order arrangement preset;
Then in described step S1, described testing tool, according to the described default order of the described IP address of preserving in described address list, is issued in each described client by described control end successively.
6. batch automatic test approach as claimed in claim 1, is characterized in that, pre-set the test parameter being associated with each described client in described control end;
In described step S1, described control end, while issuing described testing tool, issues corresponding described test parameter respectively to each described client;
Then in described step S2, each described client applies corresponding described testing tool respectively, and the described test parameter according to correspondence carries out the test of System build performance.
7. batch automatic test approach as claimed in claim 6, is characterized in that, is all associated with in a test script corresponding to the described testing tool of each described client and described test parameter;
Then in described step S1, described control end starts the described test script being associated with each described client successively, respectively described testing tool and described test parameter are sent to each described client.
8. batch automatic test approach as claimed in claim 1, it is characterized in that, described client is normally run on the (SuSE) Linux OS of different editions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510834003.XA CN105512026A (en) | 2015-11-25 | 2015-11-25 | Automatic batch testing method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510834003.XA CN105512026A (en) | 2015-11-25 | 2015-11-25 | Automatic batch testing method |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105512026A true CN105512026A (en) | 2016-04-20 |
Family
ID=55720027
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510834003.XA Pending CN105512026A (en) | 2015-11-25 | 2015-11-25 | Automatic batch testing method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105512026A (en) |
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107943636A (en) * | 2017-12-07 | 2018-04-20 | 郑州云海信息技术有限公司 | It is a kind of that the method tested is performed based on more machine batches under Linux |
| CN108829599A (en) * | 2018-06-15 | 2018-11-16 | 郑州云海信息技术有限公司 | A kind of test method and system of the QuickAssist technical software based on Linux |
| CN111104273A (en) * | 2019-12-17 | 2020-05-05 | 深圳忆联信息系统有限公司 | Batch task-based automatic distribution testing method and device and computer equipment |
| CN111198758A (en) * | 2020-01-08 | 2020-05-26 | 深圳忆联信息系统有限公司 | SSH-based Windows software starting method and device and computer equipment |
| CN111538666A (en) * | 2020-04-27 | 2020-08-14 | 深圳忆联信息系统有限公司 | Method and device for collecting test results in batches, computer equipment and storage medium |
| CN113094276A (en) * | 2021-04-15 | 2021-07-09 | 深圳忆联信息系统有限公司 | Batch testing method and device based on Linux system and computer equipment |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0910018A3 (en) * | 1997-10-15 | 2004-12-15 | Alcatel | Error checking method for real-time system software |
| CN101847118A (en) * | 2009-03-24 | 2010-09-29 | 迈普通信技术股份有限公司 | Automatic test system |
| CN102622298A (en) * | 2012-03-02 | 2012-08-01 | 奇智软件（北京）有限公司 | Software testing system and method |
| CN103237082A (en) * | 2013-05-06 | 2013-08-07 | 百度在线网络技术（北京）有限公司 | Cloud testing method, system, and cloud server |
-
2015
- 2015-11-25 CN CN201510834003.XA patent/CN105512026A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP0910018A3 (en) * | 1997-10-15 | 2004-12-15 | Alcatel | Error checking method for real-time system software |
| CN101847118A (en) * | 2009-03-24 | 2010-09-29 | 迈普通信技术股份有限公司 | Automatic test system |
| CN102622298A (en) * | 2012-03-02 | 2012-08-01 | 奇智软件（北京）有限公司 | Software testing system and method |
| CN103237082A (en) * | 2013-05-06 | 2013-08-07 | 百度在线网络技术（北京）有限公司 | Cloud testing method, system, and cloud server |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107943636A (en) * | 2017-12-07 | 2018-04-20 | 郑州云海信息技术有限公司 | It is a kind of that the method tested is performed based on more machine batches under Linux |
| CN108829599A (en) * | 2018-06-15 | 2018-11-16 | 郑州云海信息技术有限公司 | A kind of test method and system of the QuickAssist technical software based on Linux |
| CN111104273A (en) * | 2019-12-17 | 2020-05-05 | 深圳忆联信息系统有限公司 | Batch task-based automatic distribution testing method and device and computer equipment |
| CN111198758A (en) * | 2020-01-08 | 2020-05-26 | 深圳忆联信息系统有限公司 | SSH-based Windows software starting method and device and computer equipment |
| CN111198758B (en) * | 2020-01-08 | 2024-02-13 | 深圳忆联信息系统有限公司 | Windows software starting method and device based on SSH and computer equipment |
| CN111538666A (en) * | 2020-04-27 | 2020-08-14 | 深圳忆联信息系统有限公司 | Method and device for collecting test results in batches, computer equipment and storage medium |
| CN111538666B (en) * | 2020-04-27 | 2024-04-02 | 深圳忆联信息系统有限公司 | Method, device, computer equipment and storage medium for collecting test results in batches |
| CN113094276A (en) * | 2021-04-15 | 2021-07-09 | 深圳忆联信息系统有限公司 | Batch testing method and device based on Linux system and computer equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105512026A (en) | Automatic batch testing method | |
| WO2017012219A1 (en) | Software test method, apparatus and system | |
| CN102752137B (en) | The apparatus and method of virtual machine network parameter are initiatively set | |
| CN104932919A (en) | Implementation method of Linux unattended setup | |
| CN109802867A (en) | A kind of method and system for testing network interface card NCSI connective stability | |
| CN106549789B (en) | Method and system for realizing server installation | |
| CN110825985B (en) | Data acquisition system, method, device, control equipment and proxy equipment | |
| CN103200271A (en) | Advanced Risc machine (ARM) server and method of automatic installation system thereof | |
| CN106502713A (en) | A kind of method for upgrading software and system | |
| CN105119732A (en) | Device and method for distributing hosts in cluster environment | |
| CN112749095A (en) | Method, system and medium for switching operating system to execute test task | |
| CN104503802A (en) | Server-side configuration method for unattended and remote installation operation system | |
| CN113849228A (en) | Operating system batch deployment method, system, terminal and storage medium | |
| CN111273924A (en) | Software updating method and device | |
| CN105183528A (en) | Server bios upgrading method and system | |
| CN107071043A (en) | The collocation method and device of a kind of network information | |
| CN105404569A (en) | Method for testing remote Power Reset of server | |
| CN105653408A (en) | Test method for carrying out POWER CYCLE startup and shutdown on the basis of BMC (Baseboard Management Controller) IPMITOOL (Intelligent Platform Management Interface) command single-node batch control | |
| CN104935451A (en) | Fault detection method and device | |
| CN113268254A (en) | Cluster system installation method and device, electronic equipment and storage medium | |
| CN105159725A (en) | Method for establishing PXE server in RHEL6.6 system | |
| US20060048137A1 (en) | Method and apparatus for cloning an ORACLE RDBMS software | |
| CN105373477B (en) | Capacity testing method | |
| CN110737444A (en) | Remote self-adaptive dynamic deployment method and system for operating system based on firmware | |
| CN103279374A (en) | Operating system distributing technology based on MAC addresses |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160420 |