From Fedora Project Wiki

Description

This is to verify that Anaconda can perform an installation controlled by the user via a Web browser.

While Anaconda traditionally supported remote installation via a remote desktop client like VNC or RDP, browser based remote access does not require a specialized client application and should be more efficient.

This page contains the baseline test case and several variants. Run the baseline first, then any variants you want to cover; each variant only lists what it changes compared to the baseline.

Setup

  1. On one system, prepare any F45 atomic desktop media for booting the installer (anything except Live.iso or dvd.iso/netinst.iso).
  2. On another system, prepare a modern Web browser, like Firefox or Chrome
  3. Both systems can be either physical machines or VMs, but need to be able to communicate over the network with each other.

How to test

  1. In the initial boot menu screen, append inst.webui.remote and inst.webui.remote.pin=(pin) boot options and boot the installer
  2. The installer will not show the UI locally & waits for the user to connect with a Web browser.
  3. One or multiple IP addresses should be listed on the screen.
  4. If you are unsure about the IP address to connect to or for some reason you don't see the address listing on your screen, use ctrl+alt+F2 to reach a root console and the ip a command to find the IP address of the machine.
  5. On the other system, point your web browser to the IP address. If more are available, just pick one of them.
  6. A self-signed certificate warning might show up. This is expected due the ephemeral self-signed certificate that is in use. Confirm that you know what you are doing and go past the warning.
  7. A login screen should load, use the pin you have specified via boot options to log in.
  8. Proceed and complete the installation using the Anaconda Web interface from you Web browser.
  9. Boot the new system and check it starts correctly.

Expected Results

  1. After passing the appropriate boot options the installer does not start the UI locally, it is only possible to connect remotely from a browser
  2. You can connect with a Web browser and see the graphical installation
  3. The installer displays all expected screens and works properly
  4. The installation completes successfully
  5. The installed system boots into working Fedora atomic desktop installation

Known issues

  1. Once inst.webui.remote and inst.webui.remote.pin=(pin) boot options are passed, the local screen is grey (as no local Web UI is started) and there are no hints what to do next

Optional

Reconnect to a running installation from the same browser

This is a variant of the baseline test case above. Read the baseline instructions first.

After first connecting to installation remotely, disconnect and then try connecting again.


How to test (differences)

  1. Once you have successfully connected to the installation following the base test case, disconnect. This can be done for example by closing the browser tab or temporarily disabling network connectivity for either of the two systems.
  2. Connect back to the running installation, using the same IP address and pin.

Expected Results (differences)

  1. Once reconnected, it should be possible to finish the installation.
  2. If the installation was not yet started before the disconnect, it will be necessary to go over all the configuration screens again.
  3. If you see any discrepancies or errors during this second pass, please note those in your test report.
  4. If the installation was already started, the progress screen or the "installation done" screen should be visible.

Browser content scaling

This is a variant of the baseline test case above. Read the baseline instructions first.

Unlike the locally running Web UI, with remote access the remote browser can have an arbitrary window size, geometry or scaling factor.

How to test (differences)

  1. Follow the baseline test case and once successfully connected, try resizing the browser window to weird but reasonable shapes & play with browser scaling percentage, again in a seasonable range, that could be expected to be used by at least some users.

Expected Results (differences)

  1. The Anaconda Web UI should work in all reasonably sized viewport and content scaling factors.
  2. If you do find a combination if window geometry and scaling that makes the UI unusable, please note it as a test failure, including the approximate window geometry + scaling, ideally including a screenshot.

Connect using different browsers

This is a variant of the baseline test case above. Read the baseline instructions first.

Try to do the baseline use case using multiple browsers, if you have more than one available.

How to test (differences)

  1. Follow the baseline test case using browsers of you choice, until you run out of browsers or your patience.

Expected Results (differences)

  1. Mainstream browsers like Firefox or Chrome based browser are expected to work.
  2. If you have either issues with connecting to the installation or see graphical glitches during the testing, please record this as a test failure, noting what went wrong & which browser + browser version.

Connect from a mobile browser

This is a variant of the baseline test case above. Read the baseline instructions first.

In this case the idea is to see how common browser on mobile devices behave when connecting to the running Fedora installation remotely.

NOTE: This requires the mobile device to be able to reach the system running the installation, which might not be easy to pull off (installation running in a VM on a laptop might not be easily reachable to a smart-phone, even if both are connected to the same WiFi network).

How to test (differences)

  1. The easiest setup for this would be a local network that has both Ethernet and a WiFi segment.
  2. Connect a spare physical machine to the local network over Ethernet and start remote installation on it, following the baseline test case.
  3. Connect your smart-phone to the WiFi segment of the same network and use the IP in a mobile browser or your choice & then the pin to authenticate.
  4. If you can successfully reach the machine running the installation from the browser on your phone - congratulation, now you can run the baseline test case! :)

Expected Results (differences)

  1. If you can manage to set things up in such a way that the phone can reach the machine running the installation, all should ideally run the same as when connecting from a desktop browser.
  2. If there are however any issues, like unskippable SSL errors, unusable layout, sudden disconnectes, etc - please mark the test and failed, including details such a phone type & phone OS version and browser used.



References

Retrieved from "https://fedoraproject.org/w/index.php?title=QA:Testcase_Anaconda_User_Interface_Remote_WebUI&oldid=789330"