5192b06ccb
QTimeLine::currentTime() is an integer in the range [0..duration], not a float in the range [0.0..1.0]. The aim of the test appears to be to verify that currentTime() is at least 90% of the way to duration() when the timeline is almost due to finish, so verify that and give the corresponding 10% tolerance on reaching the end state. Change-Id: I38646947c3b9189a4e8e91a450c6071430ddc66a Reviewed-by: Rohan McGovern <rohan.mcgovern@nokia.com> |
||
---|---|---|
.. | ||
auto | ||
baselineserver | ||
benchmarks | ||
global | ||
manual | ||
shared | ||
README | ||
tests.pro |
This directory contains autotests and benchmarks based on QTestlib. In order to run the autotests reliably, you need to configure a desktop to match the test environment that these tests are written for. Linux X11: * The user must be logged in to an active desktop; you can't run the autotests without a valid DISPLAY that allows X11 connections. * The tests are run against a KDE3 or KDE4 desktop. * Window manager uses "click to focus", and not "focus follows mouse". Many tests move the mouse cursor around and expect this to not affect focus and activation. * Disable "click to activate", i.e., when a window is opened, the window manager should automatically activate it (give it input focus) and not wait for the user to click the window.