IVS-31 - Added Playwright tests

[rw-bsi]

• Playwright scaffolding
• 2 example test scenarios (one Django Admin, one Validate UI)

Run locally with make e2e-test

[aothms]

Nice

Two questions:

• how is this hooked into e.g github actions? I don't see any changes there or reference to the new makefile entries
• where does the slowness come from?

[aothms]

Minor thing, but should we use?

Suggested change

	const { test, expect } = require('@playwright/test');
	import { test, expect } from '@playwright/test';

(and rename file to .mjs probably)

At least that's what I'm used to in 2025, but I guess it's not a very significant thing here

[rw-bsi]

Agree - we should switch that in all UI's, maybe at package.json level and keep .js extensions?

https://nodejs.org/docs/latest/api/packages.html#type

[civilx64]

Yes, looks like we need to keep *.js extensions as the tests do not get discovered with .mjs.

[rw-bsi]

Nice

Two questions:

• how is this hooked into e.g github actions? I don't see any changes there or reference to the new makefile entries

It's not in GH Actions yet - this PR will add e2e scaffolding and sample tests, next is integration in CI/CD pipeline
(see here for example Scorecards pipeline)

• where does the slowness come from?

I assume spinning up Django with migrations - locally it takes 15s to start frontend/backend and 2s to run 3 tests
(see here for again Scorecards CI/CD integration example - bulk is packages and browsers)

We could speed it up by actually testing against the Docker images

[civilx64]

We could speed it up by actually testing against the Docker images

Or we could cache the environment setup to speed things up.