Initial curated itworx-knowledge-hub source from 3b1751d0d9dee551aa6994eee0093704dc334817

tests/e2e/specs/support/credentials.ts

@@ -0,0 +1,6 @@
+/** Fixed owner account created once by global-setup.ts and reused read-only by every
+ * spec/project (desktop and mobile alike) against the shared running stack. */
+export const OWNER_EMAIL = "eigenaar@itworx.e2e";
+export const OWNER_PASSWORD = ["correct", "horse", "battery", "staple", "e2e"].join("-");
+export const WORKSPACE_NAME = "ItWorx E2E Kennisbank";
+export const OWNER_DISPLAY_NAME = "E2E Eigenaar";

tests/e2e/specs/support/v2.ts

@@ -0,0 +1,60 @@
+import type { Page } from "@playwright/test";
+import { expect } from "@playwright/test";
+
+export async function expectAuthenticatedShell(page: Page): Promise<void> {
+  await expect(page.getByRole("button", { name: "Accountmenu" })).toBeVisible();
+}
+
+export async function openPrimaryNavigation(page: Page): Promise<void> {
+  const toggle = page.getByRole("button", { name: "Navigatie openen" });
+  // toggle.isVisible() alone does not auto-wait — calling it immediately after
+  // page.goto() can race the shell's first paint under load, silently no-op-ing on a
+  // mobile viewport where the toggle genuinely exists but has not rendered yet.
+  // Found via a real, reproducible flake in a full-suite run (V2-M2 shell audit),
+  // not by inspection. waitFor's own timeout distinguishes "not visible yet" from
+  // "never visible" (desktop, where the toggle stays CSS-hidden and the primary
+  // navigation is already on screen without it).
+  try {
+    await toggle.waitFor({ state: "visible", timeout: 2000 });
+  } catch {
+    return;
+  }
+  await toggle.click();
+}
+
+export async function followPrimaryNavigation(page: Page, name: string): Promise<void> {
+  await openPrimaryNavigation(page);
+  await page.getByRole("navigation", { name: "Hoofdnavigatie" }).getByRole("link", { name, exact: true }).click();
+}
+
+export async function openNewKnowledgePage(page: Page): Promise<void> {
+  await page.goto("/knowledge/new");
+  await expect(page.getByRole("heading", { name: "Nieuwe pagina" })).toBeVisible();
+}
+
+export async function fillMarkdown(page: Page, markdown: string): Promise<void> {
+  const editor = page.getByRole("textbox", { name: "Inhoud (Markdown)" });
+  // Explicit select-all + delete before Locator.fill(), rather than relying on
+  // fill()'s own clear heuristic: CodeMirror's contenteditable surface was not
+  // always fully cleared by fill() alone when it already had content, under mobile/
+  // touch emulation specifically — found via a real V2-M3 test where a second
+  // fillMarkdown() on an existing page's editor produced garbled
+  // old-content-plus-new-content on the chromium-mobile project only (not desktop,
+  // same code), not by inspection. Still uses fill() (not page.keyboard.type()) for
+  // the actual insertion: several existing specs fill markdown containing literal
+  // "[[...]]" wiki-link syntax, which would interact with CodeMirror's
+  // closeBrackets extension if typed via real keystrokes — fill() bypasses that
+  // keystroke-level extension entirely, matching this helper's prior behavior.
+  await editor.click();
+  await page.keyboard.press("ControlOrMeta+a");
+  await page.keyboard.press("Delete");
+  await editor.fill(markdown);
+}
+
+export function markdownEditor(page: Page) {
+  return page.getByRole("textbox", { name: "Inhoud (Markdown)" });
+}
+
+export async function readMarkdown(page: Page): Promise<string> {
+  return (await markdownEditor(page).locator(".cm-line").allTextContents()).join("\n");
+}