(no longer about the Co-op bot...)
On Mon, Jan 5, 2015 at 3:55 PM, Chris McMahon <cmcmahon(a)wikimedia.org>
wrote:
It's more getting the configuration correct (CommonSettings,
InitializeSettings, database configuration, etc.) working in beta labs in
order to discover any glitches that might occur before doing these updates
in production. test2wiki is of particular concern because it is a peer node
on the production cluster, it shares configuration with every other node on
the Wikipedia cluster. Making a mistake in test2wiki can have serious
consequences, better to make any mistake in beta labs first.
There's no config change for this, I just gave MatchBot the
'flow-create-board' right on testwiki. We have a dormant wmf-config patch
that creates a "flow-bot" group with this right,
https://gerrit.wikimedia.org/r/#/c/181120/ , and yes that should be tested
first on beta labs.
Beyond that, I'd really like the ability to set up
and tear down multiple
Flow pages with interesting content other than just
http://en.wikipedia.beta.wmflabs.org/wiki/Talk:Flow_QA for testing. (And
in doing so, encounter any issues along those lines.)
Yes! I forgot about that. Back when we had bugs with initial edits to Flow
boards, I meant to propose adding a Test_Flow_talk: namespace on beta labs
and test2wiki in which Flow is enabled, so a test could simply visit
Test_Flow_talk:Random_page_4795. If you gave the flow-create-board right
to some selenium user, it could make an API call to edit-header or
add-topic on any non-existent page and that would create a Flow board empty
except for that one edit.
--
=S Page Collaboration team engineer