anchor.diff:  %% @todo Explain in documentation why we use a process to handle test input.
   %% @doc etap is a TAP testing module for Erlang components and applications.
   %% This module allows developers to test their software using the TAP method.
  -%% 
  +%%
   %% <blockquote cite="http://en.wikipedia.org/wiki/Test_Anything_Protocol"><p>
   %% TAP, the Test Anything Protocol, is a simple text-based interface between
   %% testing modules in a test harness. TAP started life as part of the test
   %% harness for Perl but now has implementations in C/C++, Python, PHP, Perl
   %% and probably others by the time you read this.
   %% </p></blockquote>
  -%% 
  +%%
   %% The testing process begins by defining a plan using etap:plan/1, running
   %% a number of etap tests and then calling eta:end_tests/0. Please refer to
   %% the Erlang modules in the t directory of this project for example tests.
  
positive.code:                 count = State#test_state.count + 1,
                  pass = State#test_state.pass + 1
              };
              
          {_From, fail, Desc} ->
              FullMessage = skip_diag(
                  " - " ++ Desc,
  
negative.code: %% WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
  %% FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
  %% OTHER DEALINGS IN THE SOFTWARE.
  %%
  %% @author Nick Gerakines <nick@gerakines.net> [http://socklabs.com/]
  %% @author Jeremy Wall <jeremy@marzhillstudios.com>
  %% @version 0.3.4
  