Timeline for Writing tests for code whose purpose I don't understand
Current License: CC BY-SA 3.0
2 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 24, 2017 at 18:22 | comment | added | user251748 | Any kind of info is better than flying blind. I used to locate bugs in server programs that were in production by invoking the debugger on a crash dump file (Unix) and asking for the stack trace. It gave me the name of the function where the fault occurred. Even with no other knowledge (I didn't know how to use this debugger) it helped in what would otherwise be a mysterious and unreproducable situation. | |
| Feb 24, 2017 at 15:49 | history | answered | h22 | CC BY-SA 3.0 |