| 1 |
On Thursday 27 November 2003 17:42, Jason Mobarak wrote: |
| 2 |
> Somethings you need to do to get up to speed on unit tests: |
| 3 |
> |
| 4 |
> 1) Read the documentation for the unittest module in the Python standard |
| 5 |
> library. |
| 6 |
> 2) Read http://pyunit.sourceforge.net/pyunit.html |
| 7 |
> 3) Get a CVS CO of Twistedmatrix.com's CVS and look over how they do there |
| 8 |
> unit tests, they use their own implementation of unittest but the |
| 9 |
> differences are minor |
| 10 |
|
| 11 |
All complete. I didn't read every line of twisted's unittests but I get the |
| 12 |
idea. I've also kept it for a reference. |
| 13 |
|
| 14 |
> On 17:03 Thu 27 Nov , Jason Stubbs wrote: |
| 15 |
> > I think there's two ways to attack it: |
| 16 |
> > |
| 17 |
> > a) I work through documenting everything while you work through |
| 18 |
> > separating everything that's documented. Once the documenting is done, I |
| 19 |
> > can begin unit testing and you can join me once the separation is done. |
| 20 |
> > b) You document and separate and I unit test what has been completed. |
| 21 |
> |
| 22 |
> I like (b), |
| 23 |
> |
| 24 |
> > BTW, will this work become redundant by portage-ng? |
| 25 |
> |
| 26 |
> I hope after portage is separated into a library the code can be |
| 27 |
> incorporated into "portage-ng", we could very well be working on the |
| 28 |
> beginnings of the next generation of portage. I want to add "layers" to how |
| 29 |
> everything interacts, key design patterns being heavy focusing on "plug-in" |
| 30 |
> orientation and model-view-control. Some keywords you should research if you |
| 31 |
> are interested in this are Mix-In style programming and the use of |
| 32 |
> interfaces to abstract aggregate interaction between sections of a program. |
| 33 |
> |
| 34 |
> "Portage-ng" is being touted as a complete rewrite currently (from what I |
| 35 |
> remember) and it seems senseless to throw away the 10k lines of code that |
| 36 |
> make up the current portage system. |
| 37 |
|
| 38 |
Well, it seems it is a complete redesign from scratch, but the complete |
| 39 |
rewrite will be much longer coming. If you are still interested in continuing |
| 40 |
your work, I'm still interested in helping. If we do it properly, it should |
| 41 |
not be too difficult to remodel it to fit the design spec of portage-ng once |
| 42 |
it is completed. The components can be replaced by more advanced versions |
| 43 |
later if need be, but as you say there's no point in throwing 10k lines of |
| 44 |
code away. |
| 45 |
|
| 46 |
Regards, |
| 47 |
Jason Stubbs |
| 48 |
|
| 49 |
-- |
| 50 |
gentoo-portage-dev@g.o mailing list |
Archives