> I think [coordinating via Trac] sounds very good actually.
Great.
We've decided that instead of creating tickets up-front, we'll create
them as we start working on the respective modules.
> My one concern is to make sure avoid duplication
Given the number of people involved, I don't think that's gonna be a
huge issue - and if it does become a problem, we can worry about it then.
> I'd like to suggest that all refactoring be accompanied with unit
> tests for the corresponding code.
Absolutely, yeah - we're planning to be rigorous about unit testing in
the process, taking this as an opportunity to increase overall test
coverage.
> The key is just getting a recipe/vertical in order for such
> unit testing, unless we already have one?
We do:
http://tinyurl.com/bou2la
(http://trac.tiddlywiki.org/browser/Trunk/core/qunit/recipes/tests.html.recipe)
Cooking that recipe will give you the test suite.
I've just made a commit that should illustrate how easy it is to get
started:
http://trac.tiddlywiki.org/changeset/8995
Ideally, we should write up some instructions on the community wiki...
-- F.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---
