|
|
PyUnit
I took a look at PyUnit this weekend, and it looks just like JUnit. Except I don't understand it, because I don't speak Python. But the structure is the same, which is funny because it still seems completely incomprhensible if you haven't worked with it. Somebody needs to sit down and write out a nice high-level diagram, in English with pictures, discussing how the different parts fit together. I wonder how others are fairing.
I did some more reading about stories and it looks like we've got the detail level pretty much exactly right on the stories. I'll add a tad more detail when I create the master story file.
Dave says he's done, with Zope installed and a page coming up, but we can't see it. I got a page coming up, and certainly the message is configurable, and being stored somewhere. But I'm not really sure I understand how the database works. So, I'm going to extend it out a little bit and create another page. This page will create a "message" object that is referenced by a tag. Then, when you pass the tag to the display screen, it presents the appropriate message. The question will be then, if I shut Zope down and bring it up, will all the created objects come back with it. In theory, I think that's how it works. But I'm not sure.
If it does work this way, I've got some real questions, mainly concerning memory usage. Will it swap necessary objects in and out, or try to store them all in memory? I'm also wondering how you query. Is there no such thing as traditional SQL querying then? Is a query pretty much always just creating and iterating through some sort of list structure? I guess we'll find out as we learn more.
|
|
|
|
Post a Comment
<< Home