There is a lot of qWait calls in the test code. Adding delays are sometimes necessary, but in a lot of the case it also adds an assumption of fixed latency or over-estimates the required wait time. This makes the test code highly sensitive to latency, and at risk of either breaking due to code optimisations, or failing intermittently.
Generally these instances should be replaced by something that waits until something occurs, such as a callback. That way, it doesn't matter if some resources suddenly are a lot slower than anticipated.
There is a lot of
qWaitcalls in the test code. Adding delays are sometimes necessary, but in a lot of the case it also adds an assumption of fixed latency or over-estimates the required wait time. This makes the test code highly sensitive to latency, and at risk of either breaking due to code optimisations, or failing intermittently.Generally these instances should be replaced by something that waits until something occurs, such as a callback. That way, it doesn't matter if some resources suddenly are a lot slower than anticipated.