@le-space/playwright 0.9.2 → 0.9.4

package/index.d.ts

@@ -133,6 +133,13 @@ interface RelayButtonDriverOptions {
     deleteButtonName?: string;
     refreshButtonName?: string;
     advancedToggleName?: string;
+    /**
+     * The distance in CSS pixels the widget treats as a drag rather than a tap.
+     * Kept as an option because it is the widget's number, not the test's:
+     * `dragThreshold` in `fab-position.ts`. A driver that guessed it would drive
+     * a press the widget still reads as a click.
+     */
+    dragThresholdPx?: number;
 }
 interface ProvisionRelayOptions {
     accountAddress: string;
@@ -267,6 +274,59 @@ declare class RelayButtonDriver {
     readonly page: Page;
     readonly options: Required<RelayButtonDriverOptions>;
     constructor(page: Page, options?: RelayButtonDriverOptions);
+    /** The launcher itself — the thing a consumer places, and now drags. */
+    launcher(): Locator;
+    /**
+     * Where the launcher is, in viewport coordinates.
+     *
+     * The widget positions it with `position: fixed` and its own offsets, so
+     * there is no layout box on any wrapper to read — an earlier consumer tried
+     * exactly that and got 0×0, because a fixed child leaves its parent empty.
+     * The launcher's own box is the only honest source.
+     */
+    launcherBox(): Promise<{
+        x: number;
+        y: number;
+        width: number;
+        height: number;
+    }>;
+    /**
+     * Drag the launcher by an offset, as a finger or a mouse would.
+     *
+     * Several intermediate moves rather than one jump: the widget follows
+     * `pointermove` and decides between a tap and a drag on the distance
+     * travelled, so a single move from A to B exercises neither the threshold nor
+     * the clamping on the way. `steps` is deliberately low by default — enough to
+     * cross the threshold and to move afterwards, few enough to stay quick.
+     *
+     * Returns the box before and after, because every assertion worth making
+     * compares the two and reading it twice at the call site invites reading it
+     * at the wrong moment.
+     */
+    dragLauncherBy(dx: number, dy: number, options?: {
+        steps?: number;
+    }): Promise<{
+        before: {
+            x: number;
+            y: number;
+            width: number;
+            height: number;
+        };
+        after: {
+            x: number;
+            y: number;
+            width: number;
+            height: number;
+        };
+    }>;
+    /**
+     * Press and move less than the threshold — a tap, as far as the widget is
+     * concerned, however jittery the hand holding the phone.
+     *
+     * This is the half that is easy to leave untested and expensive to get wrong:
+     * a launcher that reads a one-pixel wobble as a drag never opens at all.
+     */
+    tapLauncherWithWobble(): Promise<void>;
     deployButton(): Locator;
     instance(instanceName: string): Locator;
     /**

package/index.js

@@ -297,9 +297,72 @@ var RelayButtonDriver = class {
       deployButtonName: options.deployButtonName ?? "Deploy Relay",
       deleteButtonName: options.deleteButtonName ?? "Delete",
       refreshButtonName: options.refreshButtonName ?? "Refresh",
-      advancedToggleName: options.advancedToggleName ?? "Advanced"
+      advancedToggleName: options.advancedToggleName ?? "Advanced",
+      dragThresholdPx: options.dragThresholdPx ?? 6
     };
   }
+  /** The launcher itself — the thing a consumer places, and now drags. */
+  launcher() {
+    return this.page.getByRole("button", { name: this.options.launcherName });
+  }
+  /**
+   * Where the launcher is, in viewport coordinates.
+   *
+   * The widget positions it with `position: fixed` and its own offsets, so
+   * there is no layout box on any wrapper to read — an earlier consumer tried
+   * exactly that and got 0×0, because a fixed child leaves its parent empty.
+   * The launcher's own box is the only honest source.
+   */
+  async launcherBox() {
+    const launcher = this.launcher();
+    await launcher.waitFor({ state: "visible", timeout: 3e4 });
+    const box = await launcher.boundingBox();
+    if (!box) throw new Error("The relay button launcher has no bounding box; is it rendered?");
+    return box;
+  }
+  /**
+   * Drag the launcher by an offset, as a finger or a mouse would.
+   *
+   * Several intermediate moves rather than one jump: the widget follows
+   * `pointermove` and decides between a tap and a drag on the distance
+   * travelled, so a single move from A to B exercises neither the threshold nor
+   * the clamping on the way. `steps` is deliberately low by default — enough to
+   * cross the threshold and to move afterwards, few enough to stay quick.
+   *
+   * Returns the box before and after, because every assertion worth making
+   * compares the two and reading it twice at the call site invites reading it
+   * at the wrong moment.
+   */
+  async dragLauncherBy(dx, dy, options = {}) {
+    const before = await this.launcherBox();
+    const steps = Math.max(2, options.steps ?? 8);
+    const startX = before.x + before.width / 2;
+    const startY = before.y + before.height / 2;
+    await this.page.mouse.move(startX, startY);
+    await this.page.mouse.down();
+    for (let step = 1; step <= steps; step += 1) {
+      await this.page.mouse.move(startX + dx * step / steps, startY + dy * step / steps);
+    }
+    await this.page.mouse.up();
+    return { before, after: await this.launcherBox() };
+  }
+  /**
+   * Press and move less than the threshold — a tap, as far as the widget is
+   * concerned, however jittery the hand holding the phone.
+   *
+   * This is the half that is easy to leave untested and expensive to get wrong:
+   * a launcher that reads a one-pixel wobble as a drag never opens at all.
+   */
+  async tapLauncherWithWobble() {
+    const box = await this.launcherBox();
+    const x = box.x + box.width / 2;
+    const y = box.y + box.height / 2;
+    const wobble = Math.max(1, Math.floor(this.options.dragThresholdPx / 2) - 1);
+    await this.page.mouse.move(x, y);
+    await this.page.mouse.down();
+    await this.page.mouse.move(x + wobble, y + wobble);
+    await this.page.mouse.up();
+  }
   deployButton() {
     return this.page.getByRole("button", {
       name: this.options.deployButtonName
@@ -322,9 +385,7 @@ var RelayButtonDriver = class {
     return this.page.getByLabel(this.options.sshPublicKeyLabel).or(this.page.getByPlaceholder(this.options.sshPublicKeyPlaceholder)).first();
   }
   async prepare(options) {
-    const launcher = this.page.getByRole("button", {
-      name: this.options.launcherName
-    });
+    const launcher = this.launcher();
     await launcher.waitFor({ state: "visible", timeout: 6e4 });
     await launcher.click();
     await this.instanceNameField().fill(options.instanceName);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@le-space/playwright",
-  "version": "0.9.2",
+  "version": "0.9.4",
   "description": "Reusable Playwright fixtures and Relay Button lifecycle helpers.",
   "license": "MIT",
   "type": "module",
@@ -27,8 +27,8 @@
     "url": "https://github.com/NiKrause/relay-button/issues"
   },
   "dependencies": {
-    "@le-space/aleph-bootstrap": "0.9.2",
-    "@le-space/core": "0.9.2"
+    "@le-space/aleph-bootstrap": "0.9.4",
+    "@le-space/core": "0.9.4"
   },
   "peerDependencies": {
     "@playwright/test": ">=1.61.1 <1.62.0"