action #132989
closedcoordination #121855: [epic] Agama web interactive installation
Unify interactive installations in tests/yam/agama and its respective schedules
0%
Description
Motivation¶
We have different design for agama installation test in tests/yam/agama, it is better to unify these tests as they are doing the same. We might need to split functionality in an additional test module for booting with encryption for example. The exact test can be passed as a new setting.
Acceptance criteria¶
AC1: Unify interactive installations in tests/yam/agama and its respective schedules
Additional info:¶
Refer to Agama test job group
Updated by JERiveraMoya over 1 year ago
- Description updated (diff)
- Status changed from New to Workable
- Priority changed from Normal to High
- Target version set to Current
- Parent task set to #121855
Updated by zoecao over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to zoecao
Updated by zoecao over 1 year ago
- Status changed from In Progress to Workable
- Assignee deleted (
zoecao)
Move it back to workable list, learned some related code, but still no idea how to unify the testing.
Updated by tinawang123 over 1 year ago
- Status changed from Workable to In Progress
- Assignee set to tinawang123
Updated by syrianidou_sofia over 1 year ago
Note: The "playwright test $name" command will run any test that contains $name in the test filename. It would be better to include the whole filename in the openqa command. E.g.
"playwright test tests/lvm.spec.ts" instead of "playwright test lvm"
Updated by syrianidou_sofia over 1 year ago
After talking with Joaquin about PR: https://github.com/jknphy/e2e-agama-playwright/pull/12 in daily, I have named my new playwright test encrypted_lvm. This means that the agama_dolomite_lvm test will fail, because command "playwright test lvm" will run both lvm.spec.ts and encrypted_lvm.spec.ts . See comment https://github.com/jknphy/e2e-agama-playwright/pull/12#discussion_r1299642190
Updated by JERiveraMoya over 1 year ago
Updated by JERiveraMoya over 1 year ago
For the purpose of metrics I would prefer to just use the epics in the roadmap instead of subtasks, so with related ticket should suffice, it is not like in Agile you need to do everything and we are waiting for the subtask to be completed to close the parent task in this case.
For more advance stuff, perhaps to know how many remaining we have from tasks we could use labels in the future, but better to give some good thinking about how to use labels and coordinate that with our squad metrics.
Updated by JERiveraMoya over 1 year ago
- Related to action #134690: Enable logs upload for agama playwright tests added
Updated by tinawang123 about 1 year ago
- Status changed from In Progress to Resolved
Sub task has resolved.
Close this one.