Reputation
3,529
Top tag
Next privilege 5,000 Rep.
Approve tag wiki edits
Badges
12 14
Newest
 Guru
Impact
~58k people reached

  • 0 posts edited
  • 2 helpful flags
  • 231 votes cast
Dec
18
awarded  Guru
Dec
16
comment Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
@VincentSavard fair enough - edited the answer to make it clearer.
Dec
16
revised Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
added 698 characters in body
Dec
16
comment Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
@VincentSavard: Frankly, I'd be surprised if OP's friend is that critical about unit tests per se. Rather I'd gather he's pragmatic and observing that unit tests that get written in practice are mostly pointless, and this got lost in translation. Quoting: "unit tests tend to be commented out rather than reworked". To me there's an implicit message in there - namely, that if they tend to need reworking it is that they were poorly written to begin with. Assuming so, the second proposition follows: developers would waste less time writing code that is harder to get wrong - i.e. integration tests.
Dec
16
awarded  Good Answer
Dec
12
comment Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
@DocBrown: Indeed not. What I meant is, it's so often done wrong that OP's colleague has it correct in most cases - or at least in all cases I've ever run into in unit-test obsessed companies.
Dec
12
comment Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
@AndresF. - Agreed fully. Trouble is, there's a ocean of developers out there who don't understand this and end up, well, unit testing a lot more than they should - mindlessly. If anything, the issue is tied to test coverage considerations. They often lead to more mindless unit testing.
Dec
12
awarded  Nice Answer
Dec
12
revised Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
added 66 characters in body
Dec
12
answered Is it reasonable to not write unit tests because they tend to get commented out later or because integration tests are more valuable?
Sep
23
awarded  Nice Answer
May
10
awarded  Yearling
Apr
23
awarded  Good Answer
Apr
23
comment Does using a database server make sense if the application only does things locally?
@DocBrown -- and the short answer is: it doesn't make any sense unless you're dealing with outsized data sets or in need of concurrent writes. (Or, for obvious reasons, in need of something SQLite doesn't offer.) Again, feel free to edit the answer if that point is unclear to you.
Apr
23
comment Does using a database server make sense if the application only does things locally?
@DocBrown: Specific cases where you should use a client/server RDBMS are [see answer]; for everything else SQLite works fine. I'm not sure what's unclear in there, so feel free to edit the answer if you believe it's needed.
Apr
21
awarded  Nice Answer
Apr
21
revised Does using a database server make sense if the application only does things locally?
added 8 characters in body
Apr
21
revised Does using a database server make sense if the application only does things locally?
edited body
Apr
21
answered Does using a database server make sense if the application only does things locally?
Sep
24
awarded  Autobiographer