| commit | b3caa7b55e1ba9d3c02d50baa425f601d091f4cb | |
| author | Daniel P. Berrangé <berrange@redhat.com> | |
| Thu, 10 Mar 2022 17:18:12 +0000 (10 17:18 +0000) | ||
| committer | Dr. David Alan Gilbert <dgilbert@redhat.com> | |
| Thu, 21 Apr 2022 18:36:46 +0000 (21 19:36 +0100) | ||
| tree | c494d0eb7ad90dbb1da86447a20e3f2562835110 | treesnapshot (tar.gz zip) |
| parent | ffed54f6e51db2685d44f34bb2437aac10314e00 | commitdiff |
tests: introduce ability to provide hooks for migration precopy test
There are alot of different scenarios to test with migration due to the
wide number of parameters and capabilities available. To enable sharing
of the basic precopy test scenario, we need to be able to set arbitrary
parameters and capabilities before the migration is initiated, but don't
want to have all this logic in the common helper function. Solve this
by defining two hooks that can be provided by the test case, one before
migration starts and one after migration finishes.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20220310171821.3724080-10-berrange@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
There are alot of different scenarios to test with migration due to the
wide number of parameters and capabilities available. To enable sharing
of the basic precopy test scenario, we need to be able to set arbitrary
parameters and capabilities before the migration is initiated, but don't
want to have all this logic in the common helper function. Solve this
by defining two hooks that can be provided by the test case, one before
migration starts and one after migration finishes.
Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
Message-Id: <20220310171821.3724080-10-berrange@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
| tests/qtest/migration-test.c | diffblobblamehistory |