4 * Keep writing more tests!
9 * Clutter-Wayland tests
10 * other integration tests (get creative)
12 * Write wfits test extensions for other wayland compositors.
13 * May need to petition them for module/plugin support.
15 * Refactor or remove useless/pointless EFL-Wayland tests.
16 * At some point, someone was given the task of quantity was better
17 than quality. We should revisit some tests here and determine their
18 usefulness. Most of these would be the ones that just invoke/exercise the efl
19 API's and don't have any client<->server or input-event related checks.
20 Albeit, if anything, they may still be useful to detect crashing or toolkit
21 state; but that alone is not necessarily in the nature of what we really want
22 to validate/test (which would ultimately be Wayland integration).
24 * Move away from the "check" dependency.
25 * It's important that tests are executed in a forked process.
26 * It's important that tests have a timeout.