Project

General

Profile

Actions

action #133562

closed

coordination #121855: [epic] Agama web interactive installation

Change hard coded product names in playwright test specs

Added by rainerkoenig over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2023-07-31
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Currently we have our Playwright tests with hard coded product names like here:

await expect(page.getByText("SUSE ALP Server")).toBeVisible({ timeout: 2 * minute });

That led to failures in the tests because in new builds the name changed to "SUSE ALP Dolomite". Nevertheless, hard coding product names that are subjected to change is not a good idea because it makes the pages stick to just one product even if they could be reused for another product. And with the next change of a name we have to modify code again.

ToDo

A better way seems to be putting the product name into an environment variable, e.g. AGAMA_PRODUCT (to avoid confusion with the openQA PRODUCT-setting) and then set take the value of this envirnment variable instead of hard-coding the product name. That means all Playwright code must be modified once and the script calls for Playwright must include setting this variable.

Acceptance criteria

AC1 All tests and POM pages that have hard coded product names are modified to use the new environment settings
AC2 All verification runs for the above changes passed

Actions #1

Updated by leli over 1 year ago

  • Status changed from Workable to In Progress
  • Assignee set to leli
Actions #2

Updated by leli over 1 year ago

  • Target version set to Current
Actions #3

Updated by leli over 1 year ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF