action #132884
Updated by JERiveraMoya over 1 year ago
#### Motivation Define a POM to handle the product selection screen:  #### Scope Installations of Dolomiteand ALP Micro (Dolomite), ALP Server and Tumbleweed using Agama for all architectures available in openQA (s390x and ppc64le excluded for now). #### Acceptance criteria **AC1**: Get familiar with Playwright and use the playwright test generator to get first version of your code. **AC2**: Compare Locate only the auto-generated code related with existing non-POM code in existing test. user definition and user creation and convert it to Page Object Model. **AC3**: Replace with POM code Add some dummy test (because it will not be a test for itself in existing test. the future, will be part of other tests) test to our QE repo [e2e-agama-playwright](https://github.com/jknphy/e2e-agama-playwright) using that POM. #### Additional information Playwright documentation: https://playwright.dev/docs/intro Playwright documentation - Page Object Model: https://playwright.dev/docs/pom How to use playwright with Agama: https://github.com/openSUSE/agama/blob/master/playwright/README.md Notice that for development in your system, you will need to install playwright and run `npx playwright test`, due to in the live iso the command to run is different as described in doc above, `playwright test`. Notice that some part might done for the CI in https://github.com/openSUSE/agama/tree/master/playwright/tests regarding the user and regarding the install buttom at the end of https://github.com/openSUSE/agama/blob/master/playwright/tests/take_screenshots.spec.ts but what we need is to put that logic as POMs. Existing test for CI shouldn't be touched for now, but those file might give us some inspiration in case with playwright test generator would not get the best locators. IMPORTANT: While #130000 is not yet resolve, please add a call to yupdate in your test so live-cd can pick the new test/code you implement from a branch