<div class="gmail_quote">On Wed, Jun 17, 2009 at 3:45 PM, Michael Lucas-Smith <span dir="ltr"><<a href="mailto:mlucas-smith@cincom.com">mlucas-smith@cincom.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
4 unit test failures:<br>
WACodecTest>>testCodecLatin1Binary<br>
WACodecTest>>testCodecUtf8Binary<br>
WACodecTest>>testCodecUtf8Bom<br>
WACodecTest>>testCodecUtf8ShortestForm</blockquote><div><br></div><div>Not bad.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
One unexpected functional test failure:<br>
WAClosureFunctionalTest -- "Go with ensure" runs the ensure block immediately<br>
</blockquote><div><br></div><div>From memory, I think this "fails" everywhere. Ensure doesn't work well with continuations; it operates at the level of the current request and does *not* span multiple requests in a task.</div>
<div><br></div><div>The functional tests aren't necessarily pass/fail tests; in many cases they are simply ways to exercise certain behaviour so we can easily test out different parts of the system. We usually try to document on the page what the "expected" behaviour is on most systems to make it easier for people who don't know the tests as well. I'm guessing in this case, the expectation isn't documented... feel free to add that.</div>
<div><br></div><div>Julian</div></div>