[athul-rs]

What

• Optional vitest / playwright rig groups skip (exit 5, "nothing collected") when their workdir has no node_modules.
• Required Node groups are unchanged: they still run npx --no-install and fail when their install step is missing.

Why

• Since [P0-P4] Remove Ant Design from the OSS frontend (shadcn/ui + Midnight Bloom) #2212, the optional ui e2e group reports 1 error and 0 tests on every ci-test run, main included. CI never installs tests/e2e/ui, so npx --no-install playwright test aborts with npx canceled due to missing packages ... ["playwright@..."]. The first main run after [P0-P4] Remove Ant Design from the OSS frontend (shadcn/ui + Midnight Bloom) #2212 merged (run 33623862758, 2026-09-02) already shows it.
• tests/groups.yaml says the group is optional so that "no browsers installed (or no node_modules) must skip, not gate merges", but the rig only skipped when npx itself was absent.

How

• _node_command in tests/rig/cli.py returns the existing exit-5 skip for an optional group whose workdir/node_modules is not a directory. This is the same convention the rig already uses when npx is missing.
• The ui suite stays in the repo for local runs: install tests/e2e/ui and it runs as before.

Can this PR break any existing features. If yes, please list possible items. If no, please explain why. (PS: Admins do not merge the PR without this section filled)

• No. Only optional Node groups without node_modules change, from a red error row to a skip. Today that is only ui. The required frontend vitest group is excluded by the optional check, and CI installs its dependencies (UN-4183 [MISC] Run frontend typecheck and tests in CI and make the frontend test group required #2302), so it runs exactly as before. Exit 5 already counts as non-failing for optional groups only.

Database Migrations

• None

Env Config

• None

Relevant Docs

• tests/groups.yaml comment on the ui group

Related Issues or PRs

• UN-4469
• [P0-P4] Remove Ant Design from the OSS frontend (shadcn/ui + Midnight Bloom) #2212 added the ui group
• UN-4183 [MISC] Run frontend typecheck and tests in CI and make the frontend test group required #2302 (UN-4183) added the install step for the frontend vitest group
• UN-4345 [FEAT] Frontend v1 E2E harness and the frontend-v1-e2e group #2355 (UN-4345) adds the install step for the new ui-v1 group

Dependencies Versions

• None

Notes on Testing

• Three new tests in tests/rig/tests/test_cli.py: optional group without node_modules skips; required group without node_modules still runs; optional group with node_modules runs.
• The skip test failed before the fix. With the optional guard deleted, the required-group test and both existing command-shape tests fail.
• Rig self-tests: 118 passed, 1 skipped.
• This PR's ci-test run is the end-to-end check: the ui group should show as skipped, not as an error.

Screenshots

• N/A

Checklist

I have read and understood the Contribution Guidelines.

🤖 Generated with Claude Code

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[greptile-apps]

via Greptile

Confidence Score: 5/5

[Medium impact] The PR appears safe to merge.

Summary

Optional Node test groups now skip when their working directory has no node_modules.

• Optional Node test groups skip when their packages are missing.

_{Reviews (1) · Last reviewed commit: "UN-4469 [FIX] Skip optional Node groups ..." · Reviewed by Greptile}

[github-actions]

Unstract test results

Per-group results

Status	Group	Tier	Passed	Failed	Errors	Skipped	Duration (s)
✅	e2e-api-deployment	e2e	3	0	0	0	8.7
✅	e2e-coowners	e2e	1	0	0	0	1.3
✅	e2e-etl	e2e	1	0	0	0	16.4
✅	e2e-login	e2e	2	0	0	0	1.1
✅	e2e-prompt-studio	e2e	1	0	0	0	4.6
✅	e2e-smoke	e2e	2	0	0	0	1.0
✅	e2e-workflow	e2e	1	0	0	0	14.5
✅	frontend	unit	625	0	0	0	17.9
✅	integration-backend	integration	638	0	0	26	47.0
✅	integration-connectors	integration	1	0	0	7	7.3
✅	integration-workers	integration	179	0	0	1	32.1
⚪	ui	e2e	1	0	0	0	0.0
✅	unit-backend	unit	1567	0	0	1	51.7
✅	unit-connectors	unit	82	0	0	0	11.9
✅	unit-core	unit	281	0	0	0	3.3
✅	unit-platform-service	unit	18	0	0	0	2.8
✅	unit-rig	unit	123	0	0	0	5.6
✅	unit-runner	unit	12	0	0	0	3.2
✅	unit-sdk1	unit	843	0	0	0	43.3
✅	unit-tool-sidecar	unit	8	0	0	0	1.9
✅	unit-workers	unit	1445	0	0	1	125.4
	TOTAL		5834	0	0	36	401.2

Critical paths

⚠️ Critical paths not yet covered

• workflow-execution-fan-out — Multi-file workflow execution fans out to file-processing workers and rejoins. (declared coverage: no groups declared)

✅ Covered critical paths

• auth-login — covered by e2e-login
• adapter-register-llm — covered by integration-backend
• workflow-author — covered by integration-backend
• co-owner-manage — covered by integration-backend, e2e-coowners
• workflow-create-execute — covered by e2e-workflow
• api-deployment-provision — covered by integration-backend
• api-deployment-auth — covered by integration-backend
• api-deployment-run — covered by e2e-api-deployment
• mcp-server-auth — covered by integration-backend
• mcp-platform-auth — covered by integration-backend
• platform-key-whoami — covered by integration-backend
• prompt-studio-author — covered by integration-backend
• prompt-studio-fetch-response — covered by e2e-prompt-studio
• connector-register-test — covered by integration-backend
• pipeline-etl-execute — covered by e2e-etl
• usage-aggregate-read — covered by integration-backend
• usage-token-tracking — covered by e2e-api-deployment
• callback-result-delivery — covered by e2e-api-deployment

[athul-rs]

Parking this. Reviewers are split on skipping the v0 ui group: a skip would hide that the suite isn't running, while the current error at least shows it. The group doesn't block CI, and the v1 E2E group from #2355 installs Playwright itself and replaces this suite. Reopen if Hari or Jaseem want the skip before v0 is retired.