Hard to Test TWiki Features

There are some TWiki features that are hard to fully unit test, because they require subjective review or complex interacting script calls. I want to kick off a discussion of test areas that need to be addressed. Specific areas I'm nervous about are:

• Bulk registration
• Any complex flow with edge cases that require interaction
  • e.g. deleting an attachment with the same name twice in a row
• Scripts not run very often
  • preview
  • rdiff
  • resetpasswd
  • statistics
  • mailnotify
  • twiki (why is this even there?)
• Anything in "Waiting for Feedback" status that might still be a bug
• configure
• Standard plugins that do not have unit tests or any published test plan
  • EditTablePlugin
  • InterwikiPlugin
  • PreferencesPlugin
  • RenderListPlugin
  • SlideShowPlugin
  • SmiliesPlugin
  • SpreadSheetPlugin
  • TablePlugin
  • TipsContrib
• Skins, which require subjective usability testing
  • The default templates
  • ClassicSkin
  • PatternSkin
• Anything that relies heavily on Javascript
  • BehaviourContrib
  • TwistyContrib
  • TwistyPlugin
• Upgrade/compatibility/run-once/obscure scripts
  • tick_twiki.pl
  • upgrade_emails.pl
  • rewriteshebang.pl
  • geturl.pl

Missing Unit Tests

• There should be a Fn_TEST for every TWiki variable implemented by the core
• There should be a test case for every CGI script that tests its parameters

-- Contributors: CrawfordCurrie - 09 Sep 2007

Discussion

Javascript, and browser or session variable things can be tested using the JSUnitContrib - What we need is for someone to add the JSUnit server stuff to send back the error reports too....

And if the tests are written in a scripted fashion, I can add them to the nightly builds - with emails on failure.

-- SvenDowideit