S Page wrote:
> I mean to look at
These use PHPunit, but it seems an old version, and they're for internal
testing of particular classes, not testing pages with extensions.
MediaWiki also has maintenance/parserTests.php which is supposedly good
for testing extensions. But SMW breaks it because it introduces unknown
tables. I filed bug 9335,
http://bugzilla.wikimedia.org/show_bug.cgi?id=9335 , which Rob Church
made a dupe of existing bug 8010.
This is old and incomplete.
> Meanwhile I think we should create some pages on ontoworld.org
I started, http://ontoworld.org/wiki/Category:SMW_unit_tests
It's pretty rough. It needs a [[Template:Unit test]] with
input wiki text
expected HTML output
expected factbox output
expected inline query output
and another [[Template:Test results]] to manually record PASS/FAIL/XFAIL
for each release with nice green and red emoticons :-)
Template:SMWbug, Template:Bugged, and Attribute:Bugged are also useful.
Markus Krötzsch replied:
> Agreed. There will be at least one developer in project Halo who will
> investigate means of doing proper unit testing for SMW.
I hope this helps.
> Concerning the interdependencies of code, I am constantly working on
> disentangling this mess.
I don't think the code is a mess! Extensions add features to MediaWiki,
so naturally they call back into MediaWiki all over to get things done.
Restructuring the SMW code so that a core layer has no MediaWiki
dependencies and an interface layer passes information between SMW and
MediaWiki would probably make it harder to understand.