Skip to main content

Timeline for trust factor in code review

Current License: CC BY-SA 3.0

15 events
when toggle format what by license comment
Jun 29, 2016 at 15:11 history protected gnat
Jun 29, 2016 at 15:05 answer added Toby Speight timeline score: 0
Jun 27, 2014 at 3:36 review Close votes
Jun 27, 2014 at 15:49
Jul 13, 2011 at 7:14 comment added Marjan Venema Remain impartial. You wouldn't want testers not to test just because of some developers rep to always get it right and then miss something important that blows up in your most important client's face. So test, but don't take on the testing responsibilities of the programmer nor those of the testing team. When doing reviews I run a couple of cases to ensure that the testers/QA do not have to send it straight back to development, but the programmer remains responsible for being confident that the testers/QA won't find anything.
Jul 12, 2011 at 22:44 vote accept hari
Jul 12, 2011 at 20:16 answer added tehnyit timeline score: 2
Jul 12, 2011 at 20:00 answer added BillThor timeline score: 20
Jul 12, 2011 at 19:08 comment added rlb.usa If the reviewer asks for his code to be reviewed, by all means, test it!
Jul 12, 2011 at 19:06 answer added Sparky timeline score: 5
Jul 12, 2011 at 18:51 comment added S.Lott It's not "tricky". Unless you're God, you can never know if all test-cases are needed to cover all possible corner-cases. Since you can never know this, it's not "tricky".
Jul 12, 2011 at 18:49 comment added hari @S.Lott: Good hint. But thats again pretty tricky. I (being a reviewer) might not know what all test-cases are needed to cover all possible corner-cases.
Jul 12, 2011 at 18:46 answer added JB King timeline score: 0
Jul 12, 2011 at 18:45 answer added Jarrod Nettles timeline score: 0
Jul 12, 2011 at 18:44 comment added S.Lott No unit test results? Why not?
Jul 12, 2011 at 18:39 history asked hari CC BY-SA 3.0