Skip to main content

Sessions & project layout

A mobile test is a single .trq file — the same bundle format as web. A project is just a folder of .trq files; open the folder in Trq and every session shows up in the explorer. Web and mobile sessions can live in the same project, side by side, and you organize them into sub-folders as suites.

Inside the bundle, a mobile session stores its steps, its per-session settings, its metadata, and any content it needs to replay — an uploaded file, a captured mock — all content-addressed so the test is self-contained and shareable.

Because everything lives in the one file, a mobile test is easy to version-control, diff, and hand to a teammate — it carries its own data with it.

Finding a session​

Press ⌘⇧F (Ctrl⇧F) to search every session in the project by name — fuzzy, instant, and with the number of other sessions that call each result, so you know before opening it whether it is a leaf test or something a dozen journeys depend on.

The index covers web, mobile and API sessions together: a mobile flow called from a web journey is counted the same as any other caller. See the web guide for the full details.

Deleting a session other sessions call​

A mobile session can be called as a flow from another session, the same as web — and a ▶ call step stores its target as a path. Delete that session and every caller still points at it, looking fine until a run reaches the step.

So deleting a session that something calls shows what it costs first: how many call steps break, which sessions they sit in, and an option — on by default — to remove the orphaned call steps in the same action, so those tests keep running. Untick it if you mean to repoint them at a replacement instead.

A call step whose target is gone is marked flow not found in the Events panel; right-click it to point it at another session or remove it. Renaming or moving a session repoints its callers automatically, with the call's alias left untouched.

The scan covers web and mobile sessions together — a mobile flow called from a web journey, or the reverse, is counted the same. See the web guide for the full details.