There is no way to ask a Tauri app "did you start correctly" from a script. CI can launch the binary and check it stays alive, which proves almost nothing: our app stayed alive for minutes while showing a splash screen and a frozen spinner because a module 404'd.
What would help?
A mode that creates the window, loads the URL, waits for the document to reach readyState === 'complete' (or a timeout), prints a machine readable result, and exits. Non-zero when the page did not load.
$ my-app --smoke --timeout 30
{"window":"created","document":"complete","console_errors":0}
$ echo $?
0
That one feature would let CI verify a desktop app boots. Today the options are manually reviewing a screenshot, or a log line the app author remembered to add.
Related
A readiness event on the Rust side would cover most of it even without a CLI flag: something an app can await and log itself, emitted when the webview's document finishes loading rather than when the window is created.
There is no way to ask a Tauri app "did you start correctly" from a script. CI can launch the binary and check it stays alive, which proves almost nothing: our app stayed alive for minutes while showing a splash screen and a frozen spinner because a module 404'd.
What would help?
A mode that creates the window, loads the URL, waits for the document to reach
readyState === 'complete'(or a timeout), prints a machine readable result, and exits. Non-zero when the page did not load.That one feature would let CI verify a desktop app boots. Today the options are manually reviewing a screenshot, or a log line the app author remembered to add.
Related
A readiness event on the Rust side would cover most of it even without a CLI flag: something an app can await and log itself, emitted when the webview's document finishes loading rather than when the window is created.