While transitioning to writing IG-XL test programs in .NET, specifically in C#, the move from procedural programming to object-oriented programming is taking place. A major part of this transition is consideration of this question, “What is a Test Method?” This paper dissects the traditional monolithic test method and transforms it into a composition of smaller methods. There exists multiple drivers for this architectural transition. The first of which is to leverage object-oriented programming techniques made available in .NET and C#. Next, the need for fully vetted reuse libraries is driving more generic solutions, as well as Unit Testing. However, not every piece of the test method content should be part of the reuse library. Instead, some pieces should exist in the device-level code so that is can be customized by each team and even each Product Engineer. So, we will consider the components of a test method and access what content needs to be library code and what content needs to be carved out of the library, effectively splitting the traditional test method into smaller parts that don’t all live in the same place. This architectural shift optimizes both reuse and flexibility.