|author||Milian Wolff <email@example.com>||2015-01-05 18:06:43 +0100|
|committer||Milian Wolff <firstname.lastname@example.org>||2015-01-16 19:17:36 +0100|
Make the tests less flaky and don't send empty property updates.
The tests have been flaky on the CI. And indeed, running the tests locally under valgrind, which heavily influences the timings, I could reproduce failures on my local machine as well. The failure was due to multiple things, but most notably boils down to intermittend property update noficiations. To reduce that, the myFactory.lastObj property is propagated up. This way, any change to that property won't be propagated to the clients and influence the test. Furthermore, the failing tests are hardened by also checking the server messages, which is crucial to correct the flow of messages. Finally, a bug was found, where an empty property change could be broadcasted to all clients, when only a specific client's object got its properties changed. This is also fixed by this patch now. Change-Id: I2c7ba53253e2841db1a290872dacb097a7b984cf Reviewed-by: Bernd Lamecker <email@example.com> Reviewed-by: Risto Avila <firstname.lastname@example.org> Reviewed-by: Simon Hausmann <email@example.com> Reviewed-by: Milian Wolff <firstname.lastname@example.org>
Diffstat (limited to 'examples/webchannel/qwclient')
0 files changed, 0 insertions, 0 deletions