<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 27, 2013 at 11:44 AM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">I don't like the way the tests are written anyway though: I don't like<br>
</div></div>
unit tests crawling through the UI. I'd rather see tests that checked<br>
the instvars containing the class list etc.<br></blockquote><div><br></div><div style>These days, the way to do it would be to use ToolBuilder-SUnit. It provides trivial widget implementations that don't do anything but expose their state. So you can make assertions about what the UI is displaying, and easily simulate clicks etc, without having to deal with actual morphs. </div>
<div style><br></div><div style>Colin </div></div></div></div>