CN111625404A - Method for testing NVMe hard disk based on Jenkins, system storage medium and electronic equipment - Google Patents
Method for testing NVMe hard disk based on Jenkins, system storage medium and electronic equipment Download PDFInfo
- Publication number
- CN111625404A CN111625404A CN202010317246.7A CN202010317246A CN111625404A CN 111625404 A CN111625404 A CN 111625404A CN 202010317246 A CN202010317246 A CN 202010317246A CN 111625404 A CN111625404 A CN 111625404A
- Authority
- CN
- China
- Prior art keywords
- test
- jenkins
- task
- testing
- tested
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 413
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000004590 computer program Methods 0.000 claims description 16
- 230000008569 process Effects 0.000 claims description 9
- 230000002159 abnormal effect Effects 0.000 claims description 8
- 238000001514 detection method Methods 0.000 claims description 8
- 230000003993 interaction Effects 0.000 abstract description 4
- 238000013522 software testing Methods 0.000 abstract description 2
- 230000006870 function Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 3
- 238000012545 processing Methods 0.000 description 3
- 230000008901 benefit Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 239000007787 solid Substances 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 238000013142 basic testing Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2205—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing using arrangements specific to the hardware being tested
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/22—Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
- G06F11/2273—Test methods
-
- 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/3684—Test management for test design, e.g. generating new test cases
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Testing Of Individual Semiconductor Devices (AREA)
Abstract
The invention discloses a method for testing an NVMe hard disk based on Jenkins, a system storage medium and electronic equipment, and relates to the technical field of software testing, wherein the method comprises the steps that a Jenkins end acquires a test case to be executed and an equipment identification number of tested equipment which needs to execute the test case, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment of the test case; the Jenkins end sends the test task to a controller corresponding to the tested equipment; the control machine analyzes the test task, controls the tested equipment to execute the test task through a testing machine connected with the control machine, and receives a returned execution result of the test task; and after the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal. According to the invention, the Jenkins end only carries out information interaction with the control machine and is not connected with the test machine, so that the condition that the Jenkins end has too many access clients to cause too long test time is avoided.
Description
Technical Field
The invention relates to the technical field of software testing, in particular to a method for testing an NVMe hard disk based on Jenkins, a system storage medium and electronic equipment.
Background
Jenkins is an open source software project, and is a continuous integration tool developed based on Java for monitoring continuous and repeated work. NVMe is NVM (Non-Volatile Memory) Express, a pcie (pci Express) data transmission based SSD (Solid State Drive) interface protocol. Many NVMe SSD related tests are also developed based on Jenkins' framework, such as firmware new function submission, regular release of firmware versions, regression testing of products, performance testing, and the like. The basic test structure is shown in fig. 1, wherein Database is a Database for storing test data and test results. The Test Machine is a tester, has an operating system, and is mainly used for testing a DUT, issuing commands, executing Test cases and the like. The DUT (device UnderTest) is the tested device, which is referred to herein as an SSD supporting the NVMe protocol.
As shown in fig. 1, each Test node (Test Machine) is directly controlled by a Jenkins terminal, so as to achieve the purpose of executing Test cases, monitoring and recovering Test results. The NVMe SSD is directly connected into the system through a PCIe bus, and in the early stage of product development, a DUT cannot respond to a command sent by a host under certain test cases due to factors such as product instability, so that a system blue screen or crash is caused. Once this occurs, Jenkins cannot access and control the Test Machine, and all programs running on the Test Machine cannot be normally executed and return results along with the crash, and at this time, the recovery of the Test Machine needs to be manually intervened; therefore, in the Test structure, the Ctrl Machine is introduced, which is mainly used to control the Test Machine in some cases, the control includes, but is not limited to, performing operations such as switching on and off and restarting the Test Machine through a relay and other devices, and the Test structure after the Ctrl Machine is newly added is shown in fig. 2.
As shown in fig. 2, the number of Test machines is 4, and the corresponding Ctrl Machine number is also 4. In the structure, once the Jenkins end monitors that the Test Machine has a blue screen or a dead halt, the Jenkins end can restart the Test Machine by controlling the Ctrl Machine, and after the Test Machine is recovered to enter the OS, the subsequent Test is continuously performed according to the requirements of Case.
However, for the operation of the Jenkins end, it is necessary to continuously query the state of each Test stage of the Test Machine, and for an abnormal situation, the Ctrl Machine needs to be accessed again for further control, so that there is a situation that different machines are accessed, which results in a long required Test time.
Disclosure of Invention
Aiming at the defects in the prior art, the invention aims to provide a method for testing an NVMe hard disk based on Jenkins, a system storage medium and electronic equipment.
In order to achieve the above purposes, the technical scheme adopted by the invention is as follows:
the method for testing the NVMe hard disk based on Jenkins comprises the following steps:
the Jenkins end obtains a test case to be executed and an equipment identification number of tested equipment of the test case to be executed, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment of the test case;
the Jenkins end sends the test task to a controller corresponding to the tested equipment;
the control machine analyzes the test task, controls the tested equipment to execute the test task through a testing machine connected with the control machine, and receives a returned execution result of the test task;
and after the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal.
On the basis of the technical scheme, the Jenkins terminal acquires the test case to be executed and the device identification number of the tested device to be executed, and the generating of the test task specifically comprises the following steps:
when the Jenkins terminal obtains a tested device, generating a corresponding test task;
and when the Jenkins terminal acquires a plurality of tested devices, respectively generating test tasks corresponding to the tested devices.
On the basis of the above technical solution, the controller analyzes the test task, controls the device under test to execute the test task through a tester connected to the controller, and after receiving the returned execution result of the test task, and after the test is finished, the controller generates all test information into a test log and sends the test log to the Jenkins terminal, and before the controller further includes:
the control machine detects the test result;
and when the test result shows that the test case is abnormal, the controller controls the tester to process.
On the basis of the above technical solution, after the test is finished, the step of the controlling machine generating a test log file from all the test information and sending the test log file to the Jenkins terminal further includes:
the Jenkins end receives the test log file and stores the test log file in a database;
and the Jenkins end detects and analyzes the test log file and displays an analysis result.
The invention also provides a technical scheme, and the system for testing the NVMe hard disk based on Jenkins comprises a Jenkins server, a plurality of controllers, a plurality of testing machines and tested equipment; the Jenkins server is connected with the plurality of controllers, and the testing machines are respectively connected with the controllers and the tested devices in a one-to-one correspondence manner;
the Jenkins server acquires a test case to be executed and an equipment identification number of tested equipment of the test case to be executed, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment of the test case;
the Jenkins server sends the test task to a controller corresponding to a tester connected with the tested equipment;
the control machine analyzes the test task, controls the tested equipment to execute the test task through the test machine connected with the control machine, and receives a returned execution result of the test task;
and the control machine generates all test information into a test log file and sends the test log file to the Jenkins server after the test is finished.
On the basis of the technical scheme, the method further comprises the following steps:
the Jenkins server generates a corresponding test task when acquiring a tested device;
and the Jenkins server respectively generates test tasks corresponding to the tested devices when acquiring the tested devices.
On the basis of the technical scheme, the method further comprises the following steps:
the control machine detects the test result;
and the control machine controls the testing machine to process when the test result shows that the test case is abnormal.
On the basis of the technical scheme, the method further comprises the following steps:
the Jenkins server receives the test log file and stores the test log file in a database;
and the Jenkins server performs detection analysis on the test log file and displays an analysis result.
The invention also provides a storage medium having stored thereon a computer program which, when executed by a processor, implements any of the methods described above.
The invention also provides an electronic device comprising a memory and a processor, wherein the memory stores a computer program running on the processor, and the processor implements any one of the above methods when executing the computer program
Compared with the prior art, the invention has the advantages that:
(1) the Jenkins end only carries out information interaction with the control machine and is not connected with the test machine, and therefore the situation that the Jenkins end visits too many clients to cause too long test time is avoided.
(2) The Jenkins end is only used for simple task issuing and result monitoring, real test operation and execution control are issued to the Ctrl Machine, and complexity of realization of Jenkins end codes is reduced, so that the Jenkins end codes are easy to maintain and debug.
(3) The automatic test hierarchy is clearly divided, and the portability and the easy debugging performance of the test and control codes are improved.
(4) The execution parallel rate of the trigger test case is improved, and the test trigger waiting and finishing time is reduced.
(5) The use of the cross-regional network is relieved, the frequency and the load of the network are reduced, and the situation that subsequent test cases cannot be executed due to the cross-regional network is avoided.
Drawings
FIG. 1 is a schematic diagram of a basic architecture;
FIG. 2 is a schematic diagram of a current general architecture;
FIG. 3 is a flowchart of a method for testing an NVMe hard disk based on Jenkins in the embodiment of the present invention;
FIG. 4 is a schematic diagram of an improved architecture of the present invention;
FIG. 5 is a flowchart of a method for testing an NVMe hard disk based on Jenkins in the embodiment of the present invention;
FIG. 6 is a flowchart of a method for testing an NVMe hard disk based on Jenkins in the embodiment of the present invention;
fig. 7 is a schematic structural diagram of a system for testing NVMe hard disks based on Jenkins in the embodiment of the present invention.
Description of the drawings:
100 system for testing NVMe hard disk based on Jenkins
110Jenkins server 120 control machine
130 testing machine 140 device under test
Detailed Description
The present invention will be described in further detail with reference to the accompanying drawings and examples.
As shown in fig. 3, an embodiment of the present invention provides a method for testing an NVMe hard disk based on Jenkins, including:
s100, a Jenkins terminal acquires a test case to be executed and an equipment identification number of tested equipment which needs to execute the test case, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment which executes the test case;
s200, the Jenkins end sends the test task to a control machine uniquely corresponding to the tested equipment;
s300, the control machine analyzes the test task, controls the tested equipment to execute the test task through a testing machine connected with the control machine, and receives a returned execution result of the test task;
s400, after the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal.
Specifically, in this embodiment, as shown in fig. 4, a Jenkins end (Jenkins Server) is connected to a plurality of controllers, each controller is connected to a corresponding tester, and the testers are connected to the testees respectively for testing.
A user inputs a test case to be executed and an equipment identification number of tested equipment which needs to execute the test case in a webpage control end or other input devices, a Jenkins end generates a corresponding test task after acquiring information input by the user, the test task comprises the test case and test parameters of the tested equipment which executes the test case, the equipment parameters of different tested equipment are different, and the corresponding test parameters are different accordingly.
Because each tested device uniquely corresponds to the testing machine, and the testing machine uniquely corresponds to the control machine, the control machine uniquely corresponding to the tested device is determined according to the device identification number of the tested device, and the Jenkins end sends the testing task to the control machine corresponding to the tested device.
And the control machine receives and analyzes the test task, and controls the tested equipment to execute the test task through the test machine connected with the control machine. And then the control machine receives the execution result of the tested device executing the test task, which is returned by the test machine, and when the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal, wherein the test information is all data which are received and sent by the control machine and are related to the test in the test process, such as the control machine tests the tested device, the received execution result, the decision aiming at the analysis of the execution result and the like.
According to the invention, the Jenkins end only carries out information interaction with the control machine and is not connected with the test machine, so that the number of machines for inquiry and operation processing of the Jenkins end is reduced, the network pressure is relieved, and the condition that the Jenkins end has too many access clients to cause too long test time is avoided.
Preferably, in another embodiment of the present invention, the step of obtaining, by the S100Jenkins terminal, the test case to be executed and the device identification number of the device under test that needs to execute the test case, and the generating of the test task specifically includes:
s110, when the Jenkins terminal obtains a tested device, generating a corresponding test task;
and S120, when the Jenkins end obtains a plurality of tested devices, respectively generating test tasks corresponding to the tested devices.
Specifically, in this embodiment, a user inputs a test case to be executed and an equipment identification number of a device under test that needs to execute the test case in a web control end or other input devices, and since the Jenkins end is connected to a plurality of controllers, the device under test corresponding to all the controllers does not need to be tested.
The method comprises the steps that a Jenkins end generates a corresponding test task after acquiring information input by a user, and when the Jenkins end only acquires one tested device, the test task corresponding to the tested device is generated; and when the Jenkins end acquires a plurality of tested devices, respectively generating test tasks corresponding to the tested devices. When the Jenkins end obtains a plurality of test cases to be executed by the tested devices, the test cases to be executed by the tested devices may be the same or different. However, the test tasks include test cases and test parameters of the tested devices executing the test cases, and the different tested devices have different device parameters and different corresponding test parameters, so that even if a plurality of tested devices execute the same test cases, the test tasks corresponding to the tested devices are also respectively generated, and the same test tasks do not exist.
The Jenkins end is connected with the plurality of controllers, so that the test concurrency efficiency is improved, once the Jenkins end issues the test tasks to the corresponding controllers, the test of all the tested devices is carried out simultaneously, the time for polling initialization, preparation and the like of the Jenkins end is not wasted, as the task issuing speed of the Jenkins end is very high (millisecond level), once the Jenkins end issues to the controllers, necessary control and operation can be immediately carried out, the parallelism rate almost reaches 100%, and the test machine has very obvious benefit under the condition of configuring a large batch of test machines. In the specific design implementation process, the operation system configuration and other related information of the controller need to be considered, and the environment and the like of the controller are uniformly configured as much as possible, so that the batch automation is conveniently implemented.
As shown in fig. 5, in another embodiment of the present invention, a method for testing NVMe hard disks based on Jenkins is provided, including:
s100, a Jenkins terminal acquires a test case to be executed and an equipment identification number of tested equipment which needs to execute the test case, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment which executes the test case;
s200, the Jenkins end sends the test task to a control machine uniquely corresponding to the tested equipment;
s300, the control machine analyzes the test task, controls the tested equipment to execute the test task through a testing machine connected with the control machine, and receives a returned execution result of the test task;
s350, the control machine detects the test result;
s360, when the test result shows that the test case is abnormal, the controller controls the test machine to process;
s400, after the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal.
Specifically, in this embodiment, after the Jenkins end obtains the test case to be executed and the device identification number of the device under test that needs to execute the test case, which are input by the user, a corresponding test task is generated, where the test task includes the test case and the test parameters of the device under test that executes the test case. And the Jenkins end sends the test task to the control machine uniquely corresponding to the tested equipment.
And the control machine receives and analyzes the test task, and controls the tested equipment to execute the test task through the test machine connected with the control machine. And then the control machine receives the execution result of the tested device executing the test task, which is returned by the test machine.
The control machine detects the received test result, and controls the test machine to process when the test result shows that the test case is abnormal. The control machine is provided with all interfaces such as hardware relays for exception handling, serial port control and the like, so that the exception of the test case can be detected at the first time, the corresponding exception can be recovered, and the efficiency is higher. And when the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal.
The functions of test execution, result detection, exception handling and the like of the Jenkins end lowering are completely main interaction between the controller and the tester without excessive control participation of the Jenkins end. The controller plays a larger role, the detection and the exception handling of the Test case result are carried out at the first time, the detection and the exception handling are more efficient and timely compared with the participation of the Jenkins, and the exception handling and the recovery are not required to be carried out until the Jenkins poll to the Test Machine state.
As shown in fig. 6, in another embodiment of the present invention, a method for testing NVMe hard disks based on Jenkins is provided, including:
s100, a Jenkins terminal acquires a test case to be executed and an equipment identification number of tested equipment which needs to execute the test case, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment which executes the test case;
s200, the Jenkins end sends the test task to a control machine uniquely corresponding to the tested equipment;
s300, the control machine analyzes the test task, controls the tested equipment to execute the test task through a testing machine connected with the control machine, and receives a returned execution result of the test task;
s400, after the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal;
s500, the Jenkins end receives the test log file and stores the test log file in a database;
s600, the Jenkins end carries out detection analysis on the test log file, and an analysis result is displayed.
Specifically, in this embodiment, after the Jenkins end obtains the test case to be executed and the device identification number of the device under test that needs to execute the test case, which are input by the user, a corresponding test task is generated, where the test task includes the test case and the test parameters of the device under test that executes the test case. And the Jenkins end sends the test task to the control machine uniquely corresponding to the tested equipment.
And the control machine receives and analyzes the test task, and controls the tested equipment to execute the test task through the test machine connected with the control machine. And then the control machine receives the execution result of the tested device executing the test task, which is returned by the test machine. And when the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal.
And the Jenkins end receives the test log file and stores the test log file in a database. And then the Jenkins end detects and analyzes the test log file, and displays the analysis result on the webpage control end, so that the user can call and check conveniently.
The invention can transfer the execution, result detection and exception handling functions of the test case to the controller under the condition of ensuring that the basic framework is not changed, the Jenkins end is only used for issuing tasks to the corresponding controller, and the processing conditions of the collecting controller, namely the test log files, are detected and collected without other operations, thereby reducing the polling waiting time, reducing the difficulty of realizing Jenkins end codes and handling exceptions and providing a universal framework easy to transplant.
As shown in fig. 7, in another embodiment of the present invention, a system 100 for testing NVMe hard disks based on Jenkins is provided, which includes: a Jenkins server 110, a plurality of control machines 120, a plurality of test machines 130 and a tested device 140; the Jenkins server 110 is connected to the plurality of controllers 120, and the testing machines 130 are respectively connected to the controllers 120 and the devices under test 140 in a one-to-one correspondence manner;
the Jenkins server 110 obtains a test case to be executed and an equipment identification number of the tested equipment 140 which needs to execute the test case, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment 140 of the test case;
the Jenkins server 110 sends the test task to the controller 120 corresponding to the tester 130 connected to the device under test 140;
the controlling machine 120 analyzes the test task, controls the device under test 140 to execute the test task through the testing machine 130 connected to the controlling machine, and receives a returned execution result of the test task;
after the test is finished, the controller 120 generates a test log file from all the test information and sends the test log file to the Jenkins server 110.
Further comprising: the Jenkins server 110 generates a corresponding test task when acquiring a tested device 140;
when acquiring a plurality of tested devices 140, the Jenkins server 110 generates test tasks corresponding to the tested devices 140 respectively.
Further comprising:
the controller 120 detects the test result;
the controller 120 controls the tester 130 to process the test case when the test result shows that the test case is abnormal.
Further comprising:
the Jenkins server 110 receives the test log file and stores the test log file in a database;
the Jenkins server 110 performs detection analysis on the test log file, and displays an analysis result.
Specifically, the specific implementation of each module in this embodiment has been described in detail in the corresponding method embodiment, and therefore, the detailed description is not repeated.
In further embodiments of the invention, examples of testing are performed by the architectures of fig. 2 and 4, respectively.
Taking 10 test machines as an example, table 1 is the time required for testing the current generic architecture of fig. 2, and table 2 is the time required for testing the improved architecture of fig. 4.
TABLE 1 test time for 10 test machines of the current generic architecture
TABLE 2 improved test time for 10 testers in post-test configuration
An embodiment of the invention provides a computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out all or part of the method steps of the first embodiment.
All or part of the flow of the method according to the embodiments of the present invention may be implemented by a computer program, which may be stored in a computer-readable storage medium and used by a processor to implement the steps of the embodiments of the method. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an executable file or some intermediate form, etc. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, etc. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
An embodiment of the present invention further provides an electronic device, which includes a memory and a processor, wherein the memory stores a computer program running on the processor, and the processor executes the computer program to implement all or part of the method steps in the first embodiment.
The Processor may be a Central Processing Unit (CPU), other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable gate array (FPGA) or other Programmable logic device, discrete gate or transistor logic device, discrete hardware component, or the like. The general purpose processor may be a microprocessor or the processor may be any conventional processor or the like which is the control center for the computer device and which connects the various parts of the overall computer device using various interfaces and lines.
The memory may be used to store the computer programs and/or modules, and the processor may implement various functions of the computer device by running or executing the computer programs and/or modules stored in the memory and invoking data stored in the memory. The memory may mainly include a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data (such as audio data, video data, etc.) created according to the use of the cellular phone, etc. In addition, the memory may include high speed random access memory, and may also include non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), at least one magnetic disk storage device, a Flash memory device, or other volatile solid state storage device.
The present invention is not limited to the above-described embodiments, and it will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the principle of the present invention, and such modifications and improvements are also considered to be within the scope of the present invention. Those not described in detail in this specification are within the skill of the art.
Claims (10)
1. A method for testing NVMe hard disks based on Jenkins is characterized by comprising the following steps:
the method comprises the steps that a Jenkins terminal obtains a test case to be executed and an equipment identification number of tested equipment which needs to execute the test case, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment which executes the test case;
the Jenkins end sends the test task to a controller which is only corresponding to the tested equipment;
the control machine analyzes the test task, controls the tested equipment to execute the test task through a testing machine connected with the control machine, and receives a returned execution result of the test task;
and after the execution result shows that the test is finished, the control machine generates all test information into a test log file and sends the test log file to the Jenkins terminal.
2. The method for testing the NVMe hard disk based on Jenkins as claimed in claim 1, wherein the Jenkins terminal obtains a test case to be executed and an equipment identification number of a device under test on which the test case is to be executed, and the generating of the test task specifically comprises:
when the Jenkins terminal obtains a tested device, generating a corresponding test task;
and when the Jenkins terminal acquires a plurality of tested devices, respectively generating test tasks corresponding to the tested devices.
3. The method for testing the NVMe hard disk based on Jenkins according to claim 1, wherein the step of the controller analyzing the test task, controlling the device under test to execute the test task through a tester connected to the controller, receiving the returned execution result of the test task, and after the test is finished, the step of the controller generating all test information into a test log and sending the test log to the Jenkins terminal further includes:
the control machine detects the test result;
and when the test result shows that the test case is abnormal, the controller controls the tester to process.
4. The method for testing the NVMe hard disk based on Jenkins according to claim 1, wherein after the test is finished, the controlling machine generates all test information into a test log file and sends the test log file to the Jenkins terminal, and the method further comprises the following steps:
the Jenkins end receives the test log file and stores the test log file in a database;
and the Jenkins end detects and analyzes the test log file and displays an analysis result.
5. The system for testing the NVMe hard disk based on Jenkins is characterized by comprising a Jenkins server, a plurality of controllers, a plurality of testing machines and tested equipment; the Jenkins server is connected with the plurality of controllers, and the testing machines are respectively connected with the controllers and the tested devices in a one-to-one correspondence manner;
the Jenkins server acquires a test case to be executed and an equipment identification number of tested equipment of the test case to be executed, and generates a test task, wherein the test task comprises the test case and test parameters of the tested equipment of the test case;
the Jenkins server sends the test task to a controller corresponding to a tester connected with the tested equipment;
the control machine analyzes the test task, controls the tested equipment to execute the test task through the test machine connected with the control machine, and receives a returned execution result of the test task;
and the control machine generates all test information into a test log file and sends the test log file to the Jenkins server after the test is finished.
6. The Jenkins-based NVMe hard disk testing system according to claim 5, further comprising:
the Jenkins server generates a corresponding test task when acquiring a tested device;
and the Jenkins server respectively generates test tasks corresponding to the tested devices when acquiring the tested devices.
7. The Jenkins-based NVMe hard disk testing system according to claim 5, further comprising:
the control machine detects the test result;
and the control machine controls the testing machine to process when the test result shows that the test case is abnormal.
8. The Jenkins-based NVMe hard disk testing system according to claim 5, further comprising:
the Jenkins server receives the test log file and stores the test log file in a database;
and the Jenkins server performs detection analysis on the test log file and displays an analysis result.
9. A storage medium having stored thereon a computer program, wherein the computer program, when executed by a processor, implements the method for testing NVMe hard disks based on Jenkins according to any one of claims 1 to 4.
10. An electronic device comprising a storage medium, a processor and a computer program stored in the storage medium and executable on the processor, wherein the processor implements the method for testing the NVMe hard disk based on Jenkins according to any one of claims 1-4 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010317246.7A CN111625404B (en) | 2020-04-21 | 2020-04-21 | Method, system storage medium and electronic equipment for testing NVMe hard disk based on Jenkins |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010317246.7A CN111625404B (en) | 2020-04-21 | 2020-04-21 | Method, system storage medium and electronic equipment for testing NVMe hard disk based on Jenkins |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111625404A true CN111625404A (en) | 2020-09-04 |
| CN111625404B CN111625404B (en) | 2023-06-30 |
Family
ID=72260066
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010317246.7A Active CN111625404B (en) | 2020-04-21 | 2020-04-21 | Method, system storage medium and electronic equipment for testing NVMe hard disk based on Jenkins |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111625404B (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113138886A (en) * | 2021-04-23 | 2021-07-20 | 摩拜(北京)信息技术有限公司 | Method and device for testing embedded equipment and testing equipment |
| CN113254326A (en) * | 2021-04-06 | 2021-08-13 | 至誉科技（武汉）有限公司 | Method and system for releasing firmware codes of solid state disk by utilizing Jenkins |
| CN114461150A (en) * | 2022-02-09 | 2022-05-10 | 马来西亚明试国际有限公司 | Method, system and storage medium for automatic test equipment data aggregation |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101252471A (en) * | 2008-03-20 | 2008-08-27 | 中兴通讯股份有限公司 | Distributed automatization test system and method |
| US8368915B1 (en) * | 2006-06-23 | 2013-02-05 | Open Invention Network, Llc | System and method for printer driver management in an enterprise network |
| CN104008055A (en) * | 2014-05-30 | 2014-08-27 | 广州华多网络科技有限公司 | Software testing method, device and system |
| CN109446006A (en) * | 2018-10-24 | 2019-03-08 | 郑州云海信息技术有限公司 | Distributed Raid characteristic test method, device, equipment and storage medium |
| US20190294535A1 (en) * | 2018-03-23 | 2019-09-26 | Sungard Availability Services, Lp | Unified test automation system |
| CN110456777A (en) * | 2019-08-20 | 2019-11-15 | 广州小鹏汽车科技有限公司 | The test method and system of vehicle control device |
| CN110718264A (en) * | 2019-09-23 | 2020-01-21 | 深圳忆联信息系统有限公司 | Method and device for testing information of solid state disk, computer equipment and storage medium |
| CN110928774A (en) * | 2019-11-07 | 2020-03-27 | 杭州顺网科技股份有限公司 | Automatic test system based on node formula |
-
2020
- 2020-04-21 CN CN202010317246.7A patent/CN111625404B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8368915B1 (en) * | 2006-06-23 | 2013-02-05 | Open Invention Network, Llc | System and method for printer driver management in an enterprise network |
| CN101252471A (en) * | 2008-03-20 | 2008-08-27 | 中兴通讯股份有限公司 | Distributed automatization test system and method |
| CN104008055A (en) * | 2014-05-30 | 2014-08-27 | 广州华多网络科技有限公司 | Software testing method, device and system |
| US20190294535A1 (en) * | 2018-03-23 | 2019-09-26 | Sungard Availability Services, Lp | Unified test automation system |
| CN109446006A (en) * | 2018-10-24 | 2019-03-08 | 郑州云海信息技术有限公司 | Distributed Raid characteristic test method, device, equipment and storage medium |
| CN110456777A (en) * | 2019-08-20 | 2019-11-15 | 广州小鹏汽车科技有限公司 | The test method and system of vehicle control device |
| CN110718264A (en) * | 2019-09-23 | 2020-01-21 | 深圳忆联信息系统有限公司 | Method and device for testing information of solid state disk, computer equipment and storage medium |
| CN110928774A (en) * | 2019-11-07 | 2020-03-27 | 杭州顺网科技股份有限公司 | Automatic test system based on node formula |
Non-Patent Citations (2)
| Title |
|---|
| 徐旼之: "基于云的接口自动化测试平台的设计与实现" * |
| 测试工程师: "Jenkins分布式测试" * |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113254326A (en) * | 2021-04-06 | 2021-08-13 | 至誉科技（武汉）有限公司 | Method and system for releasing firmware codes of solid state disk by utilizing Jenkins |
| CN113138886A (en) * | 2021-04-23 | 2021-07-20 | 摩拜(北京)信息技术有限公司 | Method and device for testing embedded equipment and testing equipment |
| CN114461150A (en) * | 2022-02-09 | 2022-05-10 | 马来西亚明试国际有限公司 | Method, system and storage medium for automatic test equipment data aggregation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111625404B (en) | 2023-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111625404B (en) | Method, system storage medium and electronic equipment for testing NVMe hard disk based on Jenkins | |
| US20200151072A1 (en) | Method, computer apparatus, and user interface for performing automatic test upon storage devices | |
| WO2020134634A1 (en) | Program debugging method, program debugging apparatus, terminal device, and storage medium | |
| WO2022179034A1 (en) | Automatic testing method and apparatus, electronic device, and storage medium | |
| CN105512000B (en) | Operating system abnormal information collection method and device and computer | |
| CN110865944A (en) | Data analysis method and device for test case, storage medium and test equipment | |
| CN109086175B (en) | Board card testing method and device | |
| CN112445708A (en) | Pressure testing method and device and computing equipment | |
| CN108984216B (en) | Method and device for automatically entering and configuring BIOS | |
| CN112035346A (en) | Automatic testing method, system and medium based on embedded DSP operating system | |
| CN107168756B (en) | Radio frequency driving compiling and debugging method, client, server and storage device | |
| CN112650678B (en) | Jenkins-based audio and video acceleration card product automatic test system and method | |
| CN114721686A (en) | Configuration data updating method and device, electronic equipment and storage medium | |
| CN114996081A (en) | Batch job progress monitoring method and device, electronic equipment and storage medium | |
| CN116414634A (en) | Device debugging method, system, device, debugging device and readable storage medium | |
| CN113010417A (en) | Script execution method and device based on automatic test | |
| CN112527329A (en) | Mass production method and system of solid-state storage device, terminal device and storage medium | |
| CN112148376A (en) | Terminal starting method and device | |
| CN112667463A (en) | Application system baseline state monitoring method and device | |
| CN111913758A (en) | Automatic adding method, device and system of component monitoring task | |
| CN109144798B (en) | Intelligent management system with machine learning function | |
| CN105988818B (en) | Automatic bug debugging system and method | |
| CN117251361A (en) | Method, device, equipment and storage medium for testing system stability | |
| CN117573504A (en) | Test management method and system, scheduling device and storage medium | |
| CN116149941A (en) | Monitoring method and device of server component, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| CP03 | Change of name, title or address |
Address after: 430000 west of 2-3 / F, No.2 factory building, Guannan Industrial Park, No.1 Gaoxin 2nd Road, Wuhan Donghu New Technology Development Zone, Wuhan City, Hubei Province Patentee after: Zhiyu Technology Co.,Ltd. Address before: 438600 Room 201, Juxian building, block B, changju Science Park, Gaoxin 6th Road, Donghu New Technology Development Zone, Wuhan, Hubei Province Patentee before: EXASCEND TECHNOLOGY (WUHAN) CO.,LTD. |
|
| CP03 | Change of name, title or address |