Skip to content

[Port to dtq-dev] Playwright tests: run with the LINDAT customer config - #1702

Closed
jr-rk wants to merge 1 commit into
dtq-devfrom
backport-lindat-1408-to-dtq-dev
Closed

jr-rk wants to merge 1 commit into
dtq-devfrom
backport-lindat-1408-to-dtq-dev

Conversation

@jr-rk

@jr-rk jr-rk commented Nov 3, 2026

Copy link
Copy Markdown

Notice: Not recommended to merge: dtq-dev deliberately switched the UI tests from LINDAT to DEFAULT in PR 1372, and this change reverses that.

References

  • Port of dataquest-dev/dspace-angular PR 1408 from customer/lindat (commit 7772fa7)
  • Reverses part of dtq-dev PR 1372 (commit af0c70f)

Description

.github/workflows/playwright-tests.yml sets NAME: LINDAT instead of NAME: DEFAULT, so dspace-ui-tests runs with its LINDAT customer constants.

Instructions for Reviewers

List of changes in this PR:

  • Commit 7772fa7 cherry-picked with -x, no conflicts. The patch is identical to the source commit.

Problems

  • dtq-dev UI tests would check LINDAT-specific UI against a generic dtq-dev build.

How to test: run the Playwright tests workflow; the job uses the LINDAT config from dspace-ui-tests.

AI Disclosure

  • No
  • Yes

Claude Code made the cherry-pick and wrote this description. The net diff was checked against customer/lindat.

Co-authored-by: Matus Kasak <matus.kasak@dataquest.sk>
(cherry picked from commit 7772fa7)
@jr-rk jr-rk self-assigned this Nov 3, 2026
@jr-rk

jr-rk commented Nov 3, 2026

Copy link
Copy Markdown
Author

@Kasinhou DEFAULT or LINDAT is correct for dtq-dev? Check References in PR body.

@jr-rk
jr-rk marked this pull request as ready for review November 3, 2026 07:30
@jr-rk
jr-rk removed the request for review from milanmajchrak November 3, 2026 07:32
@jr-rk

jr-rk commented Nov 3, 2026

Copy link
Copy Markdown
Author

DEFAULT is correct for dtq-dev

@jr-rk jr-rk closed this Nov 3, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants