ISerializable - Roy Osherove's Blog

I’m trying out something new. You can check it out here.

as usual, the book link list can be found here.

as usual, the book link list can be found here.

You can find the list of books with links over here:

http://osherove.com/books-i-like

I was fiddling around with the typemock API, see what it would belike to use it in a more MOQ like manner:

to support this, all the code you need, including the Faker class exists here. you’d need to reference the typemock dll and the typemock c# API dll to make it work.

I’m not sure I’m crazy about it, but it is shorter. I’m not sure it’s as readable, though.

what’s it about? in one word: productivity.

Here's what it does:

(here's the full info)

it’s late at night, and my new baby just went to sleep, again.

Time for another test review! (you can find other test reviews here)

Test Review - MEF from Roy Osherove on Vimeo.

I’ve stopped using Internet Explorer – Too damn slow, memory hogging beast.

I’ve stopped using FireFox, for the same reasons, funnily enough (until I found out about the security flaw).

I’m now using Safari – it’s blazing fast, reliable and does not have that aweful security risk that Chrome does.

What is it?

Google Chrome will reveal your saved passwords to anyone who wants them, with no possibility of securing them with a master password. The image below shows what happens when I use Chrome to save my password for gmail, I can then just go an open chrome options, click “Show Saved passwords” and select a line there, and click “Show password” (in the image that button is titled “Hide password” after clicking it.

With Firefox, the default behavior is to allow anyone to see your passwords as well, but you can actively choose to use a master password in firefox to make this less accessible. the default is that it’s open for anyone to see. With Chrome, there isn’t even a “master password” option.

Until they fix this, I am not going to use Chrome, I don’t care how fast it is. Safari is fast and doesn’t show my passwords.

K THX BY

Time for the bi-annual frameworks poll!

Update: added the difference from integration tests at the end of the post.

Here’s my latest definition of what a unit test is:

A unit test is a fast, in-memory, consistent, automated and repeatable test of a functional unit-of-work in the system.

A unit of work is any functional scenario in the system that contains logic. it can be as short as a function, or it can span multiple classes and functions, and it provides internal or business value to the system under test.

how is it different that an integration test?

An integration test usually is not in-memory: it may touch the disk file system, databases, registry or other shared resources.  It may read or need a configuration file of the file system, wheas a unit test can be fully configured in-memory, for example.

An integration test will usually run much slower because it does not run in-memory.

An integration test can be less consistent – it may use threads or random number generators so that the result of the test is not always consistent.