[z3-five] Restructuring

[Philipp von Weitershausen]

Martijn Faassen wrote:
>> In Zope 3, there's a package hierarchy convention that is not too
>> flat to provide no structure whatsoever and not too deep to find
>> yourself lost in. Most importantly, tests are included along with
>> every package and can therefore be much more easily be associated
>> with the module or class they actually test. Right now, with a big
>> blobbish FiveTest product, this is almost never the case in Five.
> 
> 
> Since we're testing integration with Zope 2, I suspect our tests will
> always be rather functionally oriented and somewhat big/blobbish. I
> imagine they can be factored out a bit more, but I'm not sure how far we
> can sensibly go.

I see two kinds of tests in Five:

- Test whether a certain (re-)implementation we have in Five works in 
every aspect that its interfaces promise. That's clearly a unit test.

- Test that Zope 3 style components work smoothly within Zope 2. This is 
what you call "testing ingration with Zope2" above, I guess.

Right now, these two types of tests are interwoven. That makes it 
*extremely* hard to debug and to concetrate on one failing component. I 
think the former kind should be kept very close to the implementation, 
like in Zope 3. The latter kind woudl probably stay right where it is, 
most probably in one or more test products like we have it now. Having 
test products is also a good way of documentation...

>> I'll obviously be creating a branch for this. I don't believe in 
>> branches that live too long, though, so I'd like to come to the point
>>  where a certain state of satisfactory restructuring is reached and 
>> everbody is ok with it pretty soon.
> 
> We're currently working on Five 0.4, which is really a fairly minor
> tweak-version that we'd like to have integrated into Zope 2.8. After
> that we could merge the work.

Sounds very good to me. What's still missing for Five 0.4? How's the 
time line?

Philipp