action #71500
closedPotential optimization by skipping deployment checks in our tests (all except explicit deployment check tests)
Description
Motivation¶
t/lib/OpenQA/Test/Database.pm has an option "skip_deployment_check" when initializing the test database. It seems this takes some seconds to execute in all tests. Probably we can save quite some time by skipping this in all but one or only a selected subset of specific tests
Updated by okurz about 4 years ago
- Status changed from New to Feedback
- Assignee set to okurz
https://github.com/os-autoinst/openQA/pull/3403 . Not exactly for deployment checks but related to what we found out.
EDIT: mkittler checked and stated that the "deployment_check" does the actual deployment, i.e. instantiation of schema, as well, so not only "check". Probably the unused option to skip should then be removed and the method renamed. But maybe we can still skip something within the check method.
EDIT: https://github.com/os-autoinst/openQA/pull/3403 merged
Updated by okurz about 4 years ago
https://github.com/os-autoinst/openQA/pull/3417 to prevent the confusion on the name by renaming.
Updated by okurz about 4 years ago
- Copied to action #72082: Reduce test runtime, e.g. less reliance on test fixtures or test database instances added
Updated by okurz about 4 years ago
https://github.com/os-autoinst/openQA/pull/3417 is merged. The "deployment check" was the actual deployment which we made more explicit with the right name.
Created #72082 as a followup to improve the use of our test database or not using them at all if possible.