action #125300
openSupport creating demo videos with pauses and mouse moving
33%
Description
Motivation¶
Additionally to testing, openQA can be used to create demonstration videos, and ideally the same
test code can be used, just that there should be certain pauses, and we would want to see the mouse
moving and have a little pause before clicking.
Testing of course still has the higher priotity, and the os-autoinst code should not get more
complicated, but for creating simple demo videos we probably don't need much new code.
Acceptance criteria¶
- AC1: A demo mode exists and is enabled via a setting like
DEMO_MODE, which can be used for videos targeted at human beings learning about something
Suggestions¶
- Provide an easy way to delay/sleep around needle matches (assuming this is usually what a user would want to take a look at)
- "Slow down" the generated video rather than the test itself (e.g. around needles etc)
- Move the mouse pointer gradually rather than instantaneously
Updated by tinita almost 2 years ago
- Status changed from New to In Progress
- Assignee set to tinita
- Target version set to Ready
Since I did that for the Perl Workshop, here is a first suggestion: https://github.com/os-autoinst/os-autoinst/pull/2274
We would need more sleep calls in various occasions I guess, but that can be also done later.
Test and needles:
Updated by okurz almost 2 years ago
Maybe you are going a bit too quick here :) I think there is still a variable NICEVIDEO or something similar
EDIT: I thought of https://github.com/os-autoinst/os-autoinst/commit/9b546ccf7082b5c4d7613c095554b07c072de3b5 , maybe it's just defined within os-autoinst-distri-opensuse nowadays
Updated by openqa_review almost 2 years ago
- Due date set to 2023-03-17
Setting due date based on mean cycle time of SUSE QE Tools
Updated by okurz almost 2 years ago
- Related to action #122908: [tools] openSUSE conference 2023 contributions size:M added
Updated by tinita almost 2 years ago
Like I wrote, I did the main work already as part of the talk preparation for the workshop, and I didn't want that code to lie around for weeks.
I wrote in the pull request that it doesn't cover all functions yet where it would need to add a sleep.
Maybe we can leave the new functionality totally undocumented for now (and/or mark it as experimental), so that we can make breaking changes later.
Updated by tinita almost 2 years ago
- Status changed from In Progress to New
- Assignee deleted (
tinita) - Target version changed from Ready to future