Writing Testable ArcObjects Applications - Part 3 - Unit Test Structure

In the previous post I described the concept of inversion of control and how to decouple classes from their dependencies using interfaces.  The objective of doing this is to make the business logic more testable, which now brings us to testing.  However, before I jump into mocking ArcObjects code, in this post I will discuss the structure of tests, which will give some context to the unit tests I will discuss in the next topic.

Writing Testable ArcObjects Applications - Part 2 - Inversion Of Control

In my last blog post I introduced the subjects of Inversion of Control (IoC) and Mocking for unit testing, and this week, as promised, I will now delve into more specific detail about applying these concepts to applications written using ArcObjects.

My focus in this article will be designing code using the SOLID principle of Dependency Inversion, and the use of Inversion of Control (IoC) frameworks for wiring applications up at runtime.

Writing Testable ArcObjects Applications - Part 1

Having previously worked in a software product development company for a number of years, and now back working with Esri technology again, I have been a little surprised by how few internet articles there are related to Unit Testing, Mocking, and Inversion of Control for applications built with ArcObjects, so I thought it might be fun to do a multiple article series on writing testable applications using ArcObjects.

Green Framing All The Things!

This will appear to be a strange subject to post about considering my other content, but I recently went through a positive thinking reset, and I was surprised and amazed by some of the results, so I thought I would share.