coordination #14818
closed[EPIC] Interactive mode is an usability disaster
100%
Description
observation¶
https://openqa.suse.de/tests/635851/file/autoinst-log.txt
steps to reproduce¶
- Start test
- Go in interactive mode in very beginning
- Pause test
- Test times out
problem¶
H1. a regression in os-autoinst
Updated by okurz almost 8 years ago
- Subject changed from Test got timeout in pause mode to [interactive] Test got timeout in pause mode
Updated by asmorodskyi almost 8 years ago
- Status changed from New to In Progress
issue not reproduces for more than 20 builds
https://openqa.suse.de/tests/latest?distri=sle&limit_previous=50&version=12-SP3&arch=x86_64&flavor=Server-DVD&machine=64bit&test=migration_zdup_offline_sle12sp1#previous
closing
Updated by asmorodskyi almost 8 years ago
- Status changed from In Progress to Rejected
Updated by okurz almost 8 years ago
- Status changed from Rejected to In Progress
it's interactive mode so the verification with 20 builds does not apply here.
Updated by coolo almost 8 years ago
- Subject changed from [interactive] Test got timeout in pause mode to Interactive mode is an usability desaster
- Category changed from Regressions/Crashes to 124
- Status changed from In Progress to New
- Priority changed from High to Normal
As a matter of fact: there is no "pause mode". The button you pressed is titled 'Stop waiting for needle' - and if you press it, the job will fail unless you create a new needle and reload.
Updated by okurz over 7 years ago
- Related to action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded added
Updated by coolo almost 7 years ago
- Subject changed from Interactive mode is an usability desaster to [EPIC] Interactive mode is an usability desaster
- Status changed from New to In Progress
I did some research on it during HW - https://hackweek.suse.com/16/projects/openqa-ide
But a severe cold stopped me from any real progress :(
Updated by coolo almost 7 years ago
- Has duplicate action #14832: reload needles and retry does not work added
Updated by coolo almost 7 years ago
- Has duplicate action #18364: interactive mode - needle editor - reload needles and retry doesn't work on most cases added
Updated by coolo almost 7 years ago
- Related to deleted (action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded)
Updated by coolo almost 7 years ago
- Has duplicate action #18700: openQA worker doesn't work reliable anymore after needle created in interactive mode and reloaded added
Updated by coolo almost 7 years ago
- Has duplicate action #18880: fix interactive mode with caching added
Updated by coolo almost 7 years ago
- Has duplicate action #19294: openQA webUI - interactive mode - needle editor icon doesn't show up after new needle reloaded added
Updated by coolo almost 7 years ago
- Has duplicate action #17786: [tools]NFS-less mode: Interactive mode needs to resync needles added
Updated by coolo over 6 years ago
First branches are set to remove what we have - and add a WS to isotovideo for remote control
Updated by coolo over 6 years ago
User Stories for openQA Developer Mode
We have different developers:
- Reviewer Ray wants a way to update needles without job restarts
- Test Developer Tim wants a way to maintain tests and needles
- System Developer Lea wants a way to access running SUTs
User Stories:
- Lea learned from a bug report that gnucash crashes on startup, but can't reproduce in her system. As such she wants openQA to pause before the gnucash test and give her a chance to step through the test process until the crash to continue manually collecting logs. Lea prefers to have direct access to the SUT - vnc or ssh. She does not need nor know openQA test API in general.
- Ray reviews the latest build of Tumbleweed and notices a font change breaking all old needles in GUI applications. He wants openQA to pause whenever an assert_screen would timeout to update the needle and redo the assert_screen with that new needle. Ray is working at about 3 scenarios at the same time - covering different areas of needles.
- Tim got a ticket from Ray that the docker test failed and wants openQA to reproduce the issue and pause at the beginning of the docker test. Afterwards he wants openQA to make a disk snapshot and step through the test execution to find out where the problem is. After he found out, he reloads the snapshot to tweak the execution. During this process, openQA records his steps and allows to add needles.
Updated by SLindoMansilla over 6 years ago
- Subject changed from [EPIC] Interactive mode is an usability desaster to [EPIC] Interactive mode is an usability disaster
Updated by okurz over 5 years ago
- Category changed from 124 to Feature requests
Updated by coolo about 5 years ago
- Status changed from In Progress to Resolved
We're done with this epic.
Updated by szarate almost 4 years ago
- Tracker changed from action to coordination
Updated by szarate almost 4 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html