CN109992493B - Test method for eliminating software exception of gas water heater - Google Patents
Test method for eliminating software exception of gas water heater Download PDFInfo
- Publication number
- CN109992493B CN109992493B CN201711471498.XA CN201711471498A CN109992493B CN 109992493 B CN109992493 B CN 109992493B CN 201711471498 A CN201711471498 A CN 201711471498A CN 109992493 B CN109992493 B CN 109992493B
- Authority
- CN
- China
- Prior art keywords
- test
- software
- rule
- gas water
- water heater
- 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
Links
- XLYOFNOQVPJJNP-UHFFFAOYSA-N water Substances O XLYOFNOQVPJJNP-UHFFFAOYSA-N 0.000 title claims abstract description 45
- 238000010998 test method Methods 0.000 title claims abstract description 15
- 238000012360 testing method Methods 0.000 claims abstract description 110
- 238000013024 troubleshooting Methods 0.000 claims abstract description 12
- 238000004891 communication Methods 0.000 claims abstract description 10
- 238000000034 method Methods 0.000 claims abstract description 8
- 230000002159 abnormal effect Effects 0.000 claims abstract description 7
- 238000001514 detection method Methods 0.000 claims description 7
- 238000011161 development Methods 0.000 abstract description 2
- 238000012938 design process Methods 0.000 abstract 1
- 230000008030 elimination Effects 0.000 description 2
- 238000003379 elimination reaction Methods 0.000 description 2
- 230000005856 abnormality Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
- 230000002035 prolonged 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/07—Responding to the occurrence of a fault, e.g. fault tolerance
- G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
- G06F11/079—Root cause analysis, i.e. error or fault diagnosis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Biomedical Technology (AREA)
- Testing And Monitoring For Control Systems (AREA)
- Alarm Systems (AREA)
Abstract
A test method for eliminating software exception of a gas water heater is characterized by comprising the following steps: firstly, building a communication platform; secondly, establishing a database, and writing test regulations into the database; thirdly, starting the upper computer and connecting the upper computer with a database; writing a software fault rate reference value beta, and selecting a rule and a test frequency n; fifthly, judging whether the test times j are more than or equal to n, if so, turning to the seventh step; if not, carrying out the next step; sixthly, testing the gas water heater by the selected regulations in sequence, and returning to the fifth step; seventhly, counting the failure rate k; eighthly: and outputting a test result: a. the failure rate k is 0%, and the software is normal; b. the failure rate k is 100%, and software fails; c. k is more than or equal to 0% and less than or equal to beta, and each fault is the same, other abnormal conditions exist; d. k is more than or equal to 0% and less than or equal to beta, and faults are different each time, troubleshooting is carried out from software; e. and when the beta is not less than or equal to k is not more than 100 percent, troubleshooting is carried out from software. The invention has the advantages that: the fault range of the gas water heater can be reduced, so that the test period is shortened, the test efficiency is improved, and the method has important significance on the whole development and design process of the gas water heater.
Description
Technical Field
The invention relates to a fault elimination method for a gas water heater, in particular to a test method for eliminating software exception of the gas water heater.
Background
Safety of the gas water heater is very important, and thus the test work is also important. However, from the present situation, the test of the gas water heater is still in a relatively laggard manual test stage, the automatic test in each performance aspect is not perfect, each important component in the manual detection equipment is basically checked little by little, and the final fault location is found.
The faults of the gas water heater in the testing process have various conditions, various fault types such as faults caused by software problems or hardware problems or faults caused by external factors can occur, if the fault conditions can not be positioned in an accurate fault type testing range, once the faults are tested, the conditions of no trouble can occur, the fault reasons can be difficult to directly find out, for example, the hardware faults can be always corrected due to the software faults, or the software faults can be always corrected due to the external factors, so that the whole testing period is long, the efficiency is low, the working time of developers can be prolonged, the working efficiency of the developers is reduced, and the problems can not be found by the developers late, and the working enthusiasm is hit.
Disclosure of Invention
The technical problem to be solved by the invention is to provide a test method capable of eliminating the software exception of the gas water heater aiming at the current state of the prior art, and the test method can effectively reduce the troubleshooting range and shorten the test period.
The technical scheme adopted by the invention for solving the technical problems is as follows: a test method for eliminating software exception of a gas water heater is characterized by comprising the following steps:
step one, a communication platform is built between a mainboard of a gas water heater and a PC (personal computer) end of an upper computer;
step two, establishing a database at the PC end, and writing the test rule into the database according to a specified format;
step three, the PC end starts the upper computer and is connected with a database;
step four, configuring an upper computer, writing a software fault rate reference value beta, and selecting a rule to be tested and the test times n;
step five, judging whether the test times j are more than or equal to n, if so, turning to step seven; if not, the next step is carried out;
step six, testing the gas water heaters in sequence according to the selected regulations in the step four, and then returning to the step five;
step seven, the upper computer calculates the failure rate of the failed test rule and counts the failure rate k of the test result of each rule;
step eight: comparing the pre-input software fault rate reference value beta, and outputting the test result corresponding to each test rule according to the following conditions:
a. if the failure rate k of the test result of the ith rule is 0%, judging that the software under the test of the rule is in a normal working state;
b. if the failure rate of the ith rule test result is that k is 100%, judging that the software under the rule test is abnormal and belongs to software failure;
c. if the failure rate of the ith rule test result is more than 0% < k < beta, and the failures occurring in each time are the same, judging that the failure occurrence under the rule test is not caused by software exception, but other exception conditions exist, and suggesting troubleshooting from other aspects;
d. if the failure rate of the ith rule test result is more than 0% < k < beta, and the failures occurring in each time are different, judging that the failure under the rule test is caused by software abnormity, and recommending to carry out troubleshooting from the aspect of software;
e. and if the failure rate beta of the ith rule test result is less than 100%, judging that the failure under the rule test is caused by software exception, and recommending to carry out troubleshooting from the aspect of software.
In order to ensure the testing accuracy and improve the testing precision, preferably, the testing times in the fourth step are n is more than or equal to 50.
Preferably, in the sixth step, a regression testing method is adopted for the testing method of the gas water heater by each rule, and after all the rules are tested, the second round and the third round … … for the nth round are performed again, which specifically includes the following steps:
(6.1) the upper computer sends a test instruction;
(6.2) the gas water heater mainboard receives the instruction and feeds back detection data to the upper computer;
(6.3) the upper computer receives the actually fed back detection data and judges whether the actually detected data are consistent with preset theoretical data or not, if so, the rule test is passed, and the next step is carried out; if not, the rule test is failed, and then the step (6.5) is carried out;
(6.4) judging whether the selected regulations are tested for all times, if so, ending the test in the current round; if not, continuing the test of the next rule and returning to the step (6.1)
(6.5), recording the number of times of failing of the rule, increasing the failing count once, and returning to the previous step (6.4).
Preferably, the communication between the gas water heater mainboard and the upper computer PC terminal in the first step is a serial communication mode.
Preferably, the software fault rate reference value β in the fourth step is an empirical value obtained from a previous fault analysis on the gas water heater software portion.
Compared with the prior art, the invention has the advantages that: the automatic test method for eliminating the software faults is introduced, the fault rate of each example obtained by testing is compared with the software fault rate reference value beta according to the software fault rate reference value beta obtained by analyzing the faults of the software part of the gas water heater in the early stage, and then the faults caused by the abnormal software are eliminated.
Drawings
Fig. 1 is a main flow chart of a testing method according to an embodiment of the present invention.
FIG. 2 is a sub-flowchart of a testing method according to an embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the accompanying examples.
As shown in fig. 1-2, the present embodiment relates to fault elimination of a gas water heater, and is mainly to determine a series of faults occurring in a test process of the gas water heater, and to eliminate the fault of software itself.
In the design and development process of a gas water heater, software has reproducibility, generally, once a software part is abnormal, each gas water heater provided with the software is abnormal, hardware is different, and even though the same hardware part structure is influenced by processing precision and assembly precision in a production process, the condition that each gas water heater provided with the hardware part structure finally fails is different, so that the embodiment provides a test method for eliminating the software abnormality of the gas water heater aiming at the reproducibility characteristic of the software, and the test method comprises the following steps:
step one, a communication platform is built between a mainboard of a lower computer gas water heater and a PC end of an upper computer, and the communication between the mainboard of the gas water heater and the PC end is a serial communication mode.
Step two, establishing a database at the PC end, and writing the test rule into the database according to a specified format; the upper computer can select local test regulations or test regulations pre-stored in a database, and the test regulations are written according to a uniform format, so that the upper computer can directly read the contents of the regulations to be tested, the time for the machine to translate is saved, and the efficiency is improved.
And step three, the PC end starts the upper computer and is connected with the database.
Fourthly, configuring an upper computer, and writing a software fault rate reference value beta into the upper computer, wherein the software fault rate reference value beta is an empirical value obtained according to the fault analysis of the gas water heater software part in the earlier stage; then, the rule to be tested (different rules are for different fault conditions, such as voltage, current, over-temperature protection, etc.) and the test number n are selected, wherein n is more than or equal to 50 in order to improve the test precision and accuracy.
Step five, judging whether the test times j are more than or equal to n, if so, turning to step seven; if not, the next step is performed.
Step six, testing the gas water heaters in sequence according to the selected regulations in the step four, and then returning to the step five; the method for testing the gas water heater by each rule in the step specifically comprises the following steps:
(6.1) the upper computer sends a test instruction;
(6.2) the lower computer gas water heater mainboard receives the instruction and feeds back detection data to the upper computer;
(6.3) the upper computer receives the actually fed back detection data and judges whether the actually detected data are consistent with preset theoretical data or not, if so, the rule test is passed, and the next step is carried out; if not, the rule test is failed, and then the step (6.5) is carried out;
(6.4) judging whether the selected regulations are tested for all times, if so, ending the test in the current round; if not, continuing the test of the next rule and returning to the step (6.1)
(6.5), recording the number of times of failing of the rule, increasing the failing count once, and returning to the previous step (6.4).
Step seven, the upper computer calculates the failure rate of the failed test rule and counts the failure rate k of the test result of each rule; and step six, each test rule needs to be tested for n times, the corresponding number of faults can occur in the tests for n times, the fault rate k of each rule is calculated, and then the fault rate k is compared with the preset fault rate beta.
Step eight: comparing the pre-input software fault rate reference value beta, and outputting the test result corresponding to each test rule according to the following conditions:
a. if the failure rate k of the test result of the ith rule is 0%, judging that the software under the test of the rule is in a normal working state;
b. if the failure rate of the ith rule test result is that k is 100%, judging that the software under the rule test is abnormal and belongs to software failure;
c. if the failure rate of the ith rule test result is more than 0% < k < beta, and the failures occurring in each time are the same, judging that the failure occurrence under the rule test is not caused by software exception, but other exception conditions exist, and suggesting troubleshooting from other aspects;
d. if the failure rate of the ith rule test result is more than 0% < k < beta, and the failures occurring in each time are different, judging that the failure under the rule test is caused by software abnormity, and recommending to carry out troubleshooting from the aspect of software;
e. and if the failure rate beta of the ith rule test result is less than 100%, judging that the failure under the rule test is caused by software exception, and recommending to carry out troubleshooting from the aspect of software.
The method and the device test the correctness of the software of the gas water heater from the software logic, introduce an n-time regression testing mechanism, directly perform regression testing after all testing of one testing rule is completed once, perform secondary testing, record whether the test passes or has been tested for several times in the background every time, and facilitate the statistics of the results in the following.
The embodiment can automatically test the software part of the whole gas water heater, and finally achieves the purpose of distinguishing software faults from other faults.
Claims (5)
1. A test method for eliminating software exception of a gas water heater is characterized by comprising the following steps:
step one, a communication platform is built between a mainboard of a gas water heater and a PC (personal computer) end of an upper computer;
step two, establishing a database at the PC end, and writing the test rule into the database according to a specified format;
step three, the PC end starts the upper computer and is connected with a database;
step four, configuring an upper computer, writing a software fault rate reference value beta, and selecting a rule to be tested and the test times n;
step five, judging whether the test times j are more than or equal to n, if so, turning to step seven; if not, the next step is carried out;
step six, testing the gas water heaters in sequence according to the selected regulations in the step four, and then returning to the step five;
step seven, the upper computer calculates the failure rate of the failed test rule and counts the failure rate k of the test result of each rule;
step eight: comparing the pre-input software fault rate reference value beta, and outputting the test result corresponding to each test rule according to the following conditions:
a. if the failure rate k of the test result of the ith rule is 0%, judging that the software under the test of the rule is in a normal working state;
b. if the failure rate of the ith rule test result is that k is 100%, judging that the software under the rule test is abnormal and belongs to software failure;
c. if the failure rate of the ith rule test result is more than 0% < k < beta, and the failures occurring in each time are the same, judging that the failure occurrence under the rule test is not caused by software exception, but other exception conditions exist, and suggesting troubleshooting from other aspects;
d. if the failure rate of the ith rule test result is more than 0% < k < beta, and the failures occurring in each time are different, judging that the failure under the rule test is caused by software abnormity, and recommending to carry out troubleshooting from the aspect of software;
e. and if the failure rate beta of the ith rule test result is less than 100%, judging that the failure under the rule test is caused by software exception, and recommending to carry out troubleshooting from the aspect of software.
2. The test method for eliminating the software exception of the gas water heater according to claim 1, wherein: and the test times n in the fourth step are more than or equal to 50.
3. The test method for eliminating the software exception of the gas water heater according to claim 1, wherein: the method for testing the gas water heater by each rule in the sixth step specifically comprises the following steps:
(6.1) the upper computer sends a test instruction;
(6.2) the gas water heater mainboard receives the instruction and feeds back detection data to the upper computer;
(6.3) the upper computer receives the actually fed back detection data and judges whether the actually detected data are consistent with preset theoretical data or not, if so, the rule test is passed, and the next step is carried out; if not, the rule test is failed, and then the step (6.5) is carried out;
(6.4) judging whether the selected regulations are tested for all times, if so, ending the test in the current round; if not, continuing the test of the next rule and returning to the step (6.1)
(6.5), recording the number of times of failing of the rule, increasing the failing count once, and returning to the previous step (6.4).
4. The test method for eliminating the software exception of the gas water heater according to claim 1, wherein: and the communication between the mainboard of the gas water heater and the PC end of the upper computer in the step one is a serial port communication mode.
5. The test method for eliminating the software exception of the gas water heater according to claim 1, wherein: and the software fault rate reference value beta in the fourth step is an empirical value obtained according to the fault analysis aiming at the gas water heater software part in the earlier stage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711471498.XA CN109992493B (en) | 2017-12-29 | 2017-12-29 | Test method for eliminating software exception of gas water heater |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711471498.XA CN109992493B (en) | 2017-12-29 | 2017-12-29 | Test method for eliminating software exception of gas water heater |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109992493A CN109992493A (en) | 2019-07-09 |
| CN109992493B true CN109992493B (en) | 2021-12-10 |
Family
ID=67108853
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711471498.XA Active CN109992493B (en) | 2017-12-29 | 2017-12-29 | Test method for eliminating software exception of gas water heater |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109992493B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5909404A (en) * | 1998-03-27 | 1999-06-01 | Lsi Logic Corporation | Refresh sampling built-in self test and repair circuit |
| CN102055604A (en) * | 2009-11-05 | 2011-05-11 | ***通信集团山东有限公司 | Fault location method and system thereof |
| CN102608993A (en) * | 2012-03-09 | 2012-07-25 | 北京经纬恒润科技有限公司 | Network automation test method, cabinet and test host |
| CN102622295A (en) * | 2012-02-17 | 2012-08-01 | 北京航空航天大学 | Self-adapting software defect positioning method based on predicate execution information analysis |
| CN102968351A (en) * | 2012-12-13 | 2013-03-13 | 中国航空无线电电子研究所 | External control method for BIT parameters |
| CN104503908A (en) * | 2014-12-17 | 2015-04-08 | 西北工业大学 | Predicate frequency statistics based software fault locating method |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7065676B1 (en) * | 2002-12-27 | 2006-06-20 | Unisys Corporation | Multi-threaded memory management test system with feedback to adjust input parameters in response to performance |
| US20060207321A1 (en) * | 2005-03-17 | 2006-09-21 | Quinton Lyon | Level measurement device with a programmable module and programming terminal |
| CN103106134B (en) * | 2011-11-10 | 2016-01-13 | 阿里巴巴集团控股有限公司 | A kind of performance deficiency detection method, device and system |
| CN102708052B (en) * | 2012-04-27 | 2017-10-20 | 北京邮电大学 | Software fault automatic positioning method in a kind of unit testing |
| CN104346243A (en) * | 2013-07-30 | 2015-02-11 | 旭达电脑（昆山）有限公司 | System for automatic adjustment of main board testing process and implement method thereof |
-
2017
- 2017-12-29 CN CN201711471498.XA patent/CN109992493B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US5909404A (en) * | 1998-03-27 | 1999-06-01 | Lsi Logic Corporation | Refresh sampling built-in self test and repair circuit |
| CN102055604A (en) * | 2009-11-05 | 2011-05-11 | ***通信集团山东有限公司 | Fault location method and system thereof |
| CN102622295A (en) * | 2012-02-17 | 2012-08-01 | 北京航空航天大学 | Self-adapting software defect positioning method based on predicate execution information analysis |
| CN102608993A (en) * | 2012-03-09 | 2012-07-25 | 北京经纬恒润科技有限公司 | Network automation test method, cabinet and test host |
| CN102968351A (en) * | 2012-12-13 | 2013-03-13 | 中国航空无线电电子研究所 | External control method for BIT parameters |
| CN104503908A (en) * | 2014-12-17 | 2015-04-08 | 西北工业大学 | Predicate frequency statistics based software fault locating method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109992493A (en) | 2019-07-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8935676B2 (en) | Automated test failure troubleshooter | |
| CN105425201B (en) | metering chip simulation test method for software reliability detection of intelligent electric energy meter | |
| US10860407B2 (en) | Dynamic error code, fault location, and test and troubleshooting user experience correlation/visualization systems and methods | |
| TW200537111A (en) | Method and apparatus for automated debug and optimization of in-circuit tests | |
| CN109992493B (en) | Test method for eliminating software exception of gas water heater | |
| CN113392000A (en) | Test case execution result analysis method, device, equipment and storage medium | |
| CN105653455A (en) | Program vulnerability detection method and detection system | |
| US20080154530A1 (en) | Method for normalized test line limits with measurement uncertainty | |
| CN113760772B (en) | Use case execution method of semi-automatic/automatic execution system for testability test | |
| CN114363145A (en) | BIT fault injection and detection time sequence control method for airborne electronic system | |
| EP3958124B1 (en) | Flight management system and method for reporting an intermitted error | |
| CN110967615B (en) | Circuit board fault diagnosis device and method | |
| Kirby et al. | Microprocessor-based protective relays deliver more information and superior reliability with lower maintenance costs | |
| CN112114242B (en) | On-line monitoring and analyzing method for automatic IC test | |
| CN112069749B (en) | Power supply connection verification method and device, electronic equipment and storage medium | |
| CN116382968B (en) | Fault detection method and device for external equipment | |
| CN108919169A (en) | A kind of fault self-diagnosis method of electric energy meter | |
| CN114089726B (en) | Fault diagnosis system | |
| US11544165B2 (en) | Method for locating and repairing intermittent faults in communication structures of an aircraft | |
| US20240055304A1 (en) | Method and device for optimizing an amount of testing with respect to a total test time | |
| CN108802538B (en) | Instrument diagnosis method and system applied to comprehensive tester | |
| CN115454704A (en) | Server fault diagnosis test method, device, terminal and storage medium | |
| CN105207840A (en) | Network terminal user offline frequency detection system and method | |
| Liebmann et al. | Using statistical analysis methods to predict switching stability | |
| US20210072312A1 (en) | Boundary Scan Test System And Method Thereof |
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 | ||
| PE01 | Entry into force of the registration of the contract for pledge of patent right |
Denomination of invention: A Testing Method for Eliminating Software Abnormalities in Gas Water Heaters Effective date of registration: 20231102 Granted publication date: 20211210 Pledgee: Bank of China Limited Ningbo Hangzhou Bay New Area sub branch Pledgor: NINGBO FOTILE KITCHEN WARE Co.,Ltd. Registration number: Y2023980063518 |
|
| PE01 | Entry into force of the registration of the contract for pledge of patent right |