Hello All,<br><br>I&#39;m new to the list here, and I have a question on creating SUnit tests for Morphs. In my latest bi-annual &quot;Squeak Peek&quot;, something clicked that hadn&#39;t in the past 3 years of periodically checking into Squeak: It started to make sense (I usually give up in frustration after a week or so, but the, &quot;Squeak by Example&quot; book has really helped this time. Kudos to the writers). <br>
<br>So, I started digging around in the Morphic classes, and I stumbled across, what appeared to be, a bug in LedDigitMorph. I played around with it until I felt satisfied that it was indeed a bug, and then submitted a report to <a href="http://bugs.squeak.org">bugs.squeak.org</a>. The powers that be agreed that this looked like a bug, and asked me to do a little more footwork on it (I had submitted my fix with the report). However, I&#39;m not quite sure how to accomplish what was requested.<br>
<br>Here&#39;s the bug (mantis ID: 
		0007067), and a test case:<br><br>LedDigitMorph does not change its state after receiving a digit:
message. You have to click on the morph before it changes. The test
case is:<br>
<br>
myDigit := LedDigitMorph new openInWorld.<br>
myDigit digit: 2.<br><br>The morph will not show the number 2 until you click on it.<br><br>I solved this bug in my image by changing the digit: message to this:<br><br>
digit: anInteger<br>
<br>
&nbsp;&nbsp;&nbsp;&nbsp;digit _ anInteger \\ 10.	&quot;make sure it stays between 0 and 9&quot;<br>
&nbsp;&nbsp;&nbsp;&nbsp;self changed.<br><br>The response I got back asked me to create a SUnit test for this issue (One that fails before the patch and passes afterwards).<br><br>Unfortunately, I&#39;m not sure how to do this (though I&#39;d be happy to continue to work on it). Can someone give me some guidance on how to go about creating SUnit test cases for this Morphic object?<br>
<br>Thanks,<br><br>Jason<br>