On Thu, Sep 19, 2013 at 1:21 PM, Rachel Thomas <[email protected]> wrote:
> From Zeljko's gerrit code, it looks like he already removed the production > tests. I was going to say that it could be still valuable to run them. > There may be a time when test2 is not updated correctly with the right > versions of features that we want to test, or is down for maintenance, and > it would be a good idea to have a backup test running on production > server. Also, those tests do not seem to be ones that would take a lot > of time or horsepower to run, so it wouldn't be much overhead to run those. > Yes, I think we should consciously choose the tests to run against production, the four noted above were more accidents of history than chosen deliberately. > > --Rachel > > *Gnome FOSS Outreach Program for Women Intern > Browser Test Automation, Wikimedia Foundation* > > Notes from the Bleeding Edge <http://www.bleededge.blogspot.com/> > > > > On Thu, Sep 19, 2013 at 4:12 PM, Željko Filipin <[email protected]>wrote: > >> On Thu, Sep 19, 2013 at 12:57 PM, Chris McMahon >> <[email protected]>wrote: >> >>> Open question: is it worthwhile to run read-only browser tests against >>> the production wiki, e.g. https://en.wikipedia.org? >>> >> >> I did some cleanup on how tests run. Feel free to comment here or in >> Gerrit: >> >> https://gerrit.wikimedia.org/r/#/c/85098/ >> >> Željko >> >> _______________________________________________ >> QA mailing list >> [email protected] >> https://lists.wikimedia.org/mailman/listinfo/qa >> >> > > _______________________________________________ > QA mailing list > [email protected] > https://lists.wikimedia.org/mailman/listinfo/qa > >
_______________________________________________ QA mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/qa
