[QA] best practices for running browser tests locally

[Nikolas Everett]

I keep a script in my home directory that I source before I run tests.  It
contains:
export MEDIAWIKI_USER=Selenium_user
export MEDIAWIKI_PASSWORD=not_for_mailing_list
export MEDIAWIKI_URL=http://solr-mw3.instance-proxy.wmflabs.org/wiki/
export REUSE_BROWSER=true

If I want to do something other than the default I source the script and
then manually modify the variables.  I suppose the only real difference is
that I keep it in my home directory so I'm not likely to commit it
accidentally.

Nik



On Mon, Jan 27, 2014 at 10:57 AM, Amir E. Aharoni <
amir.aharoni at mail.huji.ac.il> wrote:

> Hallo,
>
> Are there any suggested practices for running browser tests locally?
>
> What I usually do is that I create a little bash script in the
> tests/browser directory and it exports the relevant MEDIAWIKI_* environment
> variables.
>
> I also have a bash function that defines KEEP_BROWSER_OPEN, because I use
> it so often.
>
> Is there something smarter that anybody here does?
>
> --
> Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי
> http://aharoni.wordpress.com
> ‪“We're living in pieces,
> I want to live in peace.” – T. Moore‬
>
> _______________________________________________
> QA mailing list
> QA at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/qa
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20140127/032d791a/attachment.html>