??? 01/03/09 17:15 Read: times |
#161282 - before testing Responding to: ???'s previous message |
Richard Erlacher said:
The key is in thorough testing ... Actually, as Richard has often said elsewhere, the key comes long before testing; In fact, the key comes before you even write the first line of code; The key is in a full & through design, and then in a rigorous implementation process. Be sure that everything is throroughly reviewed at all stages throughout the process. As the old QA saying goes, "you cannot test quality into a product" not just "try it to see whether it works", The "normal" operation possibly accounts for 10% of the overall development effort; the other 90% is in ensuring that you correctly & safely handle all the possible "exception" cases... but real testing, in which you subject a batch of what you consider to be fully functional and perfect-in-every-way systems to all the conditions, extreme heat, extreme humidity, extreme cold, chemical pollution, EMI, shock, vibration, for an extended period... This focusses on the physical, "hardware" aspects - your software testing needs to be similarly rigorous: You need to ensure that all paths through your software have been tested; You need to ensure that all the "failure" cases have been exercised... |
Topic | Author | Date |
Mcu working for 24x7 | 01/01/70 00:00 | |
:) | 01/01/70 00:00 | |
be careful | 01/01/70 00:00 | |
before testing | 01/01/70 00:00 | |
sayings | 01/01/70 00:00 | |
They dont disclose exactly | 01/01/70 00:00 | |
Mars Rover | 01/01/70 00:00 | |
That wasn't a failure mode! | 01/01/70 00:00 | |
It could too be a failure.... | 01/01/70 00:00 | |
indeed, it could ... but it wasn't! | 01/01/70 00:00 | |
Essential![]() | 01/01/70 00:00 | |
On the code side, | 01/01/70 00:00 | |
Mcu working for 24x7 | 01/01/70 00:00 | |
On the EMI/EMC side | 01/01/70 00:00 |