On Sat, 07 Aug 2010 23:30:16 -0400, Mark A. Hershberger wrote:
Dan Nessett <dnessett(a)yahoo.com> writes:
I don't think walking through all the
extensions looking for test
subdirectories and then running all tests therein is a good idea.
First, in a large installation with many extensions, this takes time
and delays the test execution.
Globbing for extensions/*/tests/TestSettings.php doesn't take long at
all.
However I am looking at a way to test extensions independently of
installation.
This means I can't depend on hooks or global variables, so I need
another way to find out if an extension has tests available.
Making the developer specify the extension or
core tests to run on the
RunSeleniumTests command line is irritating (at least, it would
irritate me)
No doubt. So why not allow per-user files to set this instead of using
LocalSettings.php?
Mark.
Testing uninstalled extensions may make sense for unit tests, but not for
selenium tests. The latter exercise the code through a browser, so the
extension must be installed for selenium testing.
I'm not sure what are the advantages of "per-user" configuration files.
For unit tests the tester directly accesses the code and so has direct
access to LocalSettings. For selenium testing, we originally had a
configuration file called SeleniumLocalSettings.php, but that was
abandoned in favor of putting the configuration information in
DefaultSettings and LocalSettings.
As stated previously, selenium tests exercise MW code by accessing the
wiki through a browser. I don't see how a 'per-user' configuration file
would be integrated without introducing some serious security issues.
--
-- Dan Nessett