add testing packages

[seokju-na]

Summary by cubic

Adds @wvb-playground/testing, a small, cross‑platform WebviewDriver for E2E tests with Playwright/Selenium/Appium drivers, and ships a runnable test suite for @wvb-playground/webview-hacker-news. This enables one set of cases to run across Electron, Tauri, Android, and iOS.

• New Features

  • New @wvb-playground/testing package exporting WebviewDriver plus createPlaywrightDriver, createSeleniumDriver, and createAppiumDriver with baseURL and timeout support.
  • @wvb-playground/webview-hacker-news now exports ./testing (dist-testing) with selectors, tiny assert helpers, and platform-agnostic cases that cover feed, sorting, post detail, voting, comments, profiles, filters, theme, back, and deep links.
  • Added data-testids across the Hacker News UI to match selectors (feed, posts, votes, comments, profile, theme, nav).
  • Build/workspace updates: tsdown configs, dist-testing/ output, and workspaces include packages/*.

• Dependencies

  • @wvb-playground/testing declares optional peers: playwright-core, selenium-webdriver, webdriverio.
  • @wvb-playground/webview-hacker-news adds vitest as an optional peer and depends on @wvb-playground/testing (workspace).
  • Lockfile updated.

^{Written for commit 838cc84. Summary will update on new commits.}

[cubic-dev-ai]

2 issues found across 30 files

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="packages/testing/package.json">

<violation number="1" location="packages/testing/package.json:55">
P2: `@types/selenium-webdriver` is redundant — `selenium-webdriver` v4+ bundles its own TypeScript types. This can cause type conflicts if the `@types` package version drifts from the actual `selenium-webdriver` version.</violation>
</file>

<file name="packages/testing/src/playwright.ts">

<violation number="1" location="packages/testing/src/playwright.ts:22">
P2: Compound CSS selectors (comma-separated) break under `:visible` — only the last segment gets the pseudo-class. E.g. `visible('button, a')` produces `button, a:visible`, matching all buttons regardless of visibility instead of only visible buttons/anchors.</violation>
</file>

<sub>You're on the cubic free plan with 18 free PR reviews remaining this month. Upgrade for unlimited reviews.

Re-trigger cubic</sub>

[cubic-dev-ai]

P2: @types/selenium-webdriver is redundant — selenium-webdriver v4+ bundles its own TypeScript types. This can cause type conflicts if the @types package version drifts from the actual selenium-webdriver version.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/testing/package.json, line 55:

<comment>`@types/selenium-webdriver` is redundant — `selenium-webdriver` v4+ bundles its own TypeScript types. This can cause type conflicts if the `@types` package version drifts from the actual `selenium-webdriver` version.</comment>

<file context>
@@ -0,0 +1,62 @@
+    }
+  },
+  "devDependencies": {
+    "@types/selenium-webdriver": "^4.1.28",
+    "playwright-core": "^1.49.0",
+    "selenium-webdriver": "^4.27.0",
</file context>

[cubic-dev-ai]

P2: Compound CSS selectors (comma-separated) break under :visible — only the last segment gets the pseudo-class. E.g. visible('button, a') produces button, a:visible, matching all buttons regardless of visibility instead of only visible buttons/anchors.

Prompt for AI agents

Check if this issue is valid — if so, understand the root cause and fix it. At packages/testing/src/playwright.ts, line 22:

<comment>Compound CSS selectors (comma-separated) break under `:visible` — only the last segment gets the pseudo-class. E.g. `visible('button, a')` produces `button, a:visible`, matching all buttons regardless of visibility instead of only visible buttons/anchors.</comment>

<file context>
@@ -0,0 +1,56 @@
+  const { baseURL, defaultTimeoutMs } = options;
+  // `:visible` resolves the first *visible* match — important when a test id
+  // exists in both the desktop and mobile chrome.
+  const visible = (selector: string) => page.locator(`${selector}:visible`).first();
+  const timeout = (opts?: WaitOptions) => opts?.timeoutMs ?? defaultTimeoutMs;
+
</file context>

Suggested change

	const visible = (selector: string) => page.locator(`${selector}:visible`).first();
	const visible = (selector: string) => page.locator(`:is(${selector}):visible`).first();