action #134228
Updated by JERiveraMoya 9 months ago
#### Motivation Currently, we are using the upstream take_screenshots.spec.ts for the agama Tumbleweed default installation. We should create our own default installation test that will utilize all the POMs created so far and the user/password aligned with Yam::agama::agama_base. Latest run for existing test: https://openqa.opensuse.org/tests/latest?arch=aarch64&distri=alp&flavor=agama-live-openSUSE-Playwright&machine=aarch64&test=agama_tumbleweed&version=agama-3.0-staging Besides create new test and necessary POMs we should take care of not repeating the configuration of default user and root in each test. #### Acceptance criteria **AC1**: Create agama_dolomite and modify agama_tumbleweed to be our default installations with Playwright not using CI tests (ie: take_screenshots.spec.ts) **AC2**: Do not import `expect` on top as the validation should be done at the Page level. **AC3**: Extract the configuration of user name and password and root password to not repeat it in each test. **AC4**: Extract the part of the installation as well in order to not repeat it in each test. #### Suggestions - we can use main-page (all our Sync CI tests would use `-` instead of `_`. To distinguish better we can wait and sync our test with current change in upstream project and communicate with developers, so we can just use that simple rule. - Extraction (only if they are really running in AC3 and AC4 could be just some calls to methods in new Page Object Models (ie that while loop should be insider some page method) that represent the installation process, other option would be to use shared libraries like the example under lib/ but better not using shared libraries, as we know how this could go really wrong... upstream project)