We could easily add a time multiplier pref and you could set that during your 
test. This is probably cheap enough and useful enough to do in production 
builds.

Andreas

On Feb 16, 2014, at 7:24 PM, Andrew Sutherland <asutherl...@asutherland.org> 
wrote:

> In Gaia, the system and many of the apps use transitions/animations with a 
> non-trivial duration, particularly for card metaphor stuff where logic may be 
> blocked on the completion of the animation. (Values seem to vary between 0.3s 
> and 0.5s... no one tell UX!)
> 
> Our Gaia tests currently take an absurdly long amount of time for what is 
> being tested.  There are varying reasons for this (gratuitous teardown of the 
> b2g-desktop process, timeouts that time out but don't fail, etc.).  I believe 
> one thing we could do to speed things up would be to make all transitions 
> super short.  We still want transitionend to fire for logic reasons, but 
> otherwise the unit test infrastructure probably does not really care to 
> actually watch the transition happen.
> 
> Is it possible / advisable to have Gecko support some preference or other 
> magical mechanism to cause transitions and non-infinite animations to 
> effectively complete in some extremely small time interval / on the next turn 
> of the event loop, at least for durations originally less than 1second/other 
> short time?  I briefly looked for such an existing mechanism, but was unable 
> to find one.
> 
> The alternative would be to use a build-time mechanism in Gaia to transform 
> all CSS to effect this change in that fashion.  Gaia already has build steps 
> like this so introducing it would not be particularly difficult, but it's 
> always nice if what the tests run is minimally different from what the 
> devices run.
> 
> (Additionally, an in-Gecko mechanism could produce slightly more correct 
> results since it could realistically emulate the ordering of when the 
> transitionend events would fire before disregarding those numbers and firing 
> them all in succession.  Although an automated mechanism I suppose could just 
> map observed values to sequentially ordered small timeouts.)
> 
> Andrew
> _______________________________________________
> dev-platform mailing list
> dev-platform@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-platform

_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform

Reply via email to