Comments for The Cockney Coder

Comment on Using wrappers to aid unit testing by MarkG

MarkG — Wed, 01 May 2013 11:06:29 +0000

All those Moq It.Is() usages have bugged me somewhat, but still easier to understood (IMHO) than Rhino.

It’s a nice idea – looks like someone has been spending a fair bit of time playing with Simple.Data

The statically-typed part of me (the majority, to be fair!) immediately is concerned that a rename of the method being mocked won’t be reflected at compile-time. However, because this is a unit test, this isn’t really a problem. When the unit test runs, your dynamic wrapper will throw an exception because the method cannot be found.

Would I use it in code? Quite possibly. Support for the lambda Returns() syntax of Moq would be essential.

Comment on How do you unit test? by Isaac Abraham

Isaac Abraham — Mon, 04 Mar 2013 22:49:38 +0000

Absolutely. You can click “View Results” under any of the polls to see the current results anyway, but yes, I plan to blog about it in a few weeks (or once I have a reasonable set of data, whichever is first!).

Comment on How do you unit test? by Erik Dietrich (@daedtech)

Erik Dietrich (@daedtech) — Mon, 04 Mar 2013 22:46:45 +0000

Are you planning to publish the results when you’re finished? I’m curious to see how it breaks down and the conclusions you draw.

Comment on How do you unit test? by Isaac Abraham

Isaac Abraham — Mon, 04 Mar 2013 11:01:24 +0000

Been there, done that re: commercial reality And yes, I agree – it’s very difficult to justify the up-front cost of unit testing – particularly when the benefit can be intangible.

Comment on How do you unit test? by Isaac Abraham

Isaac Abraham — Mon, 04 Mar 2013 09:48:58 +0000

Mmmm. There’s only one question of the three that discusses “how” you write tests, and that gives you the option of the failing test first. Although as I write this that’s not the most popular option for that question anyway…

Comment on How do you unit test? by Richard Tappenden

Richard Tappenden — Mon, 04 Mar 2013 09:23:20 +0000

Not happy with the answers I had to give here. Given the opportunity, I would always go for the failing test first approach.

Comment on How do you unit test? by PokeADonkey

PokeADonkey — Sun, 03 Mar 2013 13:57:25 +0000

Unit test theory and in practice differs in my experience as does night and day. Tests are usually written as a quaility gate to a public method, e.g., on the business layer, to ensure it does what you want it to in general functional (requirements spec) terms not whether it is 100% fool proof and as a means of triggering alerts in the build process when developers screw something of yours up.

Time pressures in a commercial / small team environment always cause unit tests to fall into the “nice to have” category in the management view of priorities.

Unit tests when they are created serve little more than automated functional (I.e. Integration) tests, which is always the first and highest level of testing permitted.

This all of course is contrary to the ideals of unit testing and TDD which I aspire to; however I speak from an experienced commerial environment where “time is money” and always has to be justified.

Great blogs btw, keep it up

Comment on TypeScript exposes some irrational Microsoft hatred by Mil

Mil — Tue, 22 Jan 2013 08:53:45 +0000

Totally agree with you. Even as Crockford stated that he thinks TypeScript is a good choice to avoid some of JavaScripts problems there was a lot of BS comments about that. It’s quite sad actually.

Comment on CodeRush for beginners! by Isaac Abraham

Isaac Abraham — Wed, 02 Jan 2013 15:08:57 +0000

Hi Steve,

Thanks for the post. Yes, I found the same thing myself a few weeks ago – it’s not really that well documented though. Good idea re: dropbox – will do the same for myself with SkyDrive.

Cheers!

Isaac

Comment on CodeRush for beginners! by Stephen J.Brouillard (@NewCodeGeek)

Stephen J.Brouillard (@NewCodeGeek) — Wed, 02 Jan 2013 15:07:23 +0000

Isaac,

I just discovered your blog quite by accident as I was searching for a bit of CodeRush info. I’m also a fan and have been using CR for some time, though I feel that there’s still a great deal to learn about the product.

I realize that this is an old post, but thought I’d comment in case anyone else stumbles across it and can use the info.

Regarding your comment about being able to import/export the CR profile. While I agree that it would be nice to offer the option as a part of the menu, it really isn’t required. All the CR settings are stored as xml files. Wherever you store your CodeRush settings (I believe the default is in %UserProfile%\AppData\Roaming\CodeRush), there will be a settings.xml folder. All CodeRush settings are stored in xml files in the folder structure under here. If you want to export all settings, just make a copy of this structure. In fact, since I use multiple PCs to develop on, I changed the location of the settings data to a DropBox folder, so now all my CodeRush Settings are synced between PCs as I change them automatically. You can do the same by going into the CodeRush Settings Window and navigating to Core\Settings and changing the folder there.

I hope someone finds this helpful.

Cheers,

Steve (@NewCodeGeek)