Repository navigation
Conversation
dmnre
force-pushed
the
tests-command-progress-logs
branch
from
September 18, 2026 07:50
7c38d0d to
8fa10df
Compare
fixique
reviewed
Sep 22, 2026
dmnre
force-pushed
the
tests-command-progress-logs
branch
2 times, most recently
from
September 25, 2026 14:31
bc48482 to
f4ed0fa
Compare
geko test commandgeko test now shows live test execution progress
dmnre
force-pushed
the
tests-command-progress-logs
branch
from
October 7, 2026 13:48
f4ed0fa to
c2636f9
Compare
fixique
reviewed
Oct 9, 2026
dmnre
force-pushed
the
tests-command-progress-logs
branch
from
October 14, 2026 10:00
a17cbb7 to
71683a6
Compare
fixique
approved these changes
Oct 16, 2026
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The
geko testcommand now reports real-time progress while tests are running, showing how many tests have been executed and how many have failed, plus a summary line when the run completes.Until now, running tests produced no feedback after the build finished, so it was impossible to tell whether a test run was progressing, how many tests had executed, or whether any had failed until the process ended.
Motivation and Context
Test runs could run for a long time with no feedback, which made it hard to tell whether things were progressing, how many tests had executed, and whether failures had already occurred. This change parses
xcodebuild's test output directly into structured lifecycle events and surfaces an aggregated, real-time progress summary so users get clear feedback on test execution without waiting for the run to finish.Types of changes
Checklist: