Test runner for the Friendly Technologies platform
Keyboard shortcuts
/
Focus the filter of the current section
Esc
Close the open dialog or run report
?
Show or hide this list
FT AI Test Agent
UI test automation via Claude + Playwright
env
/
now
Pass/Fail Trend
Recent runs
No runs yet.
Case
Title
Verdict
Duration
Env
When
known
The QA-verified state could not be read; QA marks may be missing
Test Cases
Case
CoverageLast runReadinessRef
Case
Title
Deleted by
When
Reason
Nothing deleted — the trash is empty.
Loading tests…
No test cases on this stand yet.
No tests match filter
—
converter changed
Find / replace
File
Before
After
Import test cases
The LLM mode applies to a TestRail export. A native export is imported as it is.
In No LLM, cached only mode, the import skips a case without a cached conversion.
A case never converted before has none.
Draft Cases
Agent-proposed QA cases generated from exploration reports. They never sync to TestRail
and are excluded from batches / pass-rate. Review, then Run to try one or
Supersede to discard. Stale drafts auto-purge after 60 days.
No drafts. Run an Explore and use "Generate drafts" on its report.
The QA-verified state could not be read; holds may be missing
Legacy case adaptation
The adapter store may live on another worker: select the "live" stand to see the written cases.
Status
Run adaptation
job slot held
Sections
Section
Total
Done
All sections
Cases
Status
No case matches the filter.
Title
Change
Held by QArunning
Pilot report
Engine
Cases
Ready 1st pass
Ready after repair
Automation blocked
Needs attention
Errors
Mean tokens in / out
Mean billed
Mean s
Project tokens in / out
Project billed
Hours
Source (TestRail)
Adapted (editable JSON)
A written case is re-adapted only by an administrator with Re-adapt from the original.
Hold
Project 15 (in place)
:
Nothing was written.
Formatting only: the words do not change.
Style cleanup: (pasted font style removed).
Format restored: (written as plain text, like the source).
The case body changes.
The title changes.
Now in TestRail
Adapted
No in-place writes recorded for this case.
Findings that say "Needs a human" are read from the TestRail source, not from the adapted text: re-gating an edit cannot clear them. Change the case in TestRail, or leave the row for a human to decide.
Number badge: Validation score 0-100, how closely the YAML matches the TestRail case. Green 85 and up, amber 60 to 84, red below 60.
Select a test case to edit, or click "+ New" to create one.
Created by
· Last edited by
Protocol:
USP device: Instance Limits, WiFi Client Limit and Delete Objects are ignored; the ACS target comes from the env profile.
MQTT device: Instance Limits, WiFi Client Limit and Delete Objects are ignored; the broker comes from the env profile (mqtt_broker_host). A blank host blocks the case.
Tree File:
Parameters:
:
none
Delete Objects:
none
Instance Limits:
none
WiFi Client Limit:
UI Preconditions:
device_serial & portal are filled in automatically from the test
Global ACS setting — auto-restored to its prior value in the postflight.
The user (and the domain, when it had to be created here) is deleted in the postflight — an account the stand already had is kept untouched.
Written as the run's domain user, so the copy belongs to that domain and the super domain is never touched. "file server" takes the stand's file server from Settings → Stand services; a stand without one ends the run as blocked, not failed. "email server" with smtp: test mailbox writes the stand's test mailbox account (Settings → Stand services) instead of the super domain's row, and the postflight empties that copy again.
A super domain with any method on is left untouched. With all four off the chosen one is switched on and read back; the postflight switches it off again and records the read-back. "Notify via this program" needs no recipient list, so it is the one that keeps the form valid.
The device is moved back to its previous domain in the postflight; a device already in that domain is left alone.
Two rows per device, filed under an existing parameter name. With own_device_only the rows are for the run's device alone (no domain move, no second device) and no monitoring_logs_verify step is needed; without it, pair the seed with a monitoring_logs_verify step, otherwise the case stays blocked.
Leave value empty and the seed writes the super domain's number + 1, so the two differ by construction.
Creates an Upload record (PUT Device/file) so the device's File Upload list is not empty — for cases whose precondition is "a record for the uploaded file is present". Idempotent: skipped when the list already has an entry. Delivering real file CONTENT additionally needs a reachable file server.
Forces the emulator tree state before the run: ABSENT deletes each path, PRESENT re-creates it. The two are mirror images on purpose — the emulator device is shared across a batch, so a test that needs a leaf gone and one that needs it present must each assert their own state (C9776/C9777 vs C9772/C9773).
Reads the registered device back through the portal (its commands, parameter names and stored values) and checks each capability. It never writes: a device that lacks one BLOCKS the run, naming the capability and the proof it looked for. The model template is no proof of a device capability, except for read: template: a Device Profile / Group Update / Automation line is proved over the model template, which those forms read.
Counts the devices of the protocol the portal lists. It never registers one: fewer than min BLOCKS the run with the count found.
Reads the case's own device back through the portal and creates nothing (the online check asks the ACS to push a Connection Request to the device, which opening the device card does too). A state the portal shows false (no such device, another protocol, still offline, no connected host) BLOCKS the run with the premise; a read that could not decide leaves the seed unconfirmed and a pass becomes inconclusive.
Generates one report (Device distribution, CSV) through the API and waits for its row in the exports list. The post-flight deletes the file this run made; exports of other users are never touched.
Uploads a Deployment file for the device's manufacturer/model (idempotent), so the Software Manager Install form has a "File name" to pick and "Send update" is enabled.
Activates a CWMP message trace for the device (PUT Device/tools/trace, idempotent) so later "Show trace" steps find captured session entries (Informs, connection requests, SPA tasks). Duration comes from the DeviceTraceDuration setting; no postflight STOP.
Turns ON "Generate credentials" for the login — global per-login, auto-restored OFF in the postflight (C91182).
text precondition
none
Phases:
Phases ():
:
Delete Objects:
none
Diag Params:
:
TestRail
TestRail changed after this case was converted — statuses are for the text as converted; reimport to refresh
Preconditions
As converted
As converted
As converted, matching no TestRail entry
phase_index:No phases defined — add one in Emulator Setup → Phases
INTERACTClaude drives this step from a snapshot. "Action" above is the prompt it reads.
EMULATOR ACTIONStraight to the emulator MCP, no UI. Tool name plus its arguments.
Arguments ():key = argument name (a TR-181 path for set_parameters_batch)
:
no arguments yet — add below
SPA TASK VERIFYWhich Device-Activity task the portal action must have emitted.
EXPLORERead-only survey of a screen. Produces a report, never a pass or a fail, and its case is excluded from batches.
ACS TASK
catalog_task:
Parameters ():
:
no params yet — add below
object_name:
object_names:
full_names:
parameters:
method:
diag_type:
file_type:
install_url:install_uuid:
DB QUERYread-only SELECT against the Platform DB — {serial} = run device serial, {domain_id} = id of the domain this run created
expect:=
:
LOG CHECKSSH-grep a log file for errors (warn-only). File = basename in the configured log dir.
expect:
DUPLICATE USERRefuse mode (C89833): create the level-1 user's name in this run's sub-domain and expect the portal to refuse it.Allow mode (C89832): seed a super-domain user, then create the same name in this run's level-1 domain and expect it to succeed.
mode:Both users are run-scoped, created by the step and deleted in post-flight — no fields to fill.
UNUSED MODELS SCOPEC89927: reads POST /Setting/unusedModels as this run's domain user and as the super domain, and passes only when both list the same models. No fields — both callers come from the run context. An empty list fails (nothing to display makes the check vacuous).
EXTERNAL SYSTEM SCOPEC89963: reads Settings > System Settings > External System as this run's domain user and as the super domain (POST /Setting/tabs + /Setting/tabs/items), and passes only when the domain is served the super domain's configuration. An empty tab fails — "configuration is present" cannot be true of a screen with no parameters.
USER GROUP PERMISSIONSC89879 / C89881: reads the user group this run seeded (CREATE_USER_GROUP) over REST and passes only when the named item carries both View and Execute. No seeded group, an item the portal does not offer, or either state off fails and says which.
GROUP UPDATE CONDITIONC92917 / C92918 / C92926-C92930 / C93176: the update this run saved on the form (its record name) and the condition its task carries, read over REST. satisfy waits for the first condition check, then sets the conditioned parameter on the device to the value that covers it and reads it back from the emulator; sent waits for the task's own row in Device activity; executed waits for the update to read COMPLETED and checks the six counters its details chart draws; withheld waits for the condition check and checks the task never reached the device; repeat waits for the next condition check and checks the update still reads RUNNING. No browser.
GROUP UPDATE TASKS SENTC10859 / C10860 / C11589 / C11590 / C89533 / C89534: «Corresponded tasks sent to relevant device(s)». Reads the update this run saved (its record name, or the update its own seed made) and the device(s) it targets over REST. Each targeted device is asked to connect; each must hold a row of the task in Device activity, created at or after the activation, in the Sent or Completed state, and the update must show no failed, offline, not-sent or skipped device. Polls up to the bound; still unsent at the bound with the device online is a FAIL, an offline or unreachable device, a Scheduled activation, zero devices or an unreadable status is INCONCLUSIVE. No browser.
PREPROVISION DEVICEC11600: «Associate any not registered device … with domain mentioned in step 2 using preprovision functionality» done the way the product does it — the device is removed from the ACS and added back by the run's user of the domain through the portal's Add device, which files the record in that user's domain before the device connects. The domain of the new record is read back from /Device/accountInfo. REST only, no browser; the next registration step is the device's first session with that record.
REGISTER DEVICE IN DOMAINC11598 / C11599 / C11600 / C11603 / C11642 / C11677: «Perform minimum required actions to register the device» done the way the product does it — the device is bound to the run's domain over the ACS and the domain is confirmed by /Device/accountInfo. REST only, no browser. A USP agent is bound by its USP Security row instead, and a stand that will not say which ISP mode it runs ends the step inconclusive rather than passing it.
NEW MANUFACTURER DEVICEC10446: «Register at least one device of manufacturer that hasn't been earlier at the system associating it with any domain except for domain mentioned in step 2». register adds a device of a run-tagged manufacturer through the portal's Add device call (checked absent from the stand's manufacturer list first), files it in the run's second top-level domain and reads the placement back from /Device/accountInfo. await is «Wait for about 5 minutes»: a poll, bounded by those five minutes, until the device, its domain and its manufacturer are all on the stand. REST only, no browser; the device and its model are removed after the run.
DEVICE PROFILE APPLIEDC11598 / C11599 / C11600 / C11603 / C11642 / C11677: which Device Profile the ACS applied after the registration, read off the Device-Activity «Profile:» rows and the profile inventory. Nothing on the stand names the applied profile directly, so a claim nobody could measure ends inconclusive — never a pass.
DROP THE HELPER DOMAIN USERC89762 / C89764 / C90265: removes the user CREATE_DOMAIN_USER provisioned for this run, on purpose — a user is domain content and would raise the associated-entities warning these cases say must NOT appear when the domain is deleted. The settings copy stays. No fields: the user comes from the run context.
E-MAIL DELIVERYC89816 / C89817: makes the platform send an e-mail to this run's domain user and reads it back from the stand's test mailbox (Settings > Test mailbox, IMAP, read-only). Passes only when a message carrying the run's marker arrived From the sender the domain's own Email server is configured with. No mail within the wait fails with what the platform answered and both servers; a mailbox that cannot be read is inconclusive, never a pass.
FILE ON THE FILE SERVERC12384 / C12386 / C12397 / C12398: fetches ai-file-<run>.bin from the run domain's folder on the stand's file server (Settings > Stand services), where the backend files a File Management add. REST only.
DEVICE FILE TRANSFERC89813 / C89814 / C89820 / C89821: dispatches an Upload for the device as this run's domain user and lets the BACKEND build the target URL (isManual false, no url of ours), then checks the stored URL sits in the device domain's folder, the file really is there, and the ACS task completed. REST only.
upload and restore are C89820 / C89821 steps 4 and 5; both is C89813 / C89814, whose text asks for «upload and download procedure». group_update is C10460's third clause: nothing is dispatched from here — the step reads back the Upload record the seeded CREATE_GROUP_UPDATE produced and checks its URL sits in the folder of the domain the update was created in.
EXPORT REPORTC10298 / C10299 / C10403: lists this run's domain user's own report files (POST /Report/files) and downloads the newest one (POST /Report/file). The Export click alone proves nothing — the browser cannot read a blob download, so the FILE decides. record = the report exists and carries a header plus a row; content = the run's device is in the file and no device outside the run's domain tree is (csv only, there is no xlsx parser in the image).
DOMAIN DEPTHC91188 / C91189: finds the node the preceding add_subdomain created and walks the domain tree up to Super domain, so «3rd-level subdomain is created and present in the domain list» is decided by the tree rather than by the Add form the step lands on. Super domain counts as level 1.
ACS IMPORT DOMAINC89932: reads the ACS user the preceding import_file created back over REST (POST /Setting/acsUsers) and compares its own Domain cell with the expected name. The screen shows the same cell, but the judge quoted neither it nor the list.
DOMAIN-SCOPED SETTINGC89789 / C90272: after the Save, reads the named Settings section (POST /Setting/snmpServer, /Setting/alerts, …) as this run's domain user and as the super domain, and passes only when the domain holds a copy of its own that differs from the super domain's row. No copy, or a copy equal to the row, fails — the change then reached the wrong scope or both. Mode picks which claim about that pair the step makes: own (C89762 / C90247, after a Create — the copy merely has to exist), inherited (C90249, after a Delete — there must be NO copy and both callers must read one row) and differs (C12398 — the copy exists and is NOT the super domain's; the verdict names one differing field on both sides). mailbox (C89805 / C89806, Email server) — the copy is the stand's test mailbox account from Settings → Stand services (host, port, SSL, login, password, sender) and differs from the super domain's row; a stand without a mailbox is inconclusive. A changed read is also held against the super domain's row as the pre-flight found it.
EVENT URLSC90399: reads Settings > Alerts and events > Events > Edit URLs over REST (POST /Setting/events/hardcoded/urls) as the named domain user — the same two lists the dialog renders (own rows, else the inherited ones) — and checks whether the URL the CREATE_EVENT_URL preflight filed in the run's first domain is there. Present for a user of its sub-domain, absent for a user of an unrelated domain.
DEVICE DOMAIN MOVEC91352/C91353: reregisters the case's device with the other domain of this run — as the logged-in domain user through PUT /Device/accountInfo at ispMode=1, through the run's TR-069 login at ispMode=2 — waits until the placement holds, then reads the inventory as both domain users. Passes only when the user the device left no longer finds it and the user of the target domain does. Needs CREATE_DOMAIN {sibling} and a named CREATE_DOMAIN_USER on each side.
IMPORTED SERIALSC10989: after «List of serials > Save», reads the update the run's form step named (ai-mon-<run>) over REST (POST /GroupUpdate/groups/details) as the admin. Passes only when every manufacturer/model row is the domain device's model, every "Send to" reads Individual, the domain's device is associated and no associated device sits outside the run's domain. The import step lists every same-model serial on the stand, so a device outside the domain is what the filter must drop. No fields — everything is derived from the run.
EXTERNAL SYSTEM READ-ONLYC89766/C89767: reads the named External System sub-tab as this run's domain user and as the super domain (POST /Setting/tabs + /Setting/tabs/items), and passes only when the domain is served the super domain's values AND every parameter below is writable for the super domain but NOT for the domain user — the same writable flag the portal greys the control on. A parameter neither caller has is a fail.
CRED VERIFYLength mode (C91182): set credentialMinLength/MaxLength via REST, BootStrap, then check the generated {OUI}-{RANDOM}-{SERIAL} length. Leave min_len/max_len empty for a set-only "saved" step.Individual-behaviour mode (C91176): verify per-device credential generation / 0-BOOTSTRAP persistence / toggle-off, on the device authenticating under the login below.
mode:login:password:
set credentialMinLength:set credentialMaxLength:
expected RANDOM length min_len:max_len:
oui (optional, else read from device):poll_seconds:
AI CHATDevice AI Assistant: ask a question, wait for the streamed answer, judge it. Add a following acs_task/db_query step to verify a confirmed command.
question:expect_semantic (LLM judge):
expect_contains:expect_absent:
AI STEP (evidence-gated)AI executes the goal; PASS only when every claim below is independently re-validated. quote must be an exact substring of expected.
Change history
Execution history
Verdict
When
Took
Env
Owner
This case has never been run here.
Attachments
No files attached to this case.
Promote ai_step → typed steps
Original (ai_step)
Proposed (deterministic)
Generate Tree
Generating device parameter tree via bbf-tree-mcp based on test preconditions.
Regenerate Emulator Setup
Regenerating emulator_setup from test preconditions and steps using converter logic.
Emulator setup regenerated successfully
tree_file:
parameters:
delete_objects:
wifi_client_limit:
Reimport
from TestRail:
case(s) · LLM mode · model
This overwrites their YAML with a fresh conversion — any manual edits will be lost.
In "cached only" mode a case without a cached conversion is skipped instead — its YAML stays as is.
You can close this dialog: the re-import goes on on the server.
Nothing to reimport.
Pre-check of the selection
Checking case(s)...
Case
Decision
First reason
partial
Batch Report
Export
Broken steps
Step
Reason
Cases
Total time:
· started · env · · by · cut from · retried after a browser crash
Compared with the batch of ,
Failure breakdown
#
Test ID
Title
Portal
Status
Audited
Reason
Notes & defects
Time
No rows match the current cut. Clear a chip above.
REGRESSIONknownretried
—
—
Commentsloading…nothing said yet
Edit run
Queued
Nothing is left in the queue: every case has started.
Add cases
Reading the record…
This worker sends no readiness data (an older image).
Code
Source
Line
Text
Evidence
No gap.
Flags
Refused because of an env (not a gap)
Runs that did not count
The QA-verified state could not be read; QA marks may be missing
Readiness
Reading the summary…
This worker image has no readiness data yet. The labels appear after the worker update.
Tags (cut across the labels, not added to them)
spread:
Portal
Total
Gap codes
Gap
Source
Cases
Only gap
Sample
No gap on this stand.
Manual only and Postponed
Case
Title
Mark
Reason
Note
By
When
No case is marked.
Navigation fixes the agent wants to remember
Each row = a navigation self-heal that repeated during runs: the converted test asked for
one control, the real UI needed another. Accept stores the fix permanently
(portal-scoped, applied at script generation — the test YAML is untouched).
Dismiss hides the proposal forever.
Learning endpoints are disabled on the server (FT_LLM_DIAGNOSE is off).
Portal
Converted step → what actually worked
Seen
Cases
No pending navigation proposals — every learned fix is either promoted, dismissed,
or no heals have repeated yet.
→ conflictingnot promotable
Recurring failures the agent wants to register as known issues
Each row = the same test failed repeatedly with the same diagnosed durable cause
(backend / TestRail / converter bug). Accept adds it to the known-issues registry
so future diagnoses classify it instantly. Dismiss hides this signature.
Case
Bucket
Signature / note
Seen
No recurring-failure candidates right now.
Heal journal (raw)
Every runtime navigation heal, grouped. Read-only — proposals above are derived from this.
Case
Step
Target → healed action
Count
Journal is empty — no navigation heals recorded yet.
→
Environment Defaults
Central environment profiles (an env = a named settings blob).
Pick a profile per run via the Env dropdown in the Tests tab; the
worker is materialized with that env's settings for the run. Select a profile below,
edit the fields, then press Save to store it back centrally on the
gateway.
Used by FtApiClient for monitoring / device-tree calls.
The wave's Make sure that environment is set to work with "ISP"="1"
precondition reaches the env as two knobs: the interface setting
IspEnable and the ACS setting ispMode —
Multi-Domain = 1, Multi-ISP = 2.
Set writes them before the test and restores them after, which is what a
shared stand needs. Verify only writes nothing and instead checks the env
already carries the mode the test asks for; a test written for the other mode is
reported blocked and never started, so running one half of the wave
on its own env does not turn the other half red.
Pick the group to run with GET /api/tests?isp=1 / ?isp=2
(?isp=none = the cases that work under either).
This is a property of the STAND — set it in the env profile, not per run.
TR-069 emulator HTTP API base. Passed to mcp-tr-emul as emulatorUrl on every call
and queried directly for parameters, so an edit here is live from the next run: no sidecar restart.
ACS endpoint the emulated device reports to (Device.ManagementServer.URL).
Must point at the same environment as Backend / Emulator URLs.
IoT emulator (USP / LwM2M / MQTT agents) REST base. Passed to the worker's mcp-iot-emul
sidecar on every call, so an edit here is live from the next run: no restart, no wrapper.
Leave blank when this stand has no IoT emulator: USP cases then end as blocked, not failed.
Where the emulated USP agent connects: the ACS USP MTP listener (k8s env: the in-cluster service name, e.g. ftacs:61617 STOMP;
compose stand: the public host). Controller Endpoint ID is the ACS's own EID (self:ft:1 on FT stands).
Where the emulated MQTT device connects: the ACS MQTT broker (plain port 1883; k8s env: the in-cluster service name).
Leave the host blank when this stand has no MQTT device wired: MQTT cases then end as blocked, not failed.
Username and password are needed only when the broker's MQTT Security row asks for BASIC.
ft-configs-service — the stand's single writer for application settings
(IspEnable from settings.xml, ispMode from
acs_configuration.xml and so on). Preconditions write values here; empty =
the stand has no such service, so the legacy management/ACS REST path is used.
Read-only state access (preflight / verify). Test connection runs SELECT 1 against the saved config — Save settings before testing changes.
After each test, SSH to this server and grep log files (named in "absent from 'server.log'"-style assertions or log_check steps) for errors appended during the run. Warn-only — attaches to the report, never fails a test. Save settings before testing.
Device-creation tests (FTCreateDevice / addCPE) call PUT /api/Device as a pre-flight to create a pre-provisioned device — with map coordinates (C9616) or without (C9617). Test connection is a read-only reachability check; auth is validated on the actual create. Save settings before testing.
Written into the File-server settings of the domains a run creates, as that domain's own
user — never into the super domain. Save on the File server screen dials these addresses, File
Management uploads to them, device Upload / Download tasks point at them. Leave both addresses
blank when this stand has no file server: the cases that need one then end as blocked,
not failed. Addresses carry the scheme (ftp://, http://,
https://) and end with /; uploads need a WebDAV-enabled HTTP server.
The SMTP side is written into the Email server settings of the domains a run creates, as
that domain's own user — never into the super domain. The IMAP side is where
mail_delivery_verify looks for the mail the platform sent (C89816 / C89817); it
only reads — nothing is marked, moved or deleted. Leave the login blank when this stand has
no mailbox: the cases that need one then end as blocked, not failed.
0 = off (default) — the run goes at full speed. Set a value when you
watch a run with your own eyes (a demo, or following a failure over noVNC):
without it the steps replace each other faster than a person can read the
screen. The wait sits between steps and outside their error handling,
so it changes only the pace — never a verdict. It applies to every
step — browser, agentic and deterministic alike. Fractions are fine
(0.5); capped at 60 s. Note it also stretches the whole run:
1 s across a 40-step case adds about 40 seconds.
For QA stands where domains and users are created by hand: runs trip over
those leftovers, and the postflight only removes what the run itself created.
The order is dictated by the backend — portal users → ACS users → devices →
automations → domain: while the domain still holds any of those dependencies,
deletion is refused (DOMAIN_CANNOT_BE_DELETED…).
Devices under foreign domains ARE DELETED; super-domain devices
(our test-runner-*) are never touched.
On a shared stand, enable this only together with the skip list below.
Domain names the sweep never touches (case and spaces are ignored). Empty =
EVERY domain except the super domain is removed, including one somebody is
working in right now.
TestRail
Adaptation (legacy cases)
Saving writes the env profile and changes no worker: the values reach the workers when a run of that env is dispatched (the pooled workers share one settings file), and a run of another env replaces them; the Adaptation tab shows what the worker uses.
Validation scan (TestRail)Scores every case of a TestRail project against the converter
User Management
Create User
Username
Role
Created by
Status
Actions
No users found.
disabledactive
Worker Management
Add Worker
Name
Env (pinned)
Display
Base URL
noVNC URL
Status
Busy
Actions
No workers configured.
Show address
Direct address of the worker browser. It skips the gateway ticket check. To watch a run, use Live browser on the Runner tab.
—
disabledenabled
idle
Activity Log
Time
Username
Action
Target
Detail
Source
Status
No activity entries.
Test Procedures
"How to test X on portal Y" documents written by the librarian as drafts.
Only approved procedures are served to test execution. Review a draft,
then Approve (publish) or Reject (roll back to the last approved version).
Editing is not done here — corrections come via a new librarian draft or the REST API.
Name
Portal
Status
Version
Updated
No procedures.
/ 100
🔍
LLM
No issues
Loading…
Import from TestRail
● Connected● Disconnected
In No LLM, cached only mode, the import skips a case without a cached conversion.
A case never converted before has none.
Import TestRail run
Every case of the run is imported and tagged with a project label
(default: Run <id> — <run name>).
