openQA Project - coordination #14626: [epic] backend and console capabilities interface to increase extensibility and code reuse
[qe-core][tools][functional][epic] Refactor use of backends
Currently we use some backends which all need to be treated differently but also share commonalities which are not properly reflected in code, e.g. all backends that do not have a local tty but rely on remote connections to the SUTs.
- AC1: No "if's" on multiple specific backends but replace by proper characteristic what these backends share
Updated by SLindoMansilla about 4 years ago
- Assignee set to mgriessmeier
- Target version changed from Milestone 27 to Milestone 28
We need to create sub-tasks for checking that check_var('BACKEND', ...) and check_var('ARCH', ...) is not being used, at least outside lib/utils/backend,
Updated by szarate almost 3 years ago
See for the reason of tracker change: http://mailman.suse.de/mailman/private/qa-sle/2020-October/002722.html
Updated by okurz over 2 years ago
- Status changed from Resolved to Workable
- Assignee deleted (
Now I think you are going a bit too far. Just because no one defined more subtasks I would not call this resolved. There are a lot of test modules using backedn specific calls.