title: Applying CQRS - Is unit testing the thin read layer necessary?
body: <p>Given that some of the advice for implementing CQRS advocates fairly close-to-the-metal query implementation, such as ADO.NET queries directly against the database (or perhaps a LINQ-based ORM), is it a mistake to try and unit test them?</p>
  
  <p>I wonder if it's really even necessary?</p>
  
  <p>My thoughts on the matter:</p>
  
  <ol>
  <li>The additional architectural complexity to provide a mockable "Thin Read Layer" seems opposite to the very nature of the advice to keep the architectural ceremony to a minimum.</li>
  <li>The number of unit tests to effectively cover every angle of query that a user might compose is horrendous.</li>
  </ol>
  
  <p>Specifically I'm trying CQRS out in an ASP.NET MVC application and am wondering whether to bother unit testing my controller action methods, or just test the Domain Model instead.</p>
  
  <p>Many thanks in advance.</p>