action #166586
closedcoordination #163919: [epic] Create automation setup for testing Agama
Create agama installation selecting gnome pattern
0%
Description
Motivation¶
Based on findings in https://progress.opensuse.org/issues/166133 we can arrange the system before interacting via the web framework.
In this ticket we will arrange the system using actions from AC2 manually done (if in that ticket still we didn't create the automation for that, but keep checking progress on it regularly!) and then we will focus mainly here on installing the desktop gnome
Acceptance criteria¶
- AC1: Installation is arranged (manually importing existing profile or automated depending on progress in related ticket).
- AC2: (Main effort in this ticket goes to) provide automation in TS using POM to select gnome desktop in Software section by selecting the corresponding pattern.
- AC3: Scenario is enabled in O3 for all architectures.
- AC4: Validation could include something simple like a needle to check the correct desktop.
Additional information¶
agama documentation for arrange the installation (and save all the steps to create user, type password, basically is about to load the profile that we use in auto-installation, but at the moment we cannot proceed passing in kernel parameters, it is no implemented, needs to be done in the interactive installation changing ttys).
For more info about this topic, ask @lmanfredi.
There is prototype attempt with needles that we can check just to see the screens:
https://openqa.opensuse.org/tests/4451638#step/agama/13
but this is not connected with our work, it is just an example here to show some screenshots, we will do this with puppeteer.
Updated by JERiveraMoya 2 months ago
Could you please summarize your progress/learning with this ticket?
I didn't see any open PR yet so we can see where we are and help each other with the current knowledge in the team in this area.
Updated by JERiveraMoya 2 months ago · Edited
I would recommend to push a draft with the code as soon as you have the time, there are too many things we are changing everyday in the repo, things that we learn, having some idea where you are with the code would help to speed up the process. The POM is not strictly needed in your first iteration, you can show the script you run first and see that it works and as last step convert it to POM (it is just a refactor wrapping up what already works, and in some cases we have accepted code without Page Object Model, we can do in other tickets depending how is going current one).
Updated by zoecao 2 months ago · Edited
PR for this ticket:
https://github.com/jknphy/agama-integration-test-webpack/pull/19
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/20257
Will add gnome desktop validation after the job finishes installation.
Updated by JERiveraMoya 2 months ago
- Tags changed from qe-yam-sep-sprint to qe-yam-oct-sprint
It is a good start regarding TypeScript part, we need verification for other architecture and code review for TS.
Updated by JERiveraMoya about 2 months ago
There is some review comment, let's continue with this to see what we can reach in the following days and considering narrowing the scope depending on that to make more fluent to work in this new tasks. Do not hesitate to ask questions about new changes in the typescript project from last week if something is not clear.
I would recommend to remove log/ node_modules/ and even dist/ folders and to follow from the start the instructions in the README due to new bump of the version.
Updated by zoecao about 1 month ago
Submitted a new PR and close the [last one] because of big changes in upstream.
NEW PR: https://github.com/jknphy/agama-integration-test-webpack/pull/34
Adjusting the PR based on VRs: https://openqa.opensuse.org/tests/overview?version=agama-9.0&distri=opensuse&build=chcao_0
@JERiveraMoya based on the discuss in the sync up meeting last Friday, we'll close this ticket and open new tickets for the remaining tasks, do you think it is fine to review these two PR, when PRs fine to merge, then close this ticket and open new ticket to the AC3,AC4? Or any other suggestions about it?
Updated by JERiveraMoya about 1 month ago
zoecao wrote in #note-9:
Submitted a new PR and close the [last one] because of big changes in upstream.
NEW PR: https://github.com/jknphy/agama-integration-test-webpack/pull/34
Adjusting the PR based on VRs: https://openqa.opensuse.org/tests/overview?version=agama-9.0&distri=opensuse&build=chcao_0
@JERiveraMoya based on the discuss in the sync up meeting last Friday, we'll close this ticket and open new tickets for the remaining tasks, do you think it is fine to review these two PR, when PRs fine to merge, then close this ticket and open new ticket to the AC3,AC4? Or any other suggestions about it?
yes, I agree, let's focus on having the automation enabled in devel job group for all the architectures (also for s390x btw) and merge this PR once you address code review.
Updated by JERiveraMoya about 1 month ago
- Tags changed from qe-yam-oct-sprint to qe-yam-nov-sprint
Updated by zoecao 19 days ago
@JERiveraMoya, I want to close this ticket and open a new one for others to take it, or reassign it to others directly, both are fine for me. I learned the current agama manual installation, the menu of software, and learned how to select patterns using POM. Now my new branch need a rebase to remove the .ts and .ts.map files, maybe creating a new PR would make it more simple. But running VR is still a long way. Do you think it is fine to close this ticket or hand over it to others directly? I would like to learn how others resolve this from their PR.
Updated by JERiveraMoya 19 days ago
- Status changed from In Progress to Resolved
zoecao wrote in #note-12:
@JERiveraMoya, I want to close this ticket and open a new one for others to take it, or reassign it to others directly, both are fine for me. I learned the current agama manual installation, the menu of software, and learned how to select patterns using POM. Now my new branch need a rebase to remove the .ts and .ts.map files, maybe creating a new PR would make it more simple. But running VR is still a long way. Do you think it is fine to close this ticket or hand over it to others directly? I would like to learn how others resolve this from their PR.
Thanks for mentioning @zoecao , you have practically all done in https://github.com/jknphy/agama-integration-test-webpack/pull/34/ I'm glad you learn something in the way.
Let's resolve this ticket and setup a test suite that use this new ts code, don't worry if it fails badly, right now all agama builds are pretty broken.
I will merge your PR and next days in some gap I will send few missing part or create a ticket for it and share with you.
Updated by JERiveraMoya 18 days ago
I applied this PR to remove some compilation errors, there were really a few things, it is a pity that nobody could guide you with such tiny remaining bits, we need to improve as a team with this. PR: https://github.com/jknphy/agama-integration-test-webpack/pull/37/files
I think you can now setup the test suite there more comfortable.