On 8/9/10 11:27 AM, Mark A. Hershberger wrote:
Dan Nessett<dnessett(a)yahoo.com> writes:
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.
I would have to go look at why that decision
was made, but it seems like
it just allows the code to be polluted with Selenium-specific
identifiers that production code should not have *anything* to do with.
I would like to keep testing-specific code (and variables) separate and
distinct from production code.
As stated previously, selenium tests exercise MW
code by accessing the
wiki through a browser.
Agreed.
Mark.
--
http://hexmode.com/
Embrace Ignorance. Just don't get too attached.
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l I don't know where this
landed, but I wanted to point out that system
testing might be a better name for out use of Selenium, Acceptance
testing has more of a "customer is accepting a product" connotation.