CN101159775A - Hardware module testing system and method - Google Patents
Hardware module testing system and method Download PDFInfo
- Publication number
- CN101159775A CN101159775A CNA2007101818188A CN200710181818A CN101159775A CN 101159775 A CN101159775 A CN 101159775A CN A2007101818188 A CNA2007101818188 A CN A2007101818188A CN 200710181818 A CN200710181818 A CN 200710181818A CN 101159775 A CN101159775 A CN 101159775A
- Authority
- CN
- China
- Prior art keywords
- hardware module
- tested
- hardware
- test
- version information
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a hardware module test system and a method. The hardware module test method comprises following steps: S202, storing the hardware version information of the hardware module to be tested in a hardware version base; S204, storing the test term of the hardware module to be tested in a test term base; S206, storing the mapping relation between the hardware version information and the test item of the hardware module to be tested in a mapping relation base; and S208, calling a test execution unit of the hardware module to be tested stored in an execution unit base, searching the test item corresponding to the hardware version information of the hardware module to be tested according to the mapping relation between the hardware version information and the test item of the hardware module to be tested, and testing the hardware module to be tested by using the searched test item. The invention can efficiently achieve the test of the hardware module to be tested.
Description
Technical field
The present invention relates to the communications field, relate more specifically to a kind of hardware module testing system and method.
Background technology
Along with the continuous progress of society, the improving constantly of people's quality of life, people are also more and more higher to the requirement of various products, and product quality also becomes the standard that people weigh quality of life gradually.As the research and development of product and manufacturing enterprise all the time the quality of product as " Business survival this ".
How to guarantee product quality better, earlier find the product problem, the test link is had higher requirement.Reach comprehensively careful test exactly, need the overall understanding product information, be included in hardware designs, finish function, application scenario, environment for use etc.
And as the existence basis of product, the test of hardware components then is the key link and the step of product quality.The difference of product type makes the hardware of hardware module form and finish function and there are differences.
In order to save the unification of cost, realization hardware platform, the hardware module hardware and software platform has obtained continuous development and popularization, the differentiation of hardware module no longer only has been confined to hardware configuration external form and PCB batch, but has expanded to hardware module logic realization, hardware module material list, hardware module ID sign, hardware CPU model etc.That is, same hardware module, different logic realization, the configuration of different material lists will cause same hardware module to finish different functions.
In present method of testing design, often consider that the test that constantly reaches different hardware by the simple compatibility of software covers.Perhaps 2 to 3 different hardware modules can reach compatible by the mode of software, can 5 to 8 different hardware modules or more hardware module also satisfy test request by the simple software compatibility so? compatibility is complicated more, no matter is all bigger problem can occur aspect the stability in test, the reliability of test, the maintainability of code or the operability of carrying out.When make compatibility, when do not make compatibility, carry out many-sided consideration.
In addition, because the difference of hardware module is finished the difference on the function, cause hardware module test item difference, test result is fitly preserved, conveniently inquiring about again and add up simultaneously also is that present method of testing needs improved aspect.
Summary of the invention
One or more problems in view of the above the invention provides a kind of new hardware module testing system and method.
Hardware module testing system according to the present invention comprises: the hardware version storehouse is used to store the hardware version information of hardware module to be tested; The test item storehouse is used to store the test item of hardware module to be tested; The mapping relations storehouse is used to store the mapping relations between the test item of the hardware version information of hardware module to be tested and hardware module to be tested; And performance element storehouse, be used to store the test execution unit of hardware module to be tested, wherein, the test execution unit is used for according to the mapping relations between the test item of the hardware version information of hardware module to be tested and hardware module to be tested, find out the test item corresponding, and utilize the test item of being found out to treat the testing hardware module and test with the hardware version information of hardware module to be tested.
Wherein, the hardware version information of hardware module to be tested has uniqueness.Hardware version information comprises at least a in the following information: EPLD (Electrically ProgrammableLogic Device) version, material odd numbers, PCB (Printed Circuit Board) version, CPU (central processing unit) model, BOOT (startup boot) version.Be one to one or the relation of one-to-many between the hardware version information of hardware module to be tested and the test execution unit of hardware module to be tested.
Hardware module testing method according to the present invention may further comprise the steps: the hardware version information of storage hardware module to be tested in the hardware version storehouse; The test item of storage hardware module to be tested in the test item storehouse; Mapping relations in the mapping relations storehouse between the test item of the hardware version information of storage hardware module to be tested and hardware module to be tested; And the test execution unit that calls the hardware module to be tested of storing in the performance element storehouse, according to the mapping relations between the test item of the hardware version information of hardware module to be tested and hardware module to be tested, find out the test item corresponding, and utilize the test item of being found out to treat the testing hardware module and test with the hardware version information of hardware module to be tested.
Wherein, the hardware version information of hardware module to be tested has uniqueness.Hardware version information comprises at least a in the following information: EPLD version, material odd numbers, PCB version, CPU model, BOOT version.Be one to one or the relation of one-to-many between the hardware version information of hardware module to be tested and the test execution unit of hardware module to be tested.
By the present invention, can realize treating the test of testing hardware module efficiently.
Description of drawings
Accompanying drawing described herein is used to provide further understanding of the present invention, constitutes the application's a part, and illustrative examples of the present invention and explanation thereof are used to explain the present invention, do not constitute improper qualification of the present invention.In the accompanying drawings:
Fig. 1 is the block diagram according to the hardware testing system of the embodiment of the invention;
Fig. 2 is the flow chart according to the hardware testing method of the embodiment of the invention;
Fig. 3 is the configuration of cells schematic diagram according to the embodiment of the invention;
Fig. 4 is the cell call schematic diagram according to the embodiment of the invention; And
Fig. 5 is the unit maps schematic diagram according to the embodiment of the invention.
Embodiment
Below with reference to accompanying drawing, describe the specific embodiment of the present invention in detail.
With reference to figure 1, the hardware testing system according to the embodiment of the invention is described.As shown in Figure 1, this hardware testing system comprises: hardware version storehouse 102 is used to store the hardware version information of hardware module to be tested; Test item storehouse 104 is used to store the test item of hardware module to be tested; The mapping relations storehouse is used to store the mapping relations between the test item of the hardware version information of hardware module to be tested and hardware module to be tested; And performance element storehouse 106, be used to store the test execution unit of hardware module to be tested, wherein, the test execution unit is used for according to the mapping relations between the test item of the hardware version information of hardware module to be tested and hardware module to be tested, find out the test item corresponding, and utilize the test item of being found out to treat the testing hardware module and test with the hardware version information of hardware module to be tested.
That is to say, may further comprise the steps: S202, the hardware version information of storage hardware module to be tested in the hardware version storehouse according to the hardware testing method of the embodiment of the invention; S204, the test item of storage hardware module to be tested in the test item storehouse; S206, the mapping relations in the mapping relations storehouse between the test item of the hardware version information of storage hardware module to be tested and hardware module to be tested; And S208, call the test execution unit of the hardware module to be tested of storing in the performance element storehouse, according to the mapping relations between the test item of the hardware version information of hardware module to be tested and hardware module to be tested, find out the test item corresponding, and utilize the test item of being found out to treat the testing hardware module and test with the hardware version information of hardware module to be tested.
Wherein, hardware version information is the information that is used to distinguish hardware module.Hardware version information can be described the current state of hardware module more all sidedly, has uniqueness.Can obtain the hardware version information that hardware module need present according to product requirement, upgrade corresponding hardware version information on the hardware module simultaneously.
Wherein, hardware version information can comprise any information that can describe the hardware module state, can adopt several information that wherein can be different from other hardware module hardware version information as hardware module.The function that the hardware module of different hardware version information representative is finished is different with the feature that is had, and needs the project of test also variant.Can obtain the project that hardware version need be tested according to hardware version information, thereby the hardware version information of hardware module be shone upon with test event and related.
Wherein, the design of test execution unit is fully corresponding with the hardware version information of hardware module, to guarantee all test execution unit of correspondence oneself of each hardware version.The test execution unit of the hardware version information correspondence of each hardware module is separate, is independent of each other.Can be according to the hardware version information of hardware module, call corresponding test execution unit automatically and finish the related of hardware version test item and test execution unit.
Wherein, the input of test execution unit and design basis are the test items of the hardware version of hardware module, by these concrete test items, comprise that in the test execution unit method of testing realizes, test result is collected, and test result reports etc.Certainly, the relation of hardware version information and test execution unit can be one to one, also can be many-one.
Wherein, the test result that reports of test execution unit can be along with the difference of the hardware version information of hardware module and difference.Because hardware version information is in the hardware testing item difference of different time sections, so test item can't be deposited in neat mode in memory cell, employing is carried out effective compress mode to the test result of test item, leaves in the memory cell, can greatly make things convenient for inquiry and result statistics.Wherein, the test result that reports of test execution unit comprise that test item title, test item code name, test item expend time in, information such as test item failure cause and test item error code.
Be that the present invention will be described for example with environment monitoring board (follow-up abbreviation EMC) below.There is following hardware version in EMC at present as a hardware module forming the base station:
1) EMC_a00, the hardware version front page;
2) EPLD upgrading in the EMC_a01, plate;
3) EMC_a02, important chip PHY upgrading causes the material list upgrading;
4) EMC_b00, PCB carries out correcting, increases transducer;
5) EMC_b01, the CPU model is changed, and removes the expansion serial port chip simultaneously;
6) EMC_b02, BOOT changes, and the CPU boot sequence is optimized.
Several information of selecting to be different from other hardware module from the expression of these hardware versions are formed hardware version information.Wherein, hardware version information can comprise parts such as EPLD version, material odd numbers, PCB version, CPU model, BOOT version.As long as wherein have a part to change, will cause the upgrading of hardware version.
Hardware version information will be stored in the hardware version storehouse 102.In this storehouse, will preserve the hardware version information of all hardware module.If the hardware version upgrading then needs interpolation (as shown in Figure 3) is upgraded in hardware version storehouse 102.
Different hardware version corresponding hardware version information differences, corresponding hardware version test item also exists difference, test item increases or the situation of deletion so must have.Because the hardware testing Xiang Jun of all hardware module is kept in the public test item storehouse 104, so, then need interpolation (as shown in Figure 3) is upgraded in the test item storehouse if there is not corresponding test item in the test item storehouse 104.
So how represent hardware version which test item arranged? this just needs the mapping relations storehouse 106 between inquiry test item storehouse and the hardware version storehouse.The relation between test item storehouse and the hardware version storehouse has been preserved in the mapping relations storehouse, and promptly which test item is each hardware version correspondence.
The hardware version difference will inevitably cause the test execution unit will finish different test functions, or carries out the compatibility design, or carries out the design of test execution unit again, with the variation of coverage test item.
For at different hardware versions, whether carry out the redesign of test execution unit again, need carry out testing evaluation, evaluating standard is taken all factors into consideration from the following aspects:
1) stability of test execution unit and reliability;
2) the code maintainability of test execution unit;
3) requirement of the construction cycle of test execution unit;
4) the human resources requirement of test execution unit exploitation;
5) consideration of others.
A hardware version must have a unique test execution unit corresponding with it, thereby avoided the promiscuous relation between hardware version and the test execution unit fully, guarantee the comprehensive and uniqueness of test of the increment (increase and delete function) of hardware module, increased the reliability and stability of test.Can obtain the test execution unit of corresponding hardware version by performance element storehouse 106, the test fully that the test execution unit can reach the hardware version test item covers.
How does calling between them realize so? as shown in Figure 4, when the user imports the hardware version information of hardware module to be tested, pass through condition query, according to the mapping relations between hardware version information and the test item, from the test item storehouse, extract test item and form the test item set,, call corresponding test execution unit simultaneously according to hardware version information, execution by the test execution unit outputs test result.
Need to prove, for hardware version, if belong to the different hardware version of same hardware module, for example EMC_a00 shown in Fig. 5 and EMC_a02, because the difference that test item set exists is less,, do not influence performance element stability, reliability and code maintenance considering for the compatibility design of the performance element of these two hardware versions at all, can shorten again simultaneously under the superiority condition such as construction cycle, can use same test execution unit fully.For EMC_b00,, under situation about taking all factors into consideration, can select to develop again a test execution unit because change is bigger.Promptly when make compatibility, when do not make compatibility, whether the test increment that can pass through the hardware version of hardware module fully satisfies compatible evaluation condition decision, to promote development﹠ testing efficient.
The test execution unit will output test result after finishing test assignment, and the preservation of test result can be preserved with forms such as text, EXCEL or databases.What application was more at present is that application data base is preserved, and its advantage is self-evident, can greatly make things convenient for user's condition query and result statistics.But,, in the realization of the database of saving result, acquire a certain degree of difficulty because the difference of the test item that the hardware version difference of hardware module is caused more or less, or increases or deletion.
Adopt the mode of effectively compression to carry out preservation as a result, when carrying out the initial data statistics, carry out effective decompress(ion) and just can obtain original data message.The form of preserving can be as shown in Figure 5.Certainly, the present invention also is not limited to compression shown in Figure 5 and decompressing method.
The above is embodiments of the invention only, is not limited to the present invention, and for a person skilled in the art, the present invention can have various changes and variation.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within the claim scope of the present invention.
Claims (10)
1. a hardware module testing system is characterized in that, comprising:
The hardware version storehouse is used to store the hardware version information of hardware module to be tested;
The test item storehouse is used to store the test item of described hardware module to be tested;
The mapping relations storehouse is used to store the mapping relations between the test item of the hardware version information of described hardware module to be tested and described hardware module to be tested; And
The performance element storehouse, be used to store the test execution unit of described hardware module to be tested, described test execution unit is used for according to the mapping relations between the test item of the hardware version information of described hardware module to be tested and described hardware module to be tested, find out the test item corresponding, and utilize the test item of being found out that described hardware module to be tested is tested with the hardware version information of described hardware module to be tested.
2. hardware module testing system according to claim 1 is characterized in that, the hardware version information of described hardware module to be tested has uniqueness.
3. hardware module testing system according to claim 2 is characterized in that, described hardware version information comprises at least a in the following information: EPLD version, material odd numbers, PCB version, CPU model, BOOT version.
4. according to each described hardware module testing system in the claim 1 to 3, it is characterized in that, is man-to-man relation between the hardware version information of described hardware module to be tested and the test execution unit of described hardware module to be tested.
5. according to each described hardware module testing system in the claim 1 to 3, it is characterized in that, is many-to-one relation between the hardware version information of described hardware module to be tested and the test execution unit of described hardware module to be tested.
6. a hardware module testing method is characterized in that, may further comprise the steps:
The hardware version information of storage hardware module to be tested in the hardware version storehouse;
The test item of the described hardware module to be tested of storage in the test item storehouse;
Mapping relations in the mapping relations storehouse between the test item of the hardware version information of the described hardware module to be tested of storage and described hardware module to be tested; And
Call the test execution unit of the described hardware module to be tested of storing in the performance element storehouse, according to the mapping relations between the test item of the hardware version information of described hardware module to be tested and described hardware module to be tested, find out the test item corresponding, and utilize the test item of being found out that described hardware module to be tested is tested with the hardware version information of described hardware module to be tested.
7. hardware module testing method according to claim 6 is characterized in that, the hardware version information of described hardware module to be tested has uniqueness.
8. hardware module testing method according to claim 7 is characterized in that, described hardware version information comprises at least a in the following information: EPLD version, material odd numbers, PCB version, CPU model, BOOT version.
9. according to each described hardware module testing method in the claim 6 to 8, it is characterized in that, is man-to-man relation between the hardware version information of described hardware module to be tested and the test execution unit of described hardware module to be tested.
10. according to each described hardware module testing method in the claim 6 to 8, it is characterized in that, is many-to-one relation between the hardware version information of described hardware module to be tested and the test execution unit of described hardware module to be tested.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101818188A CN101159775B (en) | 2007-10-16 | 2007-10-16 | Hardware module testing system and method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101818188A CN101159775B (en) | 2007-10-16 | 2007-10-16 | Hardware module testing system and method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101159775A true CN101159775A (en) | 2008-04-09 |
| CN101159775B CN101159775B (en) | 2010-06-23 |
Family
ID=39307689
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101818188A Expired - Fee Related CN101159775B (en) | 2007-10-16 | 2007-10-16 | Hardware module testing system and method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101159775B (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108319531A (en) * | 2017-12-19 | 2018-07-24 | 瑞斯康达科技发展股份有限公司 | A kind of detection method and detection device of configuration information |
| CN113590394A (en) * | 2021-07-09 | 2021-11-02 | 深圳Tcl新技术有限公司 | Joint debugging test method and device, electronic equipment and storage medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1113296C (en) * | 1999-03-05 | 2003-07-02 | 英业达股份有限公司 | Hardware testing module and method for increasing hardeare testing speed |
| JP2003122592A (en) * | 2001-10-11 | 2003-04-25 | Nec Miyagi Ltd | Hardware inspection system |
-
2007
- 2007-10-16 CN CN2007101818188A patent/CN101159775B/en not_active Expired - Fee Related
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108319531A (en) * | 2017-12-19 | 2018-07-24 | 瑞斯康达科技发展股份有限公司 | A kind of detection method and detection device of configuration information |
| CN108319531B (en) * | 2017-12-19 | 2021-04-20 | 瑞斯康达科技发展股份有限公司 | Configuration information detection method and detection device |
| CN113590394A (en) * | 2021-07-09 | 2021-11-02 | 深圳Tcl新技术有限公司 | Joint debugging test method and device, electronic equipment and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101159775B (en) | 2010-06-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101651576B (en) | Alarm information processing method and system | |
| CN102906751B (en) | A kind of method of data storage, data query and device | |
| CN101102565B (en) | A processing method, device and equipment of user data in communication terminal | |
| CN103049515A (en) | Method, device and equipment for classifying application programs | |
| CN102236672A (en) | Method and device for importing data | |
| EP0586550A1 (en) | Relational data base memory utilization analyzer | |
| CN104239377A (en) | Platform-crossing data retrieval method and device | |
| CN103853714A (en) | Data processing method and device | |
| CN114490527B (en) | Metadata retrieval method, system, terminal and storage medium | |
| CN106708825A (en) | Data file processing method and system | |
| CN108984626B (en) | Data processing method and device and server | |
| CN112711612A (en) | Data processing method, data processing device, storage medium and electronic device | |
| CN109408471B (en) | Compressed packet decompression method and device based on matching tree and storage medium | |
| CN101159775B (en) | Hardware module testing system and method | |
| CN101452486A (en) | System data management method for [inscriptions on bones or tortoise shells and apparatus thereof | |
| CN103425793A (en) | Method for accessing database by means of database storage layer used in instant communication system | |
| CN112162731B (en) | Data expansion method, device, storage medium and electronic device | |
| CN115525655A (en) | Method and system for data query slicing | |
| US7930489B2 (en) | Techniques for optimizing configuration partitioning | |
| CN114579097A (en) | Cloud native data API construction method based on single data stream | |
| CN103279575A (en) | Method and device for processing file information | |
| CN110633388B (en) | Real-time index generation method, system and storage medium based on communication XDR | |
| CN103152386B (en) | Business datum Distributor and business datum distribution method thereof | |
| CN111611056A (en) | Data processing method and device, computer equipment and storage medium | |
| CN111782636A (en) | Data processing method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20100623 Termination date: 20161016 |