action #26918: [sle][functional][story] Why is the hotkey different in same build, same arch and same elements - openQA Tests (public) - openSUSE Project Management Tool

Actions

action #26918

closed

coordination #26912: [sle][functional][epic] test fails in partitioning - Different hotkey in same build, same arch and same elements

[sle][functional][story] Why is the hotkey different in same build, same arch and same elements

Added by SLindoMansilla over 7 years ago. Updated about 7 years ago.

Status:

Resolved

Priority:

Normal

Assignee:

Category:

Bugs in existing tests

Target version:

openQA Project (public) - Milestone 14

Start date:

2017-10-20

Due date:

% Done:

Estimated time:

Difficulty:

Description

User story¶

As a QA engineer, I want that, Yast, for the same build, same arch, same elements on screen and when I have done the same steps, I get the same hotkeys assigned to the same buttons in different jobs, so that test automation about Yast is possible.

Acceptance criteria¶

AC1: The reason that causes the different hotkey is known
AC2: The test module partitioning_raid passes, soft-fail or at least does not fail on this hotkey.

Tasks¶

Investigate why the hotkey is different (1-4h). You can use:
- https://en.opensuse.org/openSUSE:YaST_development_Misc_YDialogSpy (yast element tree analyzer)
- https://de.opensuse.org/SDB:YaST_Tricks (log for hotkey assignation)
If it is a product bug
- Report it (0.2-1h)
- Add soft-fail and workaround (1-4h)
If it is a test issue
- Adapt the test (1-4h)