Smoke test results,

Development documentation. This guide follows a reviewed snapshot of main and may describe capabilities not yet in Stable. Check Preview labels and release notes. Some executable names and paths remain unchanged for compatibility. Legacy names explained ↗

This file is committed to a public repository: no workspace, tenant, user or item names or ids go in it, and no tokens.

App version: <Settings › About>
Run by: <role, not a name>
Workspace: a test workspace marked fabric-desktop-live-test, on capacity
Command: fabric-desktop smoke-test --workspace <id> [--run-in-fabric] [--platform [--platform-upgrade]]
Smoke run id: · Live test run id:

#	Flow	Automated	By hand
1	Install and start the engine
2	Sign in, no app registration
3	Workspaces and the catalog
4	Create a lakehouse; refuse an invalid name
5	Notebook on the PC writes to OneLake
6	Publish and Run in Fabric; Monitor
7	Prove the notebook	n/a
8	Metadata project: Dev on the PC, promote to Test	n/a
9	The live test
10	Report a problem and the support bundle
11	Platform: Finish or repair once from empty
12	Platform: again, or from the Stable build (`--platform-upgrade`)
13	Platform: register a data product
14	Platform: surrogate keys		n/a
15	Platform: policy exception
16	Platform: restrict a central lakehouse family

Flows 11 to 16 only run with --platform; leave them out otherwise. Record whether the UDF connection was added by hand, and anything the platform ledger left behind.

Result is Passed only when the automated part passed and every by-hand box is ticked.

Recorded, not counted#

Azure SQL token (warehouse queries): <passed or the error, with no token>
Kusto token (warehouse Monitoring): <passed or the error, with no token>

Notes#

Inventory changes#

Need a hand?

Find a fix in troubleshooting, or share a reproducible issue with the community.

Get support ↗Improve this guide on GitHub ↗