CN111104274B - SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium - Google Patents

SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium Download PDF

Info

Publication number
CN111104274B
CN111104274B CN201911318460.8A CN201911318460A CN111104274B CN 111104274 B CN111104274 B CN 111104274B CN 201911318460 A CN201911318460 A CN 201911318460A CN 111104274 B CN111104274 B CN 111104274B
Authority
CN
China
Prior art keywords
script
test
ssd
common
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.)
Active
Application number
CN201911318460.8A
Other languages
Chinese (zh)
Other versions
CN111104274A (en
Inventor
靳嘉晖
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Inspur Smart Computing Technology Co Ltd
Original Assignee
Guangdong Inspur Big Data Research Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangdong Inspur Big Data Research Co Ltd filed Critical Guangdong Inspur Big Data Research Co Ltd
Priority to CN201911318460.8A priority Critical patent/CN111104274B/en
Publication of CN111104274A publication Critical patent/CN111104274A/en
Application granted granted Critical
Publication of CN111104274B publication Critical patent/CN111104274B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application discloses an SSD hard disk automatic test method, which comprises the following steps: determining the same scripts and exclusive scripts in the belmar script group and the harding script group; the same scripts are added to the common test script group after being combined; adding the corresponding item identifier to the exclusive script and then adding the exclusive script to the common script group; when a test instruction is received, determining the type of the SSD disk to be tested; and calling a script matched with the type in the common script group to test the SSD to be tested. According to the method, the testing platforms aiming at the belmar and the harding are combined, one set of codes is used for completing the automatic testing of different types aiming at the multi-type disc, the total number of scripts to be maintained after the combination is greatly reduced, and the platform maintenance efficiency can be remarkably improved. The application also provides an SSD hard disk automatic test device, equipment and a readable storage medium, which have the beneficial effects.

Description

SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium
Technical Field
The present disclosure relates to the field of hard disk testing technologies, and in particular, to an automatic testing method, apparatus, and device for an SSD hard disk, and a readable storage medium.
Background
Rand_test_day is a collective generic term of an automatic test script for an SSD hard disk, wherein various scenes such as reading and writing, formatting and various operations of a mixed scene are included, and the purpose of comprehensively and systematically testing the SSD is achieved by executing the random test of the script in different sequences.
Rand_test_day mainly contains two items of test, belmar, harding respectively. The two projects respectively contain more than 200 scripts, and the proportion of the same and similar scripts in the two projects is more than 80 percent, for example, when the scripts are changed or the common scripts are added, the two platforms are maintained, so that the time is consumed, errors are easy to occur, and the platform maintenance efficiency is lower.
Disclosure of Invention
The purpose of the application is to provide an SSD hard disk automatic test method, which can obviously improve the platform maintenance efficiency; another object of the present application is to provide an SSD hard disk automation test device, apparatus, and a readable storage medium.
In order to solve the above technical problems, the present application provides an automatic testing method for SSD hard disk, including:
determining the same scripts and exclusive scripts in the belmar script group and the harding script group;
merging the same scripts and adding the same scripts into a common test script group; the common test script set is a preset test script set for testing belmar or harding;
adding the corresponding item identification to the exclusive script and then adding the exclusive script to the common script group;
when a test instruction is received, determining the type of the SSD disk to be tested;
and calling the scripts matched with the type in the common script group to test the SSD disk to be tested.
Optionally, the same script is added to a common test script set after being combined, including:
judging whether names of the same scripts in the belmar script group and the harding script group are the same or not;
if not, adding a script into the common test script group after unifying the naming rules;
if yes, adding a script into the common test script set.
Optionally, adding the dedicated script to the common script group after adding the corresponding item identifier includes:
and adding a corresponding item prefix before the original script name of the exclusive script, and adding the exclusive script added with the item prefix into the common script group.
Optionally, when a test instruction is received, determining the type of the SSD disk to be tested includes:
when a test instruction is received, determining a lspci value of an SSD disk to be tested;
and determining the type of the disc according to the lspci value.
Optionally, invoking the script matched with the type in the common script set to test the SSD disk to be tested, including:
traversing each script in the common script group, and screening out scripts without item identification and scripts matched with the item identification as test scripts;
and calling the test script to test the SSD disk to be tested.
Optionally, invoking the script matched with the type in the common script set to test the SSD disk to be tested, including:
determining the drive letter of each SSD disk to be tested;
calling the script with the matched type to generate a test file corresponding to each SSD disk to be tested, and issuing the test file to the corresponding SSD disk to be tested according to the drive letter;
and calling each test file to test the corresponding SSD disk to be tested.
Optionally, calling the script with the matched type to generate a test file corresponding to each SSD disc to be tested, including:
and adjusting nvnum parameters in a common function common.sh in the type-matched script to parameter values corresponding to all SSD disks to be tested, and generating test files corresponding to all SSD disks to be tested.
The application discloses SSD hard disk automation testing device includes:
the script distinguishing unit is used for determining the same scripts and exclusive scripts in the bearing script group and the harding script group;
the first processing unit is used for adding the same script into a common test script group after merging the same script; the common test script set is a preset test script set for testing belmar or harding;
the second processing unit is used for adding the special script with the corresponding item identifier and then adding the special script to the common script group;
the type determining unit is used for determining the type of the SSD disc to be tested when a test instruction is received;
and the disk test unit is used for calling the scripts matched with the type in the common script group to test the SSD disk to be tested.
The application discloses SSD hard disk automation test equipment includes:
a memory for storing a program;
and the processor is used for realizing the steps of the SSD hard disk automatic test method when executing the program.
The application discloses a readable storage medium, wherein a program is stored on the readable storage medium, and the program realizes the steps of the SSD hard disk automatic test method when being executed by a processor.
The SSD hard disk automatic test method provided by the application comprises the following steps: determining the same scripts and exclusive scripts in the belmar script group and the harding script group; the same scripts are added to the common test script group after being combined; the common test script set is a preset test script set for testing belmar or harding; adding the corresponding item identifier to the exclusive script and then adding the exclusive script to the common script group; when a test instruction is received, determining the type of the SSD disk to be tested; and calling a script matched with the type in the common script group to test the SSD to be tested. According to the method, the testing platforms for the belmar and the harding are combined, one set of codes is used for completing the automatic testing of different types for the multi-type disk, and as the same and similar scripts in the two projects account for more than 80%, the total number of scripts to be maintained after combination is greatly reduced, and the platform maintenance efficiency can be remarkably improved.
The application also provides an automatic SSD hard disk testing device, an automatic SSD hard disk testing device and an automatic SSD hard disk testing device, and a readable storage medium, which have the beneficial effects and are not described in detail herein.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only embodiments of the present application, and that other drawings may be obtained according to the provided drawings without inventive effort to a person skilled in the art.
Fig. 1 is a flowchart of an SSD hard disk automation test method provided in an embodiment of the application;
fig. 2 is a block diagram of an SSD hard disk automation test device according to an embodiment of the disclosure;
fig. 3 is a schematic structural diagram of an SSD hard disk automation test device according to an embodiment of the disclosure.
Detailed Description
The core of the application is to provide an SSD hard disk automatic test method, which can remarkably improve script maintenance efficiency of a test platform; another core of the present application is to provide an SSD hard disk automation test device, apparatus, and a readable storage medium.
For the purposes of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of 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 apparent that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure.
Referring to fig. 1, fig. 1 is a flowchart of an SSD hard disk automation test method according to the present embodiment, the method mainly includes:
step s110, determining the same scripts and proprietary scripts in the belmar script group and the harding script group;
the same script refers to a script with the same realizing purpose, realizing mode and realizing effect, and some scripts meeting the conditions can have a little conceivable transformation on some sentences and can be classified as the same script; accordingly, a proprietary script refers to a script that is specific for implementing an SSD disk test of the type to which it belongs, for which the same script does not exist in another script group.
And determining the same scripts and exclusive scripts in the belmar script group and the harding script group so as to combine the belmar script group and the harding script group and facilitate maintenance of the rand_test_day platform.
Step s120, merging the same scripts and adding the same scripts into a common test script group; the common test script set is a preset test script set for testing belmar or harding;
for the same script for both items belmar, harding, a merge process is required, i.e. only one copy is reserved for call at belmar and harding, respectively.
In this embodiment, a specific script merging manner is not limited. Optionally, one implementation of script merging is as follows: judging whether names of the same scripts in the beta script group and the harding script group are the same or not; if not, adding a script into the common test script group after unifying the naming rules; if yes, adding a script into the common test script set. For example, if the r1 script in the belmar script group and the r1 script in the harding script group are the same script, only one part of r1 script is added to the common test script group; and 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 uniformly named as s1 script, and one part of s1 script is added into the common test script group.
Since script is generally called by identifying script names when the script is called, in this embodiment, it is proposed to add a script to a common test script group after the script names are combined, so as to facilitate identification of script types in the calling process. When the names of the two different scripts do not need to be unified, the specific unified mode is not limited in this embodiment, one of the two names may be selected for unification, and the names other than the two names may also be selected for unification, which may be set according to the actual use situation, and will not be described herein.
Step 130, adding the corresponding item identifier to the exclusive script and then adding the exclusive script to the common script group;
the item identifier refers to a test object identifier of the script, that is, whether the script is used for testing the belmar or used for testing the harding can be distinguished according to the item identifier; since script is generally called by identifying script names when the script is called, in order to facilitate quick identification and distinction of script types, in this embodiment, a manner is provided in which an adapted item (i.e. a disc type) is distinguished by adding a corresponding identifier to the script name of the proprietary script to realize item type distinction of the proprietary script, and specifically, an implementation manner is as follows: and adding the corresponding item prefix before the original script name of the exclusive script, and adding the exclusive script added with the item prefix into the common script group. The proprietary scripts for the belmar, harding items in this implementation are named separately, e.g., the belmar item naming convention is belmar_xxxx and the harding item naming convention is harding_xxxx. In this embodiment, the foregoing implementation manner is merely taken as an example, and other implementation manners based on the present application may refer to the description of this embodiment, which is not repeated herein.
It should be noted that, the execution order of step s120 and step s130 is not limited, and may be executed in parallel, or may be executed sequentially, and when executed sequentially, step s120 may be executed first, or step s130 may be executed first, and in fig. 1, only the parallel execution is described as an example, and other execution orders may be described with reference to this embodiment.
Step s140, when a test instruction is received, determining the type of the SSD disk to be tested;
and adding a judging rule into the test script to determine the type of the SSD disk to be tested currently so as to call the script with the matched type for testing, thereby realizing the automatic test of multi-disk adaptation. The manner of determining the disc type in this embodiment is not limited, and optionally, one implementation manner is as follows: when a test instruction is received, determining a lspci value of an SSD disk to be tested; the type of disc is determined from the lspci value. A determination is made for a different type of SSD device (belmar, harding) using a lsPCi, with a belmar lsPCi value of 8607 and a harding lsPCi value of 8632. The lspci value belongs to the inherent attribute of the SSD disk, and the error can be avoided by distinguishing the disk types through the lspci value, so that the efficiency and the accuracy of type determination are improved. In this embodiment, the description is given by taking the above implementation manner as an example, and other disc type determining manners may refer to the description of this embodiment, which is not repeated herein.
And step s150, calling a script matched with the type in the common script group to test the SSD to be tested.
The common script group mainly comprises two scripts, namely a script without item identification (namely a multi-type disc common test script) and a script with item identification (namely a special script under various types of discs), wherein the script with item identification mainly comprises a belmar type script and a harding type script, a process of calling the script matched with the type in the common script group to test the SSD disc to be tested is that selecting the script matched with the type of the current type disc in the common script group (comprising the common script and the special script) to test the disc, and the process can be realized by directly screening out the common test script and the script with the item identification corresponding to the current disc type, or by eliminating the script with the item identification not corresponding to the current disc type, and is not limited. Optionally, one implementation is as follows: traversing each script in the common script group, screening out scripts without item identification and scripts matched with the item identification, and taking the scripts and the scripts as test scripts; and calling a test script to test the SSD to be tested. The interference of the non-matching type script can be avoided in the mode, and the screening efficiency is improved.
In addition, in this embodiment, the description is mainly made with the case that the SSD disk to be tested is one, but at present, the script only supports one disk running 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 is generated, and in order to avoid such a resource waste, the efficiency and the utilization rate of the server and the PC are improved, in this embodiment, a method capable of testing multiple SSD disks on the same machine is further provided. Accordingly, the process of calling the script matched with the type in the common script group to test the SSD disk to be tested specifically comprises the following steps:
(1) Determining the drive letter of each SSD drive to be tested;
(2) Calling scripts with 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 drive letter;
the process of generating the test file corresponding to each SSD disc to be tested by calling the script with the matched type may specifically be: and adjusting nvnum parameters in a common function common. Sh in the script with the matched types to parameter values corresponding to the SSD disks to be tested, and generating test files corresponding to the SSD disks to be tested.
And adding nvnum parameters in a common function common, and taking the nvnum parameters from nvme devices in all scripts for distinguishing different nvme devices. For example, the SSD disc to be tested includes disc 1 and disc 2, which are respectively installed in slot 1 and slot 2, and the nvnum parameter of disc 1 is set to 1, and the nvnum parameter of disc 2 is set to 2, then the nvnum parameter in the common function common.sh in the test file for disc 1 is adjusted to 1, then the test file is the test file for disc 1, and the nvnum parameter in the common function common.sh in the test file for disc 2 is adjusted to 2, then the test file is the test file for disc 2, and then the simultaneous test of disc 1 and disc 2 can be realized.
Of course, other types of device parameters may be added to other functions to indicate different slot positions or different devices, which are not limited herein.
(3) And calling each test file to test the corresponding SSD disk to be tested.
The above manner provided by the embodiment can realize testing on the same server or pc machine aiming at a plurality of nvme devices, realize simultaneous adaptation testing of multiple discs, promote the resource utilization of a testing host, and promote the testing efficiency.
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 overall test files are approximately the same, and the test files corresponding to the SSD disks to be tested only need to be adjusted by calling the script with the matched types to generate the test files corresponding to the SSD disks to be tested, so that the test files point to the issued SSD disks to be tested. Of course, in order to implement testing of multiple types of SSD disks of different types, in step s140, identification of each type of SSD disk to be tested may be added, and generation of script files may be performed according to each type of SSD disk and the corresponding disk mounting position, which is not limited in this embodiment.
In addition, 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, the common test script set generated based on the steps s110 to s130, but the steps s110 to s130 need not be executed each time before the steps s140 to s150 are executed, and after the steps s110 to s130 are executed to generate the common test script set, the common test script set may be directly called to repeatedly execute the steps s140 to s150, so as to implement the repeated test.
Based on the description, according to the SSD hard disk automatic test method provided by the embodiment, the test platforms for belmar and harding are combined, and one set of codes is used for completing the automatic test of different types for multiple types of disks, and as the same and similar scripts in the two projects account for more than 80%, the total number of scripts to be maintained after combination is greatly reduced, and the platform maintenance efficiency can be remarkably improved.
Referring to fig. 2, fig. 2 is a block diagram of an SSD hard disk automation test device according to the embodiment; the apparatus may include: a script differentiating 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 SSD hard disk testing device provided by the embodiment can be mutually compared with the automatic SSD hard disk testing method.
The script differentiating unit 210 is mainly used for determining the same script and the exclusive script in the belmar script group and the harding script group;
the first processing unit 220 is mainly configured to combine the same scripts and add the combined scripts to the common test script set; the common test script set is a preset test script set 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 item identifier to the common script group;
the type determining unit 240 is mainly configured to determine a type of the SSD disk to be tested when receiving the test instruction;
the disk test unit 250 is mainly used for calling scripts matched with the type in the common script set to test the SSD disk to be tested.
The SSD hard disk automatic test device provided by the embodiment can obviously improve the platform maintenance efficiency.
The embodiment provides an automatic testing device for SSD hard disk, comprising: a memory and a processor.
Wherein the memory is used for storing programs;
the steps of the SSD hard disk automation test method described in the above embodiment may be specifically referred to the description of the SSD hard disk automation test method described in the above embodiment when the processor is used to execute the program.
Referring to fig. 3, a schematic structural diagram of an SSD hard disk automation test device according to the present embodiment, which may generate relatively large differences due to different configurations or performances, may include one or more processors (central processing units, CPU) 322 (e.g., one or more processors) and a memory 332, one or more storage media 330 (e.g., one or more mass storage devices) storing application programs 342 or data 344. Wherein the memory 332 and the storage medium 330 may be transitory or persistent. The program stored on the storage medium 330 may include one or more modules (not shown), each of which may include a series of instruction operations in the data processing apparatus. Still further, the central processor 322 may be configured to communicate with the storage medium 330 to execute a series of instruction operations in the storage medium 330 on the SSD hard disk automated test equipment 301.
SSD hard disk automated test equipment 301 can 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 ServerTM, mac OS XTM, unixTM, linuxTM, freeBSDTM, and the like.
The steps in the SSD hard disk automation test method described in fig. 1 above may be implemented by the structure of the SSD hard disk automation test apparatus described in the present embodiment.
The embodiment discloses a readable storage medium, on which a program is stored, and the steps of the automatic testing method for SSD hard disks described in the above embodiment are implemented when the program is executed by a processor.
The readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, and the like.
In the description, each embodiment is described in a progressive manner, and each embodiment is mainly described by the differences from other embodiments, so that the same similar parts among the embodiments are mutually referred. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant points refer to the description of the method section.
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 elements and steps are described above generally in terms of functionality in order to clearly illustrate the 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 solution. 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. The software modules may be disposed 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 application are described in detail. Specific examples are set forth herein to illustrate the principles and embodiments of the present application, and the description of the examples above is only intended to assist in understanding the methods of the present application and their core ideas. It should be noted that it would be obvious to those skilled in the art that various improvements and modifications can be made to the present application without departing from the principles of the present application, and such improvements and modifications fall within the scope of the claims of the present application.

Claims (8)

1. An automatic testing method for SSD hard disk is characterized by comprising the following steps:
determining the same scripts and exclusive scripts in the belmar script group and the harding script group;
merging the same scripts and adding the same scripts into a common test script group; the common test script set is a preset test script set for testing belmar or harding;
adding the corresponding item identification to the exclusive script and then adding the exclusive script to a common script group;
when a test instruction is received, determining the type of the SSD disk to be tested;
determining the drive letter of each SSD disk to be tested;
calling the script with the matched type to generate a test file corresponding to each SSD disk to be tested, and issuing the test file to the corresponding SSD disk to be tested according to the drive letter;
and adjusting nvnum parameters in a common function common.sh in the type-matched script to parameter values corresponding to all SSD disks to be tested, and generating test files corresponding to all SSD disks to be tested.
2. The SSD hard disk automated test method of claim 1, wherein merging the same script and adding it to a common test script group comprises:
judging whether names of the same scripts in the belmar script group and the harding script group are the same or not;
if not, adding a script into the common test script group after unifying the naming rules;
if yes, adding a script into the common test script set.
3. The SSD hard disk automated test method of claim 1, wherein adding the dedicated script to the common script group after adding the corresponding item identifier, comprises:
and adding a corresponding item prefix before the original script name of the exclusive script, and adding the exclusive script added with the item prefix into the common script group.
4. The SSD hard disk automated test method of claim 1, wherein determining the type of SSD disk to be tested when the test instruction is received comprises:
when a test instruction is received, determining a lspci value of an SSD disk to be tested;
and determining the type of the disc according to the lspci value.
5. The method of automated SSD hard disk testing of claim 1, wherein invoking the script of the common set of scripts that matches the type to test the SSD disk under test comprises:
traversing each script in the common script group, and screening out scripts without item identification and scripts matched with the item identification as test scripts;
and calling the test script to test the SSD disk to be tested.
6. An automatic testing device for an SSD hard disk, comprising:
the script distinguishing unit is used for determining the same scripts and exclusive scripts in the bearing script group and the harding script group;
the first processing unit is used for adding the same script into a common test script group after merging the same script; the common test script set is a preset test script set for testing belmar or harding;
the second processing unit is used for adding the corresponding item identifier to the exclusive script and then adding the exclusive script to a common script group;
the type determining unit is used for determining the type of the SSD disc to be tested when a test instruction is received;
a disk test unit, configured to determine a disk identifier of each SSD disk to be tested; calling the script with the matched type to generate a test file corresponding to each SSD disk to be tested, and issuing the test file to the corresponding SSD disk to be tested according to the drive letter; and adjusting nvnum parameters in a common function common.sh in the type-matched script to parameter values corresponding to all SSD disks to be tested, and generating test files corresponding to all SSD disks to be tested.
7. An SSD hard disk automated test equipment, comprising:
a memory for storing a program;
a processor for implementing the steps of the SSD hard disk automation test method according to any one of claims 1 to 5 when executing the program.
8. A readable storage medium, wherein a program is stored on the readable storage medium, which when executed by a processor, implements the steps of the SSD hard disk automation test method of any one of claims 1 to 5.
CN201911318460.8A 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 Active CN111104274B (en)

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 CN111104274A (en) 2020-05-05
CN111104274B true 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 (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7444397B2 (en) * 2004-12-21 2008-10-28 International Business Machines Corporation Method of executing test scripts against multiple systems
IN2013DE02948A (en) * 2013-10-04 2015-04-10 Unisys Corp
CN109815123A (en) * 2018-12-15 2019-05-28 中国平安人寿保险股份有限公司 Interface testing case script classification method, device, electronic equipment and medium

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
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

Also Published As

Publication number Publication date
CN111104274A (en) 2020-05-05

Similar Documents

Publication Publication Date Title
JP6045134B2 (en) Parallel workload simulation for application performance testing
CN111078551B (en) Full-link testing method, device and system and computer readable storage medium
CN110557299A (en) network transmission function batch test method, system, terminal and storage medium
CN106201857B (en) The choosing method and device of test case
CN110377519B (en) Performance capacity test method, device and equipment of big data system and storage medium
CN111090401B (en) Storage device performance prediction method and device
CN111104274B (en) SSD hard disk automatic test method, SSD hard disk automatic test device, SSD hard disk automatic test equipment and readable storage medium
CN110795308A (en) Server inspection method, device, equipment and storage medium
CN115309658A (en) Test data derivation method, device, equipment and storage medium
CN115509931A (en) System-based performance test method and device, electronic equipment and storage medium
CN113849484A (en) Big data component upgrading method and device, electronic equipment and storage medium
CN114625570A (en) Database backup scheduling method and device
CN111159988A (en) Model processing method and device, computer equipment and storage medium
CN110736920A (en) card testing method and system based on engineering management test script
CN112306850A (en) Test case generation method and device and storage medium
CN113282304B (en) System for identifying virtual machine based on app installation list
US20180176291A1 (en) Automated server deployment platform
CN113760489B (en) Resource allocation method and device
CN112035482B (en) Service table partitioning method and device
CN114401032B (en) Testing method and system for satellite communication comprehensive tester
CN111078543B (en) System dynamic test method and test device
CN117632378B (en) Performance test management method and system for virtualized CPU
CN117573461A (en) Method and system for verifying credit-fit performance of power information system
CN107423316B (en) A kind of big data processing method, apparatus and system
CN114064318A (en) Interface message processing method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant