Test Automation Articles - Steve Fenton

Skip to Navigation or
Skip to Content

Test Automation Articles

2013

My Unit Testing Epiphany Continued (2013)
My Unit Testing Epiphany (2013)

2012

Great New Testing Features in Visual Studio 2012 (2012)
Keeping Your Test Suite Fast (2012)
Why Too Many UI Tests Prevents Change (2012)
Fakes, Stubs and Shims in Visual Studio 2012 (2012)
Unit Tests Should Test One Thing (2012)
Modularising JMeter Tests (2012)
Mocking A Service Proxy In .NET With Rhino Mocks (2012)
Unit Tests Should Have Predictable Results (2012)
Combining Enhance PHP And Codespy For Code Coverage (2012)

2011

Some Handy NCrunch Tips (2011)
Slides From Test Driven Development (2011)
Software Craftsmanship And Unit Testing (2011)
Using NCover Exclusions With MSBuild (2011)
Using NCover With MSBuild To Get Reports And Trends (2011)
Adding An NCover Target To MSBuild To Get Code Coverage (2011)
Database Integration Testing With Enhance PHP (2011)
PHP Enhance Unit Testing Framework Mocks And Stubs (2011)
PHP Enhance Unit Testing Framework Full Example (2011)
PHP Enhance Test Framework First Look (2011)
PHP Unit Testing Frameworks (2011)
How I Name My Unit Tests And Why (2011)
We Need To Practice Explaining Test Driven Development (2011)

2010

Mocking NHJump In Your Unit Tests (2010)
Get NMock2 To Return Out Params (2010)

You Are Here: Home » Blog » Test Automation Articles

More

Understand The Intent Before Making Changes

There is a clever pattern in domain-driven-design whereby you create an object to represent identifiers in your model. For example, if you have a Client object, you replace the numeric id with an object called ClientId.

The reason for this is that it prevents incorrect ids being passed to method, because the methods don't allow a general type, but require the specific id type.