CN111104274A - Automatic testing method, device and equipment for SSD (solid State disk) and readable storage medium - Google Patents
Automatic testing method, device and equipment for SSD (solid State disk) and readable storage medium Download PDFInfo
- Publication number
- CN111104274A CN111104274A CN201911318460.8A CN201911318460A CN111104274A CN 111104274 A CN111104274 A CN 111104274A CN 201911318460 A CN201911318460 A CN 201911318460A CN 111104274 A CN111104274 A CN 111104274A
- Authority
- CN
- China
- Prior art keywords
- script
- test
- ssd
- common
- group
- 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 192
- 239000007787 solid Substances 0.000 title description 2
- 238000013515 script Methods 0.000 claims abstract description 279
- 238000012545 processing Methods 0.000 claims description 10
- 230000006870 function Effects 0.000 claims description 7
- 238000012216 screening Methods 0.000 claims description 5
- 238000010998 test method Methods 0.000 claims 1
- 238000000034 method Methods 0.000 abstract description 19
- 238000012423 maintenance Methods 0.000 abstract description 7
- 230000009286 beneficial effect Effects 0.000 abstract description 2
- 230000008569 process Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000006978 adaptation Effects 0.000 description 2
- 238000004422 calculation algorithm Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 239000002699 waste material Substances 0.000 description 2
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002085 persistent effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000001105 regulatory effect Effects 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000000844 transformation Methods 0.000 description 1
- 230000001052 transient effect Effects 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
-
- 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
Abstract
The application discloses an automatic SSD hard disk testing method, which comprises the following steps: determining the same scripts and special scripts in a belmr script group and a harding script group; merging the same scripts and adding the merged scripts to a common test script group; adding the exclusive script to the common script group after adding the corresponding project identifier; when a test instruction is received, determining the type of the SSD to be tested; and calling the script matched with the type in the common script group to test the SSD disk to be tested. The method combines the test platforms aiming at the belmr and the harding, finishes the automatic tests aiming at various types of disks by using a set of codes, greatly reduces the total number of the scripts to be maintained after combination, and can obviously improve the platform maintenance efficiency. The application also provides an automatic testing device and equipment for the SSD hard disk and a readable storage medium, and the automatic testing device and equipment have the beneficial effects.
Description
Technical Field
The present disclosure relates to the field of hard disk testing technologies, and in particular, to an automatic testing method, an automatic testing device, an automatic testing apparatus, and a readable storage medium for an SSD hard disk.
Background
The Rand _ test _ day is a collective general name of an automatic test script for the SSD hard disk, comprises various scenes such as reading and writing, formatting and the like and various operations of mixed scenes, and achieves the aim of comprehensive and system test for the SSD by executing the randomized test of the script in different sequences.
The Rand _ test _ day mainly contains tests of two items, namely belmr and harding. The two projects respectively contain more than 200 scripts, and the same and similar scripts account for more than 80% of the two projects, so that when the scripts are changed or a common script is newly added, the two platforms need to be maintained, time is consumed, errors are easy to occur, and the platform maintenance efficiency is low.
Disclosure of Invention
The application aims to provide an automatic testing method for the SSD, which can obviously improve the maintenance efficiency of a platform; another object of the present application is to provide an SSD hard disk automated testing apparatus, device and readable storage medium.
In order to solve the technical problem, the present application provides an automatic testing method for an SSD hard disk, including:
determining the same scripts and special scripts in a belmr script group and a harding script group;
merging the same scripts and then adding the merged scripts to a common test script group; the common test script group is a preset test script group for testing belmar or harding;
adding the exclusive script to the common script group after adding the corresponding project identifier;
when a test instruction is received, determining the type of the SSD to be tested;
and calling the script matched with the type in the common script group to test the SSD disk to be tested.
Optionally, merging the same scripts and adding the merged scripts to a common test script group, including:
judging whether the names of the same scripts in the Belmar script group and the harding script group are the same or not;
if not, unifying the naming rule and then adding a script to the common test script group;
and if so, adding a script to the common test script group.
Optionally, adding the exclusive script to the common script group after adding the corresponding item identifier, including:
and adding a corresponding project prefix in front of the original script name of the exclusive script, and adding the exclusive script added with the project prefix to the common script group.
Optionally, when the test instruction is received, determining the type of the SSD disk to be tested includes:
when a test instruction is received, determining an lspci value of the SSD to be tested;
the type of disc is determined from the lspci value.
Optionally, calling the script in the common script group, which is matched with the type, to test the SSD disk to be tested, includes:
traversing each script in the common script group, and screening out scripts without item identifications and scripts matched with the item identifications as test scripts;
and calling the test script to test the SSD disk to be tested.
Optionally, calling the script in the common script group, which is matched with the type, to test the SSD disk to be tested, includes:
determining the drive letter of each SSD to be tested;
calling the script matched with the type to generate a test file corresponding to each SSD to be tested, and issuing the test file to the corresponding SSD to be tested according to the disc identifier;
and calling each test file to test the corresponding SSD disk to be tested.
Optionally, invoking the script with the matched type to generate a test file corresponding to each SSD disk to be tested, including:
and adjusting the nvnum parameter in the common function common.sh in the script with the matched type to the parameter value corresponding to each SSD disk to be tested, and generating a test file corresponding to each SSD disk to be tested.
The application discloses automatic testing arrangement of SSD hard disk includes:
the script distinguishing unit is used for determining the same scripts and exclusive scripts in the belmr script group and the harding script group;
the first processing unit is used for merging the same scripts and then adding the merged scripts to a common test script group; the common test script group is a preset test script group for testing belmar or harding;
the second processing unit is used for adding the exclusive script to the common script group after adding the corresponding project identifier;
the type determining unit is used for determining the type of the SSD disk to be tested when the test instruction is received;
and the disk testing unit is used for calling the script matched with the type in the common script group to test the SSD disk to be tested.
The application discloses automatic test equipment of SSD hard disk includes:
a memory for storing a program;
and the processor is used for realizing the steps of the SSD hard disk automatic testing method when the program is executed.
The application discloses a readable storage medium, wherein a program is stored on the readable storage medium, and when the program is executed by a processor, the steps of the SSD hard disk automatic testing method are realized.
The automatic testing method for the SSD provided by the application comprises the following steps: determining the same scripts and special scripts in a belmr script group and a harding script group; merging the same scripts and adding the merged scripts to a common test script group; wherein, the common test script group is a preset test script group for testing belmar or harding; adding the exclusive script to the common script group after adding the corresponding project identifier; when a test instruction is received, determining the type of the SSD to be tested; and calling the script matched with the type in the common script group to test the SSD disk to be tested. The method combines the test platforms aiming at the belmr and the harding, and finishes the automatic tests aiming at the multi-type discs in different types by using a set of codes, and because the same and similar scripts account for more than 80 percent in the two items, the total number of the scripts to be maintained after combination is greatly reduced, and the platform maintenance efficiency can be obviously improved.
The application also provides an automatic testing device and equipment for the SSD and a readable storage medium, which have the beneficial effects and are not repeated herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a flowchart of an SSD hard disk automated testing method provided in the embodiment of the present application;
fig. 2 is a block diagram of a structure of an SSD hard disk automated testing apparatus provided in the embodiment of the present application;
fig. 3 is a schematic structural diagram of an SSD hard disk automated testing device according to an embodiment of the present application.
Detailed Description
The core of the application is to provide an automatic testing method for the SSD, and the method can obviously improve the script maintenance efficiency of a testing platform; another core of the present application is to provide an SSD hard disk automated testing apparatus, device and readable storage medium.
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Referring to fig. 1, fig. 1 is a flowchart illustrating an SSD hard disk automated testing method provided in this embodiment, where the method mainly includes:
step s110, determining the same script and an exclusive script in a belmr script group and a harding script group;
the same script refers to scripts with the same purpose, implementation mode and implementation effect, and some scripts meeting the above conditions may have some conceivable transformations on some statements, and may also be classified as the same script; accordingly, a proprietary script refers to a script in another script group for which the same script does not exist, which is specific to the type of SSD disk test to which it belongs.
The same scripts and the special scripts in the Belman script group and the harding script group are determined, so that the Belman script group and the harding script group are combined, and the Rand _ test _ day platform is maintained conveniently.
Step s120, merging the same scripts and adding the merged scripts to a common test script group; wherein, the common test script group is a preset test script group for testing belmar or harding;
for the same scripts of the two items of the begmar and the harding, merging processing is needed, namely only one part is reserved to be respectively called during the begmar and the harding.
In this embodiment, a specific script combination manner is not limited. Optionally, an implementation manner of script merging is as follows: judging whether the names of the same scripts in the Belmar script group and the harding script group are the same or not; if not, unifying the naming rule and then adding a script to the common test script group; if yes, adding a script to the common test script group. For example, if the r1 script in the belmr script group and the r1 script in the harding script group are the same script, only one r1 script is added to the common test script group; meanwhile, the s1 script in the belmar script group and the s2 script in the harding script group are the same script, the s1 script and the s2 script are named as the s1 script in a unified mode, and a copy of the s1 script is added to the common test script group.
Since the script is generally called by identifying the script name when the script is called, in the embodiment, the combination of the scripts is realized by adding a script to a common test script group after the script name is combined, so as to facilitate the identification of the script type in the calling process. When the names of two same scripts are different, a uniform naming rule is required, a specific uniform mode is not limited in this embodiment, one of the two names may be selected for unification, or names other than the two names may be selected for unification, and the names may be set according to actual use conditions, which is not described herein again.
Step s130, adding the special script to the common script group after adding the corresponding project identifier;
the item identifier refers to a test object identifier of the script, namely, whether the script is used for testing belmar or harding can be distinguished according to the item identifier; since the script is generally called by identifying the script name when the script is called, in order to facilitate fast identification and distinction of the script type, a method for distinguishing the item type of the dedicated script by adding a corresponding identifier to distinguish the adapted item (i.e., the type of the disc) in the script name of the dedicated script is proposed in this embodiment, specifically, one implementation method is as follows: and adding a corresponding project prefix in front of the original script name of the exclusive script, and adding the exclusive script added with the project prefix to the common script group. In this implementation, the dedicated scripts for the belmr and harding items are named separately, for example, the belmr item naming rule is belmr _ XXXX, and the harding item naming rule is harding _ XXXX. In this embodiment, only the above implementation is described as an example, and other implementation manners based on the present application can refer to the description of this embodiment, and are not described herein again.
It should be noted that the execution sequence of step s120 and step s130 is not limited, and may be executed in parallel, or may be executed in sequence, and when the execution sequence is a sequential execution sequence, step s120 may be executed first, or step s130 may be executed first, and fig. 1 only describes the parallel execution as an example, and all other execution sequences may refer to the description of this embodiment.
Step s140, when receiving the test instruction, determining the type of the SSD to be tested;
and adding a judgment rule in the test script, and determining the type of the current SSD to be tested so as to call the script with the matched type for testing and realize the automatic test of multi-disk adaptation. In this embodiment, the determination method of the disc type is not limited, and optionally, an implementation manner is as follows: when a test instruction is received, determining an lspci value of the SSD to be tested; the type of disc is determined from the lspci value. The lspci is used for judging different types of SSD devices (belmar and harding), the lspci value of belmar is 8607, and the lspci value of harding is 8632. The lspci value belongs to the inherent property of the SSD, and the disc types are distinguished through the lspci value, so that errors can be avoided, and the type determination efficiency and accuracy are improved. In this embodiment, only the above implementation manner is described as an example, and other disc type determination manners can refer to the description of this embodiment, which is not described herein again.
And step s150, calling the script matched with the type in the common script group to test the SSD disk to be tested.
The common script group mainly comprises two scripts, a script without an item identifier (namely, a multi-type disc common test script) and a script with an item identifier (namely, an exclusive script under various types of discs), wherein the script with the item identifier mainly comprises a Belmr type script and a harding type script, the process of calling the script matched with the type in the common script group to test the SSD disc to be tested is that the script matched with the current type disc type (comprising the common script and the exclusive script) in the common script group is selected to test the disc, and the process can be realized by directly screening out the common test script and the script with the item identifier corresponding to the current disc type, or by rejecting the script with the item identifier not corresponding to the current disc type, and the process is not limited. Optionally, one implementation is as follows: traversing all scripts in the common script group, and screening out scripts without item identifications and scripts matched with the item identifications as test scripts; and calling the test script to test the SSD disk to be tested. The interference of the unmatched type script can be avoided in the mode, and the screening efficiency is improved.
In addition, in this embodiment, a case that one SSD disk to be tested is mainly used as a reference, but the current script only supports running one disk on one device at the same time, for example, for a server or a PC capable of connecting multiple SSD disks, a large resource waste may be generated, and in order to avoid the resource waste, and improve efficiency and utilization rate of the server and the PC, this embodiment further provides a method that can test multiple SSD disks in the same machine. Correspondingly, the process of calling the script matched with the type in the common script group to test the SSD disk to be tested may specifically include the following steps:
(1) determining a drive letter of each SSD to be tested;
(2) calling the scripts with the matched types to generate test files corresponding to the SSD disks to be tested, and issuing the test files to the corresponding SSD disks to be tested according to the disk identifiers;
the process of calling the script with the matched type to generate the test file corresponding to each SSD disk to be tested may specifically be: and (3) regulating the nvnum parameter in the common function common.sh in the script with the matched type to the parameter value corresponding to each SSD disk to be tested, and generating a test file corresponding to each SSD disk to be tested.
And adding nvnum parameters in a common function common.sh, and taking the nvnum parameters from the nvme devices in all scripts for distinguishing aiming at different nvme devices. For example, the SSD disk to be tested includes a disk 1 and a disk 2, which are respectively installed in the slot 1 and the slot 2, and the nvnum parameter of the disk 1 is set to 1, and the nvnum parameter of the disk 2 is set to 2, and then the nvnum parameter in the common function common.sh in the test file for the disk 1 is adjusted to 1, and the test file is the test file for the disk 1, and the nvnum parameter in the common function common.sh in the test file for the disk 2 is adjusted to 2, and then the test file is the test file for the disk 2, and thus the simultaneous test of the disk 1 and the disk 2 can be achieved.
Of course, other types of device parameters may be added to other functions to indicate different slot positions or different devices, which is not limited herein.
(3) And calling each test file to test the corresponding SSD disk to be tested.
The above-mentioned mode that this embodiment provided can be directed against a plurality of nvme equipment, realizes testing on same server or pc machine, realizes the adaptation test simultaneously of many dishes, promotes the resource utilization of test host computer, promotes efficiency of software testing simultaneously.
It should be noted that, in this manner, the types of the SSD disks to be tested are required to be the same, that is, the entire test files are substantially the same, and calling the script with the matching type to generate the test file corresponding to each SSD disk to be tested only needs to adjust the test object, so that the test file points to the SSD disk to be tested that is issued. Of course, in order to implement the test of multiple different types of SSD disks, the identification of each SSD disk type to be tested may be added in step s140, and the script file is generated according to each type of SSD disk and the corresponding disk mounting position, which is not limited in this embodiment.
It should be noted that, the implementation of the steps s140 to s150 needs to be based on the implementation of the steps s110 to s130, that is, based on the common test script set generated by the steps s110 to s130, but the steps s110 to s130 need not to be executed each time the steps s140 to s150 are executed, and after the common test script set is generated by executing the steps s110 to s130, the common test script set may be directly called to repeatedly execute the steps s140 to s150, so as to implement the repeat test.
Based on the introduction, the automatic testing method for the SSD hard disk provided in this embodiment combines the testing platforms for the belmr and the harding, and completes the automatic tests for the multiple types of disks of different types with one set of codes, because the same and similar scripts in the two items account for more than 80%, the total number of the scripts to be maintained after combination is greatly reduced, and the platform maintenance efficiency can be significantly improved.
Referring to fig. 2, fig. 2 is a block diagram of an SSD hard disk automatic test device provided in this embodiment; the apparatus may include: a script distinguishing unit 210, a first processing unit 220, a second processing unit 230, a type determining unit 240, and a disk testing unit 250. The automatic testing device for the SSD provided by the embodiment can be contrasted with the automatic testing method for the SSD.
The script distinguishing unit 210 is mainly configured to determine the same script and an exclusive script in the belmr script group and the harding script group;
the first processing unit 220 is mainly used for merging the same scripts and adding the merged scripts to the common test script group; wherein, the common test script group is a preset test script group for testing belmar or harding;
the second processing unit 230 is mainly configured to add the dedicated script with the corresponding item identifier and then add the dedicated script to the common script group;
the type determining unit 240 is mainly used for determining the type of the SSD disk to be tested when the test instruction is received;
the disk test unit 250 is mainly used for calling scripts in the common script group, which are matched with the types, to test the SSD disk to be tested.
The automatic testing device for the SSD provided by the embodiment can obviously improve the platform maintenance efficiency.
The embodiment provides an automatic test equipment for an SSD, comprising: a memory and a processor.
Wherein, the memory is used for storing programs;
the processor is configured to implement the steps of the SSD hard disk automated testing method described in the above embodiments when executing the program, and specifically refer to the description of the SSD hard disk automated testing method.
Referring to fig. 3, a schematic structural diagram of an SSD hard disk automated testing device provided in this embodiment is shown, where the SSD hard disk automated testing device may generate relatively large differences due to different configurations or performances, and may include one or more processors (CPUs) 322 (e.g., one or more processors) and a memory 332, and one or more storage media 330 (e.g., one or more mass storage devices) storing an application 342 or data 344. Memory 332 and storage media 330 may be, among other things, transient storage or persistent storage. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instructions operating on a data processing device. Still further, the central processor 322 may be configured to communicate with the storage medium 330, and execute a series of instruction operations in the storage medium 330 on the SSD hard disk automation test device 301.
SSD hard disk automated test equipment 301 may also include one or more power supplies 326, one or more wired or wireless network interfaces 350, one or more input-output interfaces 358, and/or one or more operating systems 341, such as Windows Server, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, and so forth.
The steps in the SSD hard disk automated testing method described in fig. 1 above may be implemented by the structure of the SSD hard disk automated testing apparatus described in this embodiment.
The present embodiment discloses a readable storage medium, on which a program is stored, and the program, when executed by a processor, implements the steps of the SSD hard disk automated testing method described in the above embodiments, which may be referred to in the description of the SSD hard disk automated testing method in the above embodiments.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and various other readable storage media capable of storing program codes.
The embodiments are described in a progressive manner in the specification, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. The device disclosed by the embodiment corresponds to the method disclosed by the embodiment, so that the description is simple, and the relevant points can be referred to the method part for description.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in Random Access Memory (RAM), memory, Read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
The method, the device, the equipment and the readable storage medium for automatically testing the SSD hard disk provided by the present application are described in detail above. The principles and embodiments of the present application are explained herein using specific examples, which are provided only to help understand the method and the core idea of the present application. It should be noted that, for those skilled in the art, it is possible to make several improvements and modifications to the present application without departing from the principle of the present application, and such improvements and modifications also fall within the scope of the claims of the present application.
Claims (10)
1. An automatic testing method for an SSD is characterized by comprising the following steps:
determining the same scripts and special scripts in a belmr script group and a harding script group;
merging the same scripts and then adding the merged scripts to a common test script group; the common test script group is a preset test script group for testing belmar or harding;
adding the exclusive script to the common script group after adding the corresponding project identifier;
when a test instruction is received, determining the type of the SSD to be tested;
and calling the script matched with the type in the common script group to test the SSD disk to be tested.
2. The automated testing method of the SSD hard disk of claim 1, wherein merging the same script and adding to a common test script group comprises:
judging whether the names of the same scripts in the Belmar script group and the harding script group are the same or not;
if not, unifying the naming rule and then adding a script to the common test script group;
and if so, adding a script to the common test script group.
3. The automated testing method for the SSD hard disk of claim 1, wherein adding the dedicated script to the common script group after adding the corresponding item identifier comprises:
and adding a corresponding project prefix in front of the original script name of the exclusive script, and adding the exclusive script added with the project prefix to the common script group.
4. The automated testing method of the SSD hard disk of claim 1, wherein determining the type of the SSD disk to be tested when the test instruction is received comprises:
when a test instruction is received, determining an lspci value of the SSD to be tested;
the type of disc is determined from the lspci value.
5. The automated testing method of the SSD hard disk of claim 1, wherein invoking the script in the common script group that matches the type to test the SSD disk to be tested comprises:
traversing each script in the common script group, and screening out scripts without item identifications and scripts matched with the item identifications as test scripts;
and calling the test script to test the SSD disk to be tested.
6. The automatic testing method for the SSD hard disk of any one of claims 1 to 5, wherein calling the script in the common script group, which is matched with the type, to test the SSD disk to be tested comprises:
determining the drive letter of each SSD to be tested;
calling the script matched with the type to generate a test file corresponding to each SSD to be tested, and issuing the test file to the corresponding SSD to be tested according to the disc identifier;
and calling each test file to test the corresponding SSD disk to be tested.
7. The automatic testing method of the SSD hard disk of claim 6, wherein invoking the script of type matching to generate a test file corresponding to each SSD disk to be tested comprises:
and adjusting the nvnum parameter in the common function common.sh in the script with the matched type to the parameter value corresponding to each SSD disk to be tested, and generating a test file corresponding to each SSD disk to be tested.
8. An automatic testing arrangement of SSD hard disk characterized in that includes:
the script distinguishing unit is used for determining the same scripts and exclusive scripts in the belmr script group and the harding script group;
the first processing unit is used for merging the same scripts and then adding the merged scripts to a common test script group; the common test script group is a preset test script group for testing belmar or harding;
the second processing unit is used for adding the exclusive script to the common script group after adding the corresponding project identifier;
the type determining unit is used for determining the type of the SSD disk to be tested when the test instruction is received;
and the disk testing unit is used for calling the script matched with the type in the common script group to test the SSD disk to be tested.
9. An automatic test equipment for SSD hard disk, comprising:
a memory for storing a program;
a processor for implementing the steps of the SSD hard disk automated testing method of any of claims 1 to 7 when executing the program.
10. A readable storage medium, characterized in that the readable storage medium has stored thereon a program which, when executed by a processor, implements the steps of the SSD hard disk automated test method according to any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911318460.8A CN111104274B (en) | 2019-12-19 | 2019-12-19 | SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911318460.8A CN111104274B (en) | 2019-12-19 | 2019-12-19 | SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111104274A true CN111104274A (en) | 2020-05-05 |
| CN111104274B CN111104274B (en) | 2023-07-14 |
Family
ID=70422895
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911318460.8A Active CN111104274B (en) | 2019-12-19 | 2019-12-19 | SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111104274B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060136579A1 (en) * | 2004-12-21 | 2006-06-22 | International Business Machines Corporation | Method of executing test scripts against multiple systems |
| US20150100830A1 (en) * | 2013-10-04 | 2015-04-09 | Unisys Corporation | Method and system for selecting and executing test scripts |
| CN105161132A (en) * | 2015-08-27 | 2015-12-16 | 浪潮电子信息产业股份有限公司 | NVMe SSD read-only protection method based on FPGA |
| CN107391333A (en) * | 2017-08-14 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of OSD disk failures method of testing and system |
| CN108052451A (en) * | 2017-12-26 | 2018-05-18 | 网易（杭州）网络有限公司 | Test method, system, test server, test terminal and storage medium |
| CN109815123A (en) * | 2018-12-15 | 2019-05-28 | 中国平安人寿保险股份有限公司 | Interface testing case script classification method, device, electronic equipment and medium |
-
2019
- 2019-12-19 CN CN201911318460.8A patent/CN111104274B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060136579A1 (en) * | 2004-12-21 | 2006-06-22 | International Business Machines Corporation | Method of executing test scripts against multiple systems |
| US20150100830A1 (en) * | 2013-10-04 | 2015-04-09 | Unisys Corporation | Method and system for selecting and executing test scripts |
| CN105161132A (en) * | 2015-08-27 | 2015-12-16 | 浪潮电子信息产业股份有限公司 | NVMe SSD read-only protection method based on FPGA |
| CN107391333A (en) * | 2017-08-14 | 2017-11-24 | 郑州云海信息技术有限公司 | A kind of OSD disk failures method of testing and system |
| CN108052451A (en) * | 2017-12-26 | 2018-05-18 | 网易（杭州）网络有限公司 | Test method, system, test server, test terminal and storage medium |
| CN109815123A (en) * | 2018-12-15 | 2019-05-28 | 中国平安人寿保险股份有限公司 | Interface testing case script classification method, device, electronic equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111104274B (en) | 2023-07-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110557299A (en) | network transmission function batch test method, system, terminal and storage medium | |
| CN105487952A (en) | PCIE-SSD automatic test method based on FIO | |
| CN111124911A (en) | Automatic testing method, device, equipment and readable storage medium | |
| CN112416803A (en) | Automatic testing method and device | |
| US11928461B2 (en) | Software utilization optimization in managed networks | |
| CN111104274A (en) | Automatic testing method, device and equipment for SSD (solid State disk) and readable storage medium | |
| CN111026656A (en) | Automatic testing system, method, equipment and storage medium for distributed storage | |
| CN110968351A (en) | BIOS configuration method and device | |
| CN115454851A (en) | Interface regression testing method and device, storage medium and electronic device | |
| CN115309658A (en) | Test data derivation method, device, equipment and storage medium | |
| CN111400117B (en) | Method for automatically testing Ceph cluster | |
| CN112269733B (en) | Automatic aging test method for server and storage medium | |
| CN111159714B (en) | Method and system for verifying credibility of main body in operation in access control | |
| CN113031970A (en) | Automatic installation and deployment method and system | |
| CN113849484A (en) | Big data component upgrading method and device, electronic equipment and storage medium | |
| CN108769246B (en) | NFS sharing maximization test method and system | |
| CN114401032B (en) | Testing method and system for satellite communication comprehensive tester | |
| WO2018111399A1 (en) | Automated server deployment platform | |
| CN109005021B (en) | Host time management method and related device in virtualization environment | |
| CN107943942B (en) | Event-driven multi-turn file acquisition system | |
| CN113836001A (en) | Code detection method, device and storage medium | |
| CN110825616A (en) | Automatic test system for mobile terminal equipment in local area network | |
| JP2016177634A (en) | Flow generation method and flow generation program | |
| CN115756517A (en) | Method, device and medium for burning SSD (solid State disk) | |
| CN117632378A (en) | Performance test management method and system for virtualized CPU |
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 |