umputun / agterm / 32060495421
97%

DEFAULT BRANCH: master
Ran
Jobs 1
Files 93
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst
coverage: 97.972%. Remained the same
32060495421

push

github

umputun 
perf(tests): take automatic screenshots instead of a video per UI test

XCTest starts a diagnostic screen recording as each test method begins, before
setUp, and blocks on it. A stack sample of agtermUITests-Runner during that silent
window showed 6786 of 6789 samples parked in mach_msg under
startingTestWithActivity: and attachDiagnosticScreenRecordingForDevice:, so the
runner was asleep on IPC rather than doing work.

It cost 18-25s per method and grew over time on this host: a class-by-class run of
322 executions spent 101 of 152.8 minutes there, before any test code ran. agterm
was never involved; launch to accessibility is 0.354s and accessibility to
automation 0.452s.

Xcode 26 exposes no way to disable capture, so this switches the format. Four runs
against the same products confirm it, two through a patched xctestrun and two
through the regenerated scheme: the pre-setUp gap falls from 25.20s to 0.05-0.32s.
ControlAPIUITests goes from 28.6 to 7.4 minutes for its 82 methods,
EditMenuUITests from 105 to 31 seconds.

The docs had drifted with it. ui-tests.md counted 77 of something the tree never
had; it is 44 classes and 429 methods, and a per-class second count stopped meaning
anything once the fixed cost went away. CLAUDE.md's "about 7 minutes" for
ControlAPIUITests was accurate and had been silently invalidated by the recording
default; it now measures 7.4 again.

The cost is that a failing UI test keeps automatic screenshots but loses the video.

8018 of 8184 relevant lines covered (97.97%)

4985959.34 hits per line

Jobs
ID Job ID Ran Files Coverage
1 32060495421.1 93
97.97
 GitHub Action Run
Source Files on build 32060495421