Update on 1.2 testing
yura.zenevich at gmail.com
Mon Apr 12 13:42:58 UTC 2010
If I am not mistaken UI Options doesn't use keyboard accessibility plugin so
we don't have to re-test if in this regard.
On Mon, Apr 12, 2010 at 9:36 AM, Justin Obara <obara.justin at gmail.com>wrote:
> Also I forgot to mention that the Reorderer needs to completely retested
> after the fix to FLUID-3590.
> On 2010-04-12, at 9:29 AM, Justin Obara wrote:
> > Hello,
> > Just to be clear, the components that need to be retested in regards to
> keyboard accessibility are InlineEdit (all variants) and UI Options. If you
> have already tested these components before the fix for FLUID-3590 went in,
> you just need to do the keyboard tasks from the state based tests.
> > Thanks
> > Justin
> > On 2010-04-09, at 4:52 PM, Justin Obara wrote:
> >> The fix for FLUID-3590 has just gone in. All testing tasks are now open.
> >> Please also make sure to go back and redo any of the keyboard testing
> tasks for components that you have already tested.
> >> Thanks for all the help
> >> Justin
> >> On 2010-04-08, at 5:30 PM, Justin Obara wrote:
> >>> We are progressing towards a fix for our last remaining blocker,
> >>> http://issues.fluidproject.org/browse/FLUID-3590
> >>> Hopefully the fix will be in place in a day or so.
> >>> What this means for testing is that all of the reorderer tasks and any
> component that uses the keyboard a11y plugin will need the keyboard tasks
> >>> You should probably focus on the UI Options and Uploader tasks to start
> >>> Thanks for all of the help.
> >>> Justin
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the fluid-work