Re: [Pybeep-devel] Mockobjects and Interfaces.

[Gabe W. <gw...@wa...>]

Is it appropriate to move all the Mock classes? It seems like some of the
Mock classes are very specific to certain test cases, and by putting them
together separate from the test cases they are associated with, you are
creating some issues about maintenance. Not a big issue, just thought I'd
bring it up....

	-Gabe

On 14 Feb 2002, Sean Allen wrote:

> Finally got my time back ;-)
>
> In the test/
>
> moved all the Mock* classes into their own module as it was going to get
> messy later. Did a little work on the Session test.
>
> To foster some discussion:
> Although this is very early. Has anybody( i.e. people who aren't Gabe or
> me.) had any thoughts as to what kind of interface they would like for
> the library. I'm not trying to solicit detailed designs, but rather a
> feel of what kind of utility classes might be useful once we get the
> core working. Just to look at who may want to do what with this.
>
> Sean Allen
>
>
>
>
>

-- 
Gabe Wachob                   gw...@wa...
Personal                   http://www.wachob.com
CTO, WiredObjects    http://www.wiredobjects.com