tests/test-runner: Add a 'wait_reconfigure' command
This makes sure that a client has properly responded to a configure event it itself triggered. In practice, this is just two 'wait' commands, with a 'dispatch' in between, which is needed because a single one does not reliably include the two way round trip happening when e.g. responding to a unmaximize configure event triggered by a unmaximize request. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1171
This commit is contained in:
parent
476ef76de6
commit
62f449d7d5
@ -637,6 +637,24 @@ test_case_do (TestCase *test,
|
|||||||
if (!test_case_wait (test, error))
|
if (!test_case_wait (test, error))
|
||||||
return FALSE;
|
return FALSE;
|
||||||
}
|
}
|
||||||
|
else if (strcmp (argv[0], "wait_reconfigure") == 0)
|
||||||
|
{
|
||||||
|
if (argc != 1)
|
||||||
|
BAD_COMMAND("usage: %s", argv[0]);
|
||||||
|
|
||||||
|
/*
|
||||||
|
* Wait twice, so that we
|
||||||
|
* 1) First wait for any requests to configure being made
|
||||||
|
* 2) Then wait until the new configuration has been applied
|
||||||
|
*/
|
||||||
|
|
||||||
|
if (!test_case_wait (test, error))
|
||||||
|
return FALSE;
|
||||||
|
if (!test_case_dispatch (test, error))
|
||||||
|
return FALSE;
|
||||||
|
if (!test_case_wait (test, error))
|
||||||
|
return FALSE;
|
||||||
|
}
|
||||||
else if (strcmp (argv[0], "dispatch") == 0)
|
else if (strcmp (argv[0], "dispatch") == 0)
|
||||||
{
|
{
|
||||||
if (argc != 1)
|
if (argc != 1)
|
||||||
|
Loading…
x
Reference in New Issue
Block a user