@specific.dev/spectest 0.41.0 → 0.44.0

package/src/mobile.ts

@@ -99,14 +99,18 @@ export async function openMobile(opts: {
 }
 
 /**
- * Acquire the persistent phone-emulated session for an app (one per app URL,
- * created on first use). The daemon calls this from `ctx.mobile(app)` with a
- * per-test rrweb recorder; the resulting record carries `frame: "mobile"` so
- * the dashboard renders a phone bezel. `detach` is the test-end hook;
- * `mobile.close()` destroys the session for real.
+ * Acquire the persistent phone-emulated session for an app (one per app URL
+ * per `name`, created on first use). The daemon calls this from
+ * `ctx.mobile(app, name?)` with a per-test rrweb recorder; the resulting
+ * record carries `frame: "mobile"` so the dashboard renders a phone bezel.
+ * `detach` is the test-end hook; `mobile.close()` destroys the session for
+ * real.
  */
 export async function openPersistentMobile(opts: {
   url: string;
+  /** Session name — `""` (the default) is the unnamed session every
+   *  `ctx.mobile(app)` call shares. Two names on one app are two phones. */
+  name?: string;
   recorder: BrowserSessionRecorder | null;
   /** Installed before the fresh session's first navigation (ignored on an
    *  attached session, which already carries it on the forked holder). */
@@ -121,6 +125,7 @@ export async function openPersistentMobile(opts: {
 }> {
   const { browser, attached, detach } = await acquirePersistentMobileBackend(
     opts.url,
+    opts.name ?? "",
     opts.recorder,
     opts.initScript,
   );

package/src/recorder.ts

@@ -429,6 +429,16 @@ export interface BrowserEvent extends BaseEvent {
    * with a `BrowserSessionRecorder` attached (the daemon always does).
    */
   sessionId?: string;
+  /**
+   * Author-given name of that session — `ctx.browser("alice")` — absent
+   * for the default unnamed browser, so a single-browser test's steps
+   * carry no name and render exactly as they always have. Present, it is
+   * what the step list badges to say which browser acted. Duplicated here
+   * rather than resolved from the session record because the CLI's
+   * failure detail renders from persisted events alone, with no replay
+   * bundle to look the session up in.
+   */
+  sessionName?: string;
   /**
    * Wall-clock `Date.now()` captured at the moment this op *finished*.
    * Lives in the same time base as rrweb's `event.timestamp` fields,