Hi all,
I'd like to master TDD in the way Mr. Wilkes describes it here:
http://www.circulartriangle.com/blog/?p=10
by the end of 2010. To that end, I have a "test product" called
collective.project that I am looking for
feedback on:
https://dev.plone.org/collective/browser/collective.project/trunk/README.txt
I had originally promised to deliver tests and a user manual for it by the end
of the year, but since I missed
that deadline I thought I'd set a new one. I've written tests before. I know
how to run the
testrunner. I just can't make a habit of it which is what I'm looking to
change.
A bit about the code:
- There are 4 dexterity content types: client, project, iteration, task.
-
https://dev.plone.org/collective/browser/collective.project/trunk/collective/project/client.py
-
https://dev.plone.org/collective/browser/collective.project/trunk/collective/project/project.py
-
https://dev.plone.org/collective/browser/collective.project/trunk/collective/project/iteration.py
-
https://dev.plone.org/collective/browser/collective.project/trunk/collective/project/task.py
- There is a "bulk iteration creator":
-
https://dev.plone.org/collective/browser/collective.project/trunk/collective/project/browser/create_iteration.py
- I've just begun to move duplicated code from the content types to a
common module.
-
https://dev.plone.org/collective/browser/collective.project/trunk/collective/project/common.py
What I'm looking for:
- Advice on what types of tests you'd expect to see.
- Ideas to make testing "fun".
- Code review.
- Any comments that may strike you.
Thanks and happy new year,
Alex
---
Alex Clark · http://aclark.net
Practical Plone 3 · http://tinyurl.com/practical-plone
_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers
