Timeline for Functional testing before code checkin
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2014 at 9:07 | comment | added | Arseni Mourzenko | “enforce a rule that each code check-in must have test, not only test but functional test as well”: Imagine a check-in is made to simply correct a typo in user interface. What would be the reaction of the developer who will be forced to write a unit test and a functional test for that? | |
| Jan 12, 2013 at 22:03 | history | tweeted | twitter.com/#!/StackProgrammer/status/290217386844512256 | ||
| Jan 12, 2013 at 12:44 | history | edited | gnat |
edited tags
|
|
| Jan 12, 2013 at 12:38 | history | edited | gnat | CC BY-SA 3.0 |
edited tags; edited title
|
| Jan 12, 2013 at 12:00 | answer | added | gnat | timeline score: 4 | |
| Jan 12, 2013 at 5:15 | answer | added | iteratingself | timeline score: 6 | |
| Jan 12, 2013 at 3:33 | comment | added | maple_shaft♦ | I reopened this question because the underlying concept intrigues me. I don't think it is a good idea necessarily, but it is certainly worthy of a question. | |
| Jan 12, 2013 at 3:31 | answer | added | maple_shaft♦ | timeline score: 7 | |
| Jan 12, 2013 at 3:30 | history | reopened | maple_shaft♦ | ||
| Jan 12, 2013 at 3:23 | history | closed |
Walter CommunityBot Jim G. Yusubov |
not constructive | |
| Jan 12, 2013 at 1:19 | history | edited | maple_shaft♦ | CC BY-SA 3.0 |
Removing NC bits and pieces
|
| Jan 11, 2013 at 23:57 | review | Close votes | |||
| Jan 12, 2013 at 3:23 | |||||
| Jan 11, 2013 at 23:40 | history | edited | Walter | CC BY-SA 3.0 |
fixed grammar
|
| Jan 11, 2013 at 23:12 | review | First posts | |||
| Jan 11, 2013 at 23:20 | |||||
| Jan 11, 2013 at 22:53 | history | asked | bond | CC BY-SA 3.0 |