Timeline for Does it make sense to write tests for legacy code when there is no time for a complete refactoring?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Jun 8, 2014 at 12:52 | history | suggested | Michael Green | CC BY-SA 3.0 | Repettion removed. |
| Jun 8, 2014 at 10:39 | review | Suggested edits | |||
| S Jun 8, 2014 at 12:52 | |||||
| Feb 6, 2014 at 16:48 | comment | added | Izkata | Sadly true. We have a couple of obvious bugs that manifest in edge cases that we can't fix because our client prefers consistency over correctness. (They're caused due to the data-gathering code allowing things the reporting code doesn't take into account, like leaving one field in a series of fields blank) | |
| Feb 6, 2014 at 11:01 | history | answered | Rory Hunter | CC BY-SA 3.0 |