On Jul 20, 1:52 pm, Tobias Beer <beertob...@googlemail.com> wrote: > On 19 Jul., 15:55, PMario <pmari...@gmail.com> wrote: > > > I think, that's what automated tests are > > for.https://github.com/TiddlyWiki/tiddlywiki/tree/master/test > > -m :) > > Mhhh, and now what? Sorry that I am (currently) too lazy to figure out > where to begin with any of this. Why is it that these ReadMe files on > GitHub almost always only contain high level technical information but > no links to resources on how work with this stuff? Does this test > suite provide information such as...
There is a README at the bottom of https://github.com/TiddlyWiki/tiddlywiki which points to some resources in the github wiki. If you think certain things are missing it would be great to get this feedback. > > WARNING > -> YourPlugin > --> hasClass(): deprecated as of 2.6.3 > > ...upon testing ... a wiki ... a plugin.js ...a xyz ?!? > > Cheers, Tobias. What you are describing would be quite complicated to do. Best thing to do is to add a script tag to your plugin at the bottom of a TiddlyWiki and in Chrome under developer tools see if any exceptions are thrown due to functions not existing. As pmario points out tests (such as those written in qunit) will help - but you have to write them yourself for your own plugins for them to be helpful. The tests in that directory only check core functions of TiddlyWiki work as expected.. not plugins. :) -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to tiddlywiki@googlegroups.com. To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
