1,516 reputation
516
bio website jimmykeen.net
location
age
visits member for 2 years, 6 months
seen Feb 8 at 22:19

Lurking somewhere around unit testing tag...

...and on top of that, I now run unit testing-themed C#/.NET blog. If you ever wondered:

You might find few answers there!


Jan
30
awarded  Nice Answer
Oct
22
awarded  Yearling
Mar
18
awarded  Booster
Mar
16
awarded  Announcer
Dec
2
accepted Documentation degrading - how to deal with it?
Nov
8
comment Does the “one assertion per test” rule apply for checking initial conditions?
@pdr: I don't consider it (rule) outdated and overkill, I'm saying that it should be taken with caution and more as a guideline than rule. It all narrows down to what you understand under one assertion. Applying it literally to every test might quickly backfire (but that's true to any rule). Care to hint where I sound as if everyone was agreeing with me, as that was not intention of my post?
Nov
8
answered Does the “one assertion per test” rule apply for checking initial conditions?
Oct
25
comment Are injectable classes allowed to have constructor parameters in DI?
@Downvoter: adventurous enough to share knowledge which led you to decision this answer is incorrect?
Oct
25
revised Are injectable classes allowed to have constructor parameters in DI?
lost parser dependency
Oct
25
answered Are injectable classes allowed to have constructor parameters in DI?
Oct
22
awarded  Yearling
Oct
17
comment Pair programming and unit testing
Most large software houses have manual testers and automated tests teams. But I have never seen separate team for unit tests, as those are programmer-only tests, wrote by the very same guys who write code.
Oct
17
answered Pair programming and unit testing
Oct
3
revised TDD - Outside In vs Inside Out
typo
Sep
28
awarded  Nice Answer
Sep
27
revised TDD - Outside In vs Inside Out
fixed bit repetitive descriptions and added links to sources
Sep
27
answered TDD - Outside In vs Inside Out
Sep
11
awarded  Nice Answer
Aug
17
comment Sporadic unittests or TDD?
@CesarGon: OP mentioned sporadic testing which, as I understand, is writing unit test when you feel it matters. Instead, one could start with TDD and decide when not to write unit test. After all, it's much easier to determine that "this code has small chances of breaking, so I skip test" (because you wrote similar code many times) rather than "this code will break, so I write test" (it's essentially the same story as is it a bug when you know about it upfront issue I mentioned). That's what I meant by full testing; do selection, but not when to write, but rather when not to write.
Aug
13
comment Sporadic unittests or TDD?
@CesarGon: Nowhere in this post I claimed that (nobody ever claims that, this is prime example of straw man argument). Heck, I even explicitly stated OP should not follow "delusive magical-fairy-tale 100%" coverage.