The Reading Web team will be taking time every Monday to QA the mobile site.
We're currently lining up work around improving our development, testing,
and release processes. In fact, work on improving our browser testing
infrastructure has already begun [0]. This work is all about reducing the
size of a critical feedback loop: from a developer submitting a patch to a
bug being reported. Taking a day every sprint to QA each others work on the
beta cluster isn't ideal but it does help us to reduce the size of the
feedback loop until we're finished improving our workflows.
Here's what I sent out to the team members in the QA Day invite:
According to the deployment schedule [1], our latest and greatest code will
be hitting group 0 wikis on a Tuesday. I strongly
encourage you to take the
time to test a few common and uncommon workflows across the myriad features
new and old and report any bugs you uncover before the train starts
rolling. You might also want to take a look at a few of the group 0 wikis
on Tuesday too while our development environments don't replicate that of
production. If you find the time after all of this, then perhaps you could
try translating one or two workflows into browser tests (!!!)
[0]
https://phabricator.wikimedia.org/T100293
[1]
https://wikitech.wikimedia.org/wiki/Deployments/One_week
<https://www.google.com/url?q=https%3A%2F%2Fwikitech.wikimedia.org%2Fwiki%2FDeployments%2FOne_week&ust=1434624314404000&usg=AFQjCNE4wcOnRZk2lVGWEel4-3r9wEdghg>