DDBug Issue Tracking Product
You can see DDBug in action (and report bugs or request features for DDBug itself)
at the MetaDDBug . Why did we do DDBug?
- We needed a simple issue tracker that we could convince our clients to use.
- The first iteration of DDBug (never released) was done with
ZClasses and was very useful, but didn't have unit tests and so
it wasn't very easy to extend reliably.
- We wanted to practice what we believed to be the current (as of
April 2003) recommended best practices in developing a Zope Product.
Among the nifty features you can learn by reading the source are:
- Comprehensive unit testing (which depend on Stefan Holek's
ZopeTestCase ).
- How to create a Zope object that is addable only to certain kinds
of containers but not others.
- Zope3 module and class naming conventions.
- Interface declarations (still underused)
- All this in a product with with less than 600 lines of code (but
more than 700 lines of tests!!).
|
| Latest Release: |
2.0.0 a4
|
| Last Updated: |
2003-05-21 16:34:09 |
| Author: |
ZopeOrgSite
|
| Categories: |
Content Object, Developer, Examples, Feedback |
| Maturity: |
Development |
|
Log in
Forgot your password?
