On Mon, Jan 5, 2015 at 4:39 PM, S Page <spage@wikimedia.org> wrote:

On Mon, Jan 5, 2015 at 4:19 PM, Jonathan Morgan <jmorgan@wikimedia.org> wrote:

Our first priority is to test our whole workflow on testwiki. I see that MatchBot has the Flow-bot user right now, so are we good to go with testing creating a talkpage as a Flow board there?

Should be. https://test.wikipedia.org/wiki/Special:Contributions/MatchBot suggests someone was trying it (on Christmas day!).

On Mon, Jan 5, 2015 at 3:24 PM, Chris McMahon <cmcmahon@wikimedia.org> wrote:
I'd really like to see this on beta labs if possible, hopefully in advance of testwiki and particularly in advance of test2wiki.

Why, does QA usually get involved in testing bots and API calls? This isn't a user action amenable to browser testing.

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.

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.)