We need to review and update the release criteria and test cases for the current implementation of the webUI for Workstation Change.
As of right now, the storage workflows are:
Broadly speaking, I think we need to review the 'guided partitioning' criteria and test cases to see exactly how to map the new flows onto them, and clone the 'custom partitioning' test case set again for cockpit-based partitioning, plus some criteria tweaks.
I am working through this at present. So far I've done minor and hopefully uncontroversial tweaks to the release criteria, and I've cloned the custom partitioning test case set in the install matrix template and implemented the three easiest test cases, with some new templates. The rest of the test case links are still to pages that don't exist, at present.
Regarding criteria, I wonder whether we want to have yet another section for cockpit-based UI? What if we grouped custom+blivet+cockpit together, and called it advanced or manual partitioning? That way our criteria would talk about guided (the simpler workflow where you don't create partitions and specify mount points yourself) and manual partitioning (where you create partitions and specify mount points yourself), and list requirements for each. It wouldn't matter which particular frontend+backend is used for manual partitioning. If some features are not available in one of the UIs, we would add "when available" to the criterion.
that is essentially the approach i'm taking so far.
Metadata Update from @adamwill: - Issue tagged with: anacondawebui
Metadata Update from @adamwill: - Issue priority set to: critical (was: normal) - Issue set to the milestone: Fedora 40
I did some more on this today, adding a 'preserve /home' test case (and tweaking the existing ones a bit) and doing some more organization on the matrix. going to add more missing cases tomorrow.
Metadata Update from @adamwill: - Issue untagged with: anacondawebui - Issue priority set to: normal (was: critical) - Issue set to the milestone: None (was: Fedora 40)
Metadata Update from @adamwill: - Issue priority set to: critical (was: normal) - Issue set to the milestone: Fedora 40 - Issue tagged with: anacondawebui
Hi, I would like to know the status of this. Do you think you have enough time to adapt to this change or not?
I kinda suspended it because of https://github.com/rhinstaller/anaconda-webui/pull/72 - I expected that PR to change the UI 'flow' significantly in some cases (especially regarding mount point assignment), and I didn't want to have to rewrite the test cases twice. Now that change has made it to the images (I believe) I'm going to pick this up and try to finish the changes today or tomorrow. We're then planning a test week starting on Thursday - https://pagure.io/fedora-qa/issue/764
Update: FESCo today decided to defer the Change to F41. So this is no longer an appropriate change for F40 (unless something surprising happens suddenly). I'll unpick the changes I made to the matrices and release criteria tomorrow, though we can keep the test cases for Test Days and to put back in future.
I've unpicked the changes for F40. I created the F41 Beta criteria page before doing so, so that still has the webui stuff (seemed a good idea). Let's push this ticket out to F41, assuming for now the Change will still happen in F41 (it seems there's a chance it won't, but let's pretend for now).
Metadata Update from @adamwill: - Issue priority set to: normal (was: critical) - Issue set to the milestone: Fedora 41 (was: Fedora 40)
Login to comment on this ticket.