Skip to main content
15 events
when toggle format what by license comment
Feb 12, 2019 at 14:46 answer added Gaurav Srivastava timeline score: 1
Feb 26, 2014 at 4:52 answer added Yawar Amin timeline score: 0
Feb 5, 2014 at 22:03 answer added guillaume31 timeline score: 2
Feb 5, 2014 at 20:33 answer added JeffO timeline score: 1
Feb 5, 2014 at 20:00 answer added MikeSW timeline score: 0
Feb 5, 2014 at 19:34 answer added DougM timeline score: 1
Feb 5, 2014 at 19:22 answer added pnvn timeline score: 1
Feb 5, 2014 at 11:17 comment added Marjan Venema Doesn't measure whether you are "doing TDD", but a good articles on test metrics nonetheless: Selecting Developer Testing Metrics
Feb 5, 2014 at 8:20 comment added Bart van Ingen Schenau If it is just to satisfy the bean counters: commit the tests before and separately from the code. The earlier commit times are an indication that the tests were likely written first.
Feb 5, 2014 at 4:33 history tweeted twitter.com/#!/StackProgrammer/status/430922012094398464
Feb 5, 2014 at 0:42 answer added combinatorics timeline score: 16
Feb 5, 2014 at 0:41 answer added Reactgular timeline score: -1
Feb 5, 2014 at 0:30 comment added Frank Hileman Your question brings up an interesting point; does TDD (rigid) make any measurable, objective difference in development? So many development methods are untested in objective terms. You may actually get some data. If the use of TDD is un-measurable...
Feb 5, 2014 at 0:01 comment added Fabinout Junior Developper here: Maybe set steps with your manager. such as 1) write tests depending solely on specifications. 2)the coordinator/Project Manager checks that they comply with the specifications; 3) Developper can start. That may be slow a first glance, at least, it will show which specifications are poor or well-written.
Feb 4, 2014 at 23:49 history asked Vaccano CC BY-SA 3.0