ubuntu-phone team mailing list archive

[Sergio Schvezov <sergio.schvezov@xxxxxxxxxxxxx>]

On viernes 27 de junio de 2014 14h'45:47 ART, Łukasz 'sil2100' Zemczak 
wrote:
> Hi,
>
> So, in overall I would also opt for getting the issue fixed instead of
> just disabling the test, but I can understand the rationale for the
> disablement itself; as this is an issue that's coming from a separate
> component - and that the it's actually blocking landing of a serious
> regression fix.

Always a difficult spot to be in :-)

> I agree with what the QA representatives said: let's disable the test
> but only if we have a bug reported and at least having someone working
> on it actively, making sure it gets actually fixed as soon as possible.
> I would also encapsulate the actual test disablement in a big FIXME with
> the bug number mentioned in the comments.

Some test runners support an ExpectFail annotation, wouldn't that be 
prefered? Once it starts working the test would fail and you'd get rid of 
your workaround.

Cheers
Sergio