On Mar 5, 1:23 pm, FND <[email protected]> wrote:
> > 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.
As long as that means before actually working on the respective file/
module, then that's fine. Those tickets can then also be used to check
what others are working on.
> > 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.
See above.
> > 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.htm...)
> Cooking that recipe will give you the test suite.
That's great thanks. However I'm unsure as to how tests are to be
written for functions that involve accessing the store. Any examples
available?
I should be able to start on this over the coming weekend.
Saq
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
