Roan Kattouw wrote:
2010/3/10 Conrad Irwin:
This should work the same way as extension parser-tests, with the tests in the extension's directory, included using a config variable. Otherwise, extensions are split over two places, so there's not such an easy way to just tarball them, and it's less clear from the SVN commit paths that all work was just to the extension, it also provides more flexibility if people want it.
On the other hand, we intend on setting up a server that runs these tests automatically. Instead of having to pull these tests from a million different places, it'd be nice if this server could just update from one dir and be done with it, which is exactly why I set it up the way I did. I agree that this is kind of the enemy of nice bundling of tests with extensions, but I think having an automatic test setup that tests stuff /before/ it's released is more important and more frequently used than providing easy access to tests to those .3% of downloaders that are actually gonna run them.
Roan Kattouw (Catrope)
Shouldn't that server have the extensions checked out and installed on a local mediawiki before running them ? (I am assuming it's a single server testing against localhost)