﻿<?xml version="1.0" encoding="utf-8"?><rss version="2.0"><channel><title>Ayende @ Rahien</title><link>http://ayende.com</link><description>Ayende @ Rahien</description><copyright>Copyright (C) Ayende Rahien  2004 - 2021 (c) 2026</copyright><ttl>60</ttl><item><title>Jeff Brown commented on Test Responsabilities</title><description>Indeed.  Unit tests should be simple and straightforward wherever possible.
  
  
The goal of a good unit test framework should be to isolate non-essential testing concerns (such as specifying mock object behavior) so that the bulk force of the testing effort can be brought to bear on the essential problem: specifying the expected outcome.
  
  
To that end, test patterns, factories, constraints, indirection, and other techniques should largely be applied with the objective of clarifying the expression of the test specification, of validating the intent of the test itself, or of facilitating diagnostic efforts to identify the cause or extent of a failure.  Thus can the provision of advanced features such as DSLs, models, declarative markup, and rich reporting be justified.
</description><link>http://ayende.com/2247/test-responsabilities#comment1</link><guid>http://ayende.com/2247/test-responsabilities#comment1</guid><pubDate>Sat, 24 Mar 2007 22:03:04 GMT</pubDate></item></channel></rss>