action #178396
closedcoordination #169654: [epic] Create test scenarios for Agama
Modify DASD puppeteer test to adapt new UI
0%
Description
Motivation¶
DASD configuration in S390x-zVM hosts has changed due the new Agama UI.
Now, Puppeteer test doesn't require to select the dasd device after enable it
Acceptance criteria¶
- AC1: s390x-zvm tests related to DASD can configure disk and start installation.
Additional information¶
Doing some manual check we know which steps are required.
- Configure Agama as usual.
- Go to Storage
No devices foundscreen should appear. - Click on
Manage DASD devices. - Click on First DASD device.
- Click on
Perform an action. - Click on
Activate. - Return to storage and or overview to start installation.
Updated by JERiveraMoya about 2 months ago
- Tags set to qe-yam-mar-sprint-fy25
- Status changed from New to In Progress
- Assignee set to jfernandez
- Parent task set to #169654
Updated by jfernandez about 2 months ago
Updated by JERiveraMoya about 2 months ago
Additional suggestions:
- Refresh using puppeteer.
- Handling how to mark as softfailure when something fails in puppeteer side (discuss with the squad some proposal before doing a big implementation).
Updated by jfernandez about 2 months ago
Refresh using puppeteer.
I tried to include page.reload() the web shows the storage UI correctly but Puppeteer is not able to continue the execution, probably by some broken locators or execution trace.
Handling how to mark as softfailure when something fails in puppeteer side (discuss with the squad some proposal before doing a big implementation).
I'm not sure that we should do that, Puppeteer is the test itself if the test fails the job should.
In any case, the option that comes to my mind could be to parse Puppeteer return codes or in lack of this the Puppeteer output/spec and mark the test softfailed in case a known condition occurs.
Updated by JERiveraMoya about 1 month ago
- Status changed from In Progress to Resolved