Timeline for How to correct a mistake in the test, after writing implementation
Current License: CC BY-SA 3.0
25 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 12, 2018 at 6:52 | history | edited | candied_orange | CC BY-SA 3.0 | added 48 characters in body |
| Apr 13, 2017 at 12:45 | history | edited | CommunityBot | replaced http://softwareengineering.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Feb 1, 2017 at 21:37 | history | edited | candied_orange | CC BY-SA 3.0 | added 98 characters in body |
| Feb 1, 2017 at 2:31 | history | edited | candied_orange | CC BY-SA 3.0 | deleted 10 characters in body |
| Jan 31, 2017 at 18:45 | vote | accept | Attilio | ||
| Jan 30, 2017 at 13:36 | history | edited | candied_orange | CC BY-SA 3.0 | added 251 characters in body |
| Jan 30, 2017 at 12:20 | history | edited | candied_orange | CC BY-SA 3.0 | deleted 6 characters in body |
| Jan 30, 2017 at 11:39 | history | edited | candied_orange | CC BY-SA 3.0 | deleted 6 characters in body |
| Jan 30, 2017 at 11:15 | history | edited | candied_orange | CC BY-SA 3.0 | edited body |
| Jan 30, 2017 at 10:53 | history | edited | candied_orange | CC BY-SA 3.0 | added 16 characters in body |
| Jan 30, 2017 at 5:02 | history | edited | candied_orange | CC BY-SA 3.0 | deleted 4 characters in body |
| Jan 30, 2017 at 4:20 | history | edited | candied_orange | CC BY-SA 3.0 | added 171 characters in body |
| Jan 30, 2017 at 4:01 | history | edited | candied_orange | CC BY-SA 3.0 | added 564 characters in body |
| Jan 30, 2017 at 3:54 | history | edited | candied_orange | CC BY-SA 3.0 | added 564 characters in body |
| Jan 30, 2017 at 3:45 | history | edited | candied_orange | CC BY-SA 3.0 | added 564 characters in body |
| Jan 30, 2017 at 3:25 | history | edited | candied_orange | CC BY-SA 3.0 | added 564 characters in body |
| Jan 30, 2017 at 3:15 | history | edited | candied_orange | CC BY-SA 3.0 | added 564 characters in body |
| Jan 29, 2017 at 16:29 | history | edited | candied_orange | CC BY-SA 3.0 | added 12 characters in body |
| Jan 29, 2017 at 13:21 | comment | added | jonrsharpe | @GolezTrol I didn't say how to revert the code; comment it out, cut and paste, stash it, use your IDE's history; it doesn't really matter. The crucial thing is why you do it: so you can check that you're getting the right failure. I've edited, hopefully to clarify. | |
| Jan 29, 2017 at 13:19 | comment | added | GolezTrol | @jonrsharpe Your answer is good too, and I upvoted it before even reading this one. But where you are very strict in reverting the code, CandiedOrange suggests a more pragmatic approach that appeals more to me. | |
| Jan 29, 2017 at 9:53 | comment | added | jonrsharpe | @GolezTrol I think my answer says the same thing, so I'd appreciate any feedback you had on whether that was unclear. | |
| Jan 29, 2017 at 5:25 | history | edited | candied_orange | CC BY-SA 3.0 | added 6 characters in body |
| Jan 29, 2017 at 4:59 | history | edited | candied_orange | CC BY-SA 3.0 | deleted 1 character in body |
| Jan 29, 2017 at 2:47 | comment | added | GolezTrol | I like this answer best: It's important to see the test fail with incorrect code, so I would delete/comment out the code, correct the tests and see them fail, put back the code (maybe introduce a deliberate error to put the tests to the test) and correct to code to make it work. It's very XP to completely delete and rewrite it, but sometimes you just have to be pragmatic. ;) | |
| Jan 29, 2017 at 2:04 | history | answered | candied_orange | CC BY-SA 3.0 |