AndreMiras / kivy-ios / 38442378640

1%

master: 1%

push

github

:white_check_mark: Add Release simulator startup smoke

CI builds the generated Xcode project but never launches it, so a
change that breaks app startup can still go green: Python not finding
its bundled stdlib, native launch arguments getting eaten, or Kivy
failing to open a window.

Add a small test app and a runner that catch this on a real simulator:

- tests/test_startup/main.py is a tiny Kivy app that checks itself at
  startup (argv, json/zlib/sqlite3/ssl, SDL2 window) and writes its
  progress to a JSON file in its data container. It only reports
  success from a Clock callback, i.e. once the Kivy event loop runs.
- .ci/test_simulator_startup.py generates that app with
  `toolchain create`, builds it in Release for the simulator, installs
  it on an available iPhone and launches it twice: once plain, once
  with -NSDocumentRevisionsDebugMode YES like Xcode does when running
  from the IDE. Each launch gets a fresh ID so a result left over from
  an earlier launch can't count as a pass.
- The result goes through a JSON file rather than console output
  because Release builds can suppress Kivy logs.

The smoke runs as one extra step in build_python3_kivy on
macos-latest, capped at 20 minutes. Diagnostics (build log, simulator
inventory, per-launch logs and results) are uploaded as an artifact,
on failure too. It uses the simulators already on the runner image
and doesn't download runtimes.

The runner logic (simulator selection, result handling, timeouts) has
unit tests that run on the Ubuntu job. See tests/test_startup/README.md
for running it locally and debugging failures.

8 of 468 branches covered (1.71%)

Branch coverage included in aggregate %.

35 of 2408 relevant lines covered (1.45%)

0.01 hits per line