Would it be possible as these behaviors are implemented for us to create automated UI-level acceptance tests for them, and run the tests against code in beta labs? If we could create these as we go along, they would serve as a growing set of regression tests. Also, it would be nice to run the tests in all supported browsers, including Internet Explorer if we can. Knowing that stuff works in IE as we go along should save rework later on.
The descriptions of the stories in Mingle are a bit sparse. https://mingle.corp.wikimedia.org/projects/flow/cards/grid?color_by=priority...
On Sun, Aug 18, 2013 at 5:28 PM, Brandon Harris bharris@wikimedia.orgwrote:
I've gone ahead and written up two Functional Specificationdocuments:
http://www.mediawiki.org/wiki/Flow_Portal/Functional_Specifications/Moderati...
* This reflects the conversations we had onThursday and Friday and fleshes out some behaviors.
http://www.mediawiki.org/wiki/Flow_Portal/Functional_Specifications/Search_a...
* This describes (mostly) how the local Boardsearch will work. It gets kind of technical with the language (e.g., "compositional intersection tokens") but I think it's readable for the audience. I did this one because I was getting asked about it.
I'm going to be creating several of these and breaking them upinto sections. Stuff like "this is how timestamps behave" and "this is how edit windows behave" and the like. Where necessary I'll start making mockups (some of this will be easier to do in photoshop than making interactive ones, especially given the speed at which Andrew and Erik are producing code).
Off the top of my head, here is my current list of TODOs: * User renames / Account merges (merge boards) * Board * Single Topic * Feed * Editors * Scratchpads * Timestamp behavior * History behavior
Brandon Harris, Senior Designer, Wikimedia Foundation
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
EE mailing list EE@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/ee