We had a good day today, here's some feedback: > * migrate current jsspec core tests to qunit
This was the main thrust of our work - we started with: http://svn.tiddlywiki.org/Trunk/core/tests/jsspec/ jsspec: Animator.jsspec.js jsspec: BasicTypes.jsspec.js jsspec: Crypto.jsspec.js jsspec: Dates.jsspec.js jsspec: Dom.jsspec.js jsspec: FileSystem.jsspec.js jsspec: GenerateRss.jsspec.js jsspec: Macros.jsspec.js jsspec: Messages.jsspec.js jsspec: Mocks.jsspec.js jsspec: RGB.jsspec.js jsspec: Shadows.jsspec.js jsspec: Strings.jsspec.js jsspec: Tiddler.jsspec.js jsspec: TiddlyWiki.jsspec.js jsspec: TW21Saver.jsspec.js jsspec: Version.jsspec.js jsspec: Wikifier.jsspec.js jsspec: Wizard.jsspec.js jsspec: XML.jsspec.js jsspec: Zoomer.jsspec.js and now have:: http://svn.tiddlywiki.org/Trunk/core/test/tests/ jshead: SavingRSS.js jshead: BasicTypes.js jshead: Crypto.js jshead: DOM.js jshead: Dates.js #jshead: Encoding.js jshead: RGB.js jshead: FileSystem.js jshead: Strings.js jshead: Utilities.js jshead: Wikifier.js so a little way to go. Help here is appreciated! You can run the tests by "cook test" in the directory: http://svn.tiddlywiki.org/Trunk/core/test/recipes/ We did hit a few blocks on the way. We added the jqmock module for the bespoke jsspec mockers: http://code.google.com/p/jqmock/ added a new "startup" event to the core so tests can work with the store, etc: http://trac.tiddlywiki.org/ticket/978 and evolved patterns for init/tear-down, and encountered an issue with a race-condition on the test summary. > * improve and standardise the language of test cases, to improve > documentation of the core The qunit framework is less BDD than jsspec, but we decided to work on evolving the language as we progress. We're also considering adding a "yellow" status for tests which need work, or which have tickets outstanding. > * improve the coverage of tests in the core, possibly quantifying > this with jscoverage Martin started to look at jscoverage, not yet working with TiddlyWiki, looks promising. > * produce a pattern for qunit tests in plugins others may follow That's still outstanding, but a matter of personal preference - I'm hoping to publish something which fits in with how I write plugins. > Anyone willing, and able to join us physically is more than welcome at > Osmosoft towers, and we can coordinate remotely via IRC, well at least > during core-UK working hours, and of course you'll able to follow our > work on trac, etc. In the event we had seven participants. Thanks to all who took part! > I'll commit to writing up our discoveries afterwards, and helping > others contribute in this activity. Which is the reason for writing this email ;-) Now we need to ensure we keep working on the tests, and ensure they continue to pass as we develop the TiddlyWiki core. Paul (psd) -- http://blog.whatfettle.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
