Google Cloud. IT Tests: Fixing and rework for 4.3.0-RC2 #2420
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
As the main issue stands, there were major problems considering that several logging sentences were changed in the source code but the tests were not adapted accordingly.
The PR resolves the following issues:
test_schedule
:acuum_result=2
was not neededtest_remote_configuration
TimeTravels
fromtest_day_wday
since they are no consistent at all. We can not rely on TimeTravel to make the tests work properly.Safety checks
Status
(*) Keep in mind that there is no way to include
configuration.yaml
dynamically before running QACTL. Which means that the first run fails cause the file is not there, you need to upload it manually to the vagrant box and then re-run the test.