QA (public) » openQA Project (public)

To put this into context: This is about job modules that need needle updates for check_screens. If in development mode, the job creates a snapshot per job module, so that when I recreate a needle, I get an option to restart the job from start or from the job module that had the needle.

So that's basically 'setting the SKIPTO variable' in the middle of the test. Just to check whether I understand this correctly:

1. Prerequisites (in which state should this rollback be possible)¶

1. User has created a developer session
2. Test is paused due to check_screen or assert_screen timeout
3. User has created a new needle via the needle editor

2. What we have so far (when https://github.com/os-autoinst/openQA/pull/1727 is merged)¶

1. The test can only pause on assert_screen timeout but not on check_screen timeout.
2. The developer mode allows to resume a paused test where it has been interrupted.
3. If it has been interrupted due to an assert_screen timeout, needles are reloaded and the assertion is retried.

3. What we need to implement¶

1. If in development mode, the job creates a snapshot per job module (by default?).
2. The test can pause on check_screen timeout (in addition to 2.1).
3. When prerequisites are met, the web UI proposes to revert the test execution to a previous snapshot before resuming (in addition to 2.2 and 2.3).
4. The web UI sends the command to revert via the liveviewhandler to os-autoinst. The worker is not involved.
5. Status info and possible error messages related to the rollback are passed to the frontend via the liveviewhandler so the user can see what's going on.
6. I assume that when we revert the VM to a previous snapshot, we must also revert the execution of the Perl test code to that point. Otherwise the state of the VM and the test code execution would be out-of-sync.

PR for making pause on check_screen timeout from os-autoinst side: https://github.com/os-autoinst/os-autoinst/pull/1013

Note that this ticket still needs refinement.