[QA] Run UploadWizard API integration test against production...

[Aaron Arcos]

Hi there Željko,

  Just changed <https://gerrit.wikimedia.org/r/#/c/109335/> the script to
support environment variables (MEDIAWIKI_USER and MEDIAWIKI_PASSWORD).
Gergo tested it and it worked fine. Please,
let us know if anything else.

  Also, we would like to get this script to run against every beta build.
The sooner
we detect bugs, the cheaper they are to fix. Let us know how we can help for
this to happen.

Thanx again !



On Fri, Jan 24, 2014 at 8:52 AM, Željko Filipin <zfilipin at wikimedia.org>wrote:

> On Fri, Jan 24, 2014 at 3:05 AM, Gergo Tisza <gtisza at wikimedia.org> wrote:
>
>> USERNAME=mw_test_uw_1
>> PASSWORD=wizard2013
>> set -e
>>
>> virtualenv --distribute DEV
>> DEV/bin/pip install -r tests/api/requirements.txt
>> DEV/bin/python tests/api/upload-wizard_tests.py --username "$USERNAME"
>> --password "$PASSWORD"
>> DEV/bin/python tests/api/upload-wizard_tests.py --username "$USERNAME"
>> --password "$PASSWORD" --gen_new_image
>>
>
> Thanks, everything works fine now with the new requirements.txt. The
> problem is that console log of every Jenkins log is public and if we
> provide password from the command line, it will be visible to everybody.
>
> The way we solved that problem in Ruby is that the scripts expect the
> password to be located in MEDIAWIKI_PASSWORD environment variable[1]. Can
> you do something similar for upload-wizard_tests.py?
>
> Željko
> --
> 1:
> https://github.com/wikimedia/qa-browsertests/blob/master/features/step_definitions/login_steps.rb#L20
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wikimedia.org/pipermail/qa/attachments/20140124/431d4e25/attachment.html>