QA » openQA Project » openQA Tests » qe-yam

See https://jira.suse.com/browse/SLE-16263
https://jira.suse.com/browse/SLE-16358
https://jira.suse.com/browse/SLE-16359

We should test it in TW and SLES. TW has new button being added, SLES requires key presses to open newly added functionality.

Content of trello cards:
Let's continue with https://trello.com/c/nF3fJyI3/2186-8-shouldhave-an-easy-way-to-check-or-reconfigure-the-installer-settings

1. Think about how user is going to use it?
2. When user is going to realize and need it?
3. How and where to change it?
4. What are the limits?
5. How many times you might need to ...

Ideas¶

@ladislavslezak : maybe we could implement it similarly to the debugger support. If you press the Ctrl+Alt+Shift+D shortcut a debugger window pops up.

We do not need to implement a GUI dialog for it, this is for experts or in corner cases so we can mention it in the documentation or publish a TID for specific cases ("If you need to configure the network then press combination and write command 'foo',...").

It would provide a command line with prompt (an IRB session?), there you could write predefined commands (configure network) or plain Ruby commands (so it would be a generic tool, you could basically inspect or change everything, similar to the debugger).

At start it would print a list of available commands (or at least something like `type "help" for help) so it provides some guidance to the users.

Pull Requests¶

• The main part: https://github.com/yast/yast-installation/pull/905
• A small fix in libyui-ncurses: https://github.com/libyui/libyui-ncurses/pull/111 (avoid mixing script with the supposedly deactivated ncurses UI after the UI.CloseUI call)
• A simple tool for switching windows: https://github.com/yast/yast-x11/pull/23 (do an Alt-Tab equivalent from a script)
• Libyui Keyboard Shortcuts;
  • https://github.com/libyui/libyui/pull/179
  • https://github.com/libyui/libyui-ncurses/pull/113
  • https://github.com/libyui/libyui-qt/pull/145
  • https://github.com/yast/yast-ycp-ui-bindings/pull/66
  • https://github.com/yast/yast-ruby-bindings/pull/268
  • https://github.com/yast/yast-ruby-bindings/pull/270

=============
The discussion happens at https://jira.suse.com/browse/PM-1895
https://jira.suse.com/browse/SLE-16263
https://jira.suse.com/browse/SLE-16358

What do we need?¶

The current installer is capable of many more things that are available in the UI. They are either done already in Linuxrc or entered as a Linuxrc parameter but they are in fact ENV variables. We need to re/set some of these and also inspect theirstate as people can easily mistype them.

How can we do that?¶

Ideally by providing expert settings / debugger that shows that in UI. The idea is to replace the [Network Settings...] button by an icon and have everything there. How to show that is part of this research. Ideally on all screens.

Some of the features might need additional action, e.g., reloading the same step or even restarting YaST. Explore the needs, do not over-engineer though. We have the support already because of self-update.

This is a research project, we need to explore new ideas, try new things, offer options and implement it or throw away. Try to find out what would help the most. Good candidates are options that you would expect to have UI, but you have to configure them on Linuxrc commandline AND you find out too late, e.g., HTTP Proxy (bug/feature) or NTLM Authentication (feature).

Review¶

Here are my thoughts after going through all the cited documents

• https://github.com/yast/yast-installation/issues/898

Feel free to comment there.

============================