| ??? 09/09/05 13:05 Read: times |
#100864 - Testing Responding to: ???'s previous message |
Erik Malund said:
I often have the unfortunate "pleasure" of seeing code that is based on everything just humming along, and, invariably, I have to add measures to handle when that is not the case. Trouble is, much of the so-called "testing" that people speak of is done on the same principle: "I've tested this and it works" means "I supplied all the right inputs, and got all the right outputs" - but, as soon as something slightly askew happens, it all stops working and they say, "I tested this and it was working - but now it's stopped. How can that possibly happen??" |
| Topic | Author | Date |
| I just had to fix something in a system | 01/01/70 00:00 | |
| 90:10 Rule | 01/01/70 00:00 | |
| code like this is where we hear "the cod | 01/01/70 00:00 | |
| Testing | 01/01/70 00:00 | |
| A common 'gotcha' | 01/01/70 00:00 | |
| Design document | 01/01/70 00:00 | |
| What is magic document you speak of? | 01/01/70 00:00 | |
Ask | 01/01/70 00:00 | |
| Normal | 01/01/70 00:00 |