Skip to main content

Timeline for Do I need to test everything?

Current License: CC BY-SA 3.0

32 events
when toggle format what by license comment
Nov 2, 2015 at 11:50 comment added Filip Bartuzi It's been 3 years now... how was your TDD project? :)
Apr 28, 2012 at 19:56 comment added Evan Plaice Wait until you decide to re-structure your code. Any time massive changes are introduced, you need to verify functionality. Without tests you'll need to go through your application and test all of the functionality manually. Introduce another large update and you'll have to do it again. Unit tests are just a 'cheap' way to make sure everything is working as expected.
Apr 28, 2012 at 12:33 answer added hwjp timeline score: -1
Mar 22, 2012 at 22:02 comment added Erik Reppen And I'll be your TDD stick in the mud for today. And no I'm not advocating no automated testing whatsoever. TDD is in fact an actual specific coding strategy, not just declaring that testing is necessary.
Mar 22, 2012 at 21:32 answer added Erik Reppen timeline score: 0
Mar 12, 2012 at 19:17 comment added Ben Lee Don't test if you don't understand the value, it's that simple. If you don't get it, your tests will not be effective anyway, and may actually give a false sense of safety. As @ZJR pointed out, eventually you'll either see a reason for testing and just get it, or you won't. Until you see a reason, don't test.
S Mar 11, 2012 at 16:19 history suggested Peter Mortensen CC BY-SA 3.0
Copy edited. Shortened. Added context.
Mar 11, 2012 at 16:11 review Suggested edits
S Mar 11, 2012 at 16:19
Mar 10, 2012 at 21:10 vote accept Matteo Pagliazzi
Mar 10, 2012 at 3:07 comment added ZJR Not seeing the real advantage in writing tests and writing them out of blind faith doesn't really sound right. Go on without writing tests, after a while you'll experience an unexpected regression and know why you're testing.
Mar 9, 2012 at 23:53 answer added Chriseyre2000 timeline score: 2
Mar 9, 2012 at 23:17 comment added Mason Wheeler For some reason, this question makes me want to post an image macro of Captain Nero yelling "TEST EVERYTHING!!!"
Mar 9, 2012 at 22:59 answer added Paul Biggar timeline score: -1
Mar 9, 2012 at 21:32 answer added jamesc timeline score: 2
Mar 9, 2012 at 20:51 history tweeted twitter.com/#!/StackProgrammer/status/178221608056524800
Mar 9, 2012 at 20:48 comment added Paul @JonStrayer: Yes, it's the same question
Mar 9, 2012 at 20:18 history edited java_mouse
edited tags
S Mar 9, 2012 at 19:31 history suggested Andy
not specific to RoR
Mar 9, 2012 at 19:26 vote accept Matteo Pagliazzi
Mar 9, 2012 at 21:53
Mar 9, 2012 at 19:26 review Suggested edits
S Mar 9, 2012 at 19:31
Mar 9, 2012 at 18:13 comment added jcmeloni I don't know that this is exactly a duplicate question, but there are some great answers in What are the disadvantages of test-first programming? and When is it appropriate to not unit test?.
Mar 9, 2012 at 17:50 answer added NoChance timeline score: 2
Mar 9, 2012 at 17:49 comment added pdr @JonStrayer: Is it? Are you certain the answer would be the same for RoR as .NET? I would suggest that by design RoR has deliberately reduced the cost of testing, while not having type-safety in the form of a compiler massively increases the benefit of testing.
Mar 9, 2012 at 17:43 history edited Matteo Pagliazzi
edited tags
Mar 9, 2012 at 17:42 comment added Jon Strayer This really isn't a ruby on rails question. it's more of a TDD question.
Mar 9, 2012 at 17:42 answer added Schleis timeline score: 3
Mar 9, 2012 at 17:41 answer added Jon Strayer timeline score: 49
Mar 9, 2012 at 17:06 answer added Bruce Ediger timeline score: 8
Mar 9, 2012 at 16:58 answer added Doug T. timeline score: 34
Mar 9, 2012 at 16:58 answer added wessiyad timeline score: 1
Mar 9, 2012 at 16:55 history edited user28988 CC BY-SA 3.0
added 1 characters in body
Mar 9, 2012 at 16:54 history asked Matteo Pagliazzi CC BY-SA 3.0