|
Hi Afzaal,
Cool Answer 
|
|
|
|
|
Thanks for the link. It's always useful to read a different perspective on an important subject.
If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time - a tremendous whack.
--Winston Churchill
|
|
|
|
|
|
No, the most boring activity a developer can be involved in is a four hour meeting you have to attend, of which the last five minutes are relevant to your job. If you are lucky.
And then someone will say "oh, just one other thing..." And that'll add another hour or two.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You can't be sure enough that you're properly utilizing dynamic multidisciplinary channels to authoritatively cloudify end-to-end imperatives.
Just saying.
|
|
|
|
|
I think we'd better run that up the flagpole and see if anyone salutes it.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
You are absolutely right!
Behzad
|
|
|
|
|
Don't treat it as religious dogma. Ignore silly "rules" (which are just "some guy who thinks he has figured out software development said so, so it must be true").
Write unit tests because without them you might accidentally break things.
|
|
|
|
|
Never, ever test your code, that way you have more time to write rubbish!
veni bibi saltavi
|
|
|
|
|
Nagy Vilmos wrote: Never, ever test your code, that way you have more time to write rubbish drink Gin!
FTFY!
OT: How did the dentist go?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Two deep rooted buggers removed with large pliers and 8 novacains
veni bibi saltavi
|
|
|
|
|
And when does the dentist get out of intensive care?
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Member 11547329 wrote: Is Unit Testing is most boring activity for Developer
Whenever I am bored doing programming, I ask myself, why can't the computer do this, which has led to some interesting tools over the years.
I still don't see why we don't have tools that generate the unit tests for us. I mean, it really isn't that hard if we were only to apply ourselves to the problem.
Marc
|
|
|
|
|
Marc Clifton wrote: I still don't see why we don't have tools that generate the unit tests for us.
Clickety[^]
/ravi
|
|
|
|
|
Ravi Bhavnani wrote: Clickety[^]
True, but I've never tried, as I expect to be disappointed.
Have you tried it?
Marc
|
|
|
|
|
No, I haven't tried it. I've been building my unit tests manually so far. Admittedly, I don't test every method and property - just (what I deem to be) points of failure.
/ravi
|
|
|
|
|
I haven't either; but it looks like it's just a test stub generator. You'd still have to do the hard work of writing any non-trivial setup code, and then actually writing meaningful test content. The one in VS08/10 was a major waste of time IMO; and it appears MS agrees with me since based on the comments there they yanked it from 2012.
I've also played a bit with MS's automagic unit testing tool back around the New Year. While it fell well short of its "cover your legacy code in a single button click" hype; if you're writing readily testable code now it seemed like it might be able to generate good test coverage of it. Things like non-trivial state setup, logic in winform event handlers, or classes with tight coupling to the file system all defeated it; unfortunately my un-unit tested legacy .net code is riddled with those constructs making it mostly useless to me. (Even aside from only having MSDN pro - and the feature apparently being limited to the rebranded Premium tier.)
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
I test my unit frequently...  Oh! You mean code! Ummm, yeah, I do that too. 
|
|
|
|
|
Boring beats staying up till 4:00am trying to fix a critical bug in production.
/ravi
|
|
|
|
|
Ravi,
I agree wid u.
I also face this problem several times.
|
|
|
|
|
|
I've never unit tested.
Unless running the program in a debugger, handing my keyboard to a small child, and telling them "Smash a ton of keys" counts. 
When I talk to people who don't even know what source code is, I open an editor window and say "This is what we go through every time you find a bug!"
|
|
|
|
|
No, there are worse things many times more boring than unit testing.
Like spending three months looking for a decent job because your last company imploded due to all the unfixed bugs.
Like spending a week hunting for a bug in your colleague's code who thought unit testing was boring so he didn't bother.
Like waiting six months for your cool new feature to go live because your testing organization only does system test, and therefore can only afford to release twice a year.
|
|
|
|
|
A related question is: are there any studies that show implementing unit testing and TDD has decreased the number of bugs in released programs than old-fashioned testing methods?
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
Well, problem is a problem[^].
The sh*t I complain about
It's like there ain't a cloud in the sky and it's raining out - Eminem
~! Firewall !~
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
