Re: [Tutor] Unexpected Behavior in unittest

2006-03-01 Thread Carroll, Barry
TED] > Sent: Tuesday, February 28, 2006 2:57 PM > To: Carroll, Barry > Cc: tutor@python.org > Subject: RE: [Tutor] Unexpected Behavior in unittest > > > > > I wish it were that simple. 'test3.py' is the name of the file > > containing the test case clas

Re: [Tutor] Unexpected Behavior in unittest

2006-02-28 Thread Danny Yoo
> I wish it were that simple. 'test3.py' is the name of the file > containing the test case class. I left the invocation out of my output > excerpt. It should look like this: Hi Barry, Ok. But still go back and make sure you're running the right file. The error message says that: > Trace

Re: [Tutor] Unexpected Behavior in unittest

2006-02-28 Thread Carroll, Barry
AIL PROTECTED] 541-302-1107 We who cut mere stones must always be envisioning cathedrals. -Quarry worker's creed > -Original Message- > From: Danny Yoo [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 28,

Re: [Tutor] Unexpected Behavior in unittest

2006-02-28 Thread Danny Yoo
> In this case, the assignment to lg.cs failed. > >> > F > == > FAIL: test_cs (__main__.cs_tryout) > -- > Traceback (most recent call last): >

[Tutor] Unexpected Behavior in unittest

2006-02-28 Thread Carroll, Barry
Greetings: This is a fairly long-winded question. I beg your indulgence. I am writing unit tests for our bar code scanner test software, and I have encountered some results that I cannot explain nor get around. Here is the scenario. Our program implements a generator class for creating 'la