anchor.diff:      <cfargument name="Args" required="true" type="struct">
       <cfset var s_args = StructNew()>
   
  -    <cfif this.TestStyle eq "default">
  +    <cfif variables.TestStyle eq "default">
         <cfreturn args>
       </cfif>
   
  
positive.code: <cfcomponent displayname="Assert"
               hint="Main component for asserting state. You will not generally need to instantiate this component directly - the framework makes it available for your TestCases. Use this to see what assertions are available and note that it can easily be extended using the Assert.addDecortor() method or by editing the mxunit-config.xml file, following the examples therein.">
  
    <cfparam name="this.TestStyle" default="default">
  
  	<cfset clearClassVariables()>
  
  	<cffunction name="clearClassVariables" access="public">
  		<cfset this.expected = "">
  		<cfset this.actual = "">
  	</cffunction>
  
    <!--- Constructor;  named init instead of Assert because BlueDragon has a built-in
  
negative.code:   <!--- convenience (sort of...maybe) for enabling users of cfunit to convert their stuff without terrible pain. a test case would need to use setTestStyle('cfunit') in the constructor or setUp method of a test --->
    <cffunction name="setTestStyle" access="public" hint="Sets the current test style.">
      <cfargument name="TestStyle" type="string" required="true" hint="Use 'default' to have the framework behave like cfcunit with respect to arguments; otherwise, pass 'cfunit' to behave like cfunit (i.e. for certain assertions, the message is the first arg). This only affects assertEquals and assertTrue">
      <cfset variables.TestStyle = arguments.TestStyle>
    </cffunction>
  
    <cffunction name="getTestStyle" access="public" output="false" hint="returns the current test style">
      <cfreturn variables.TestStyle>
    </cffunction>
  
    <cffunction name="fail" access="public" returntype="void" static="true" hint="Fails a test with the given MESSAGE.">
  