A testing control plane that runs the suite and keeps the evidence.
- task queue
- local executor
- Allure reports
MeteorTest · MVP, active development
Mobile engineering with release quality built in.
I build iOS and cross-platform apps, the API contracts they depend on, and the automated checks that keep each release dependable.
Engineering portfolio of Pengyu Qi (Connor).
A testing control plane that runs the suite and keeps the evidence.
One product, three repositories, one interface contract.
A 2.5D learning game with backend-authoritative progress.
Captured from the running builds, not mockups.




Counted from the public GitHub repositories on 31 October 2026. Private repositories are not included.
Scroll to move through the build.
Recording, playback, local storage and offline practice flows, with mock services marked explicitly in Debug builds so nothing pretends to be real data.
EC-API-0.1 is versioned and hash-distributed to both clients, so the iOS app, the uni-app x app and the FastAPI backend move together instead of drifting apart.
Appium and pytest suites produce real pass/fail results and Allure artifacts before a build leaves the machine, and the same run is recorded on this page.
One interface contract, versioned and hash-distributed, keeps the iOS client, the cross-platform client and the backend in step.
Automation testing platform for projects, suites, local executors, reports, and AI-assisted operations.
A testing control plane that connects project contracts, AI-assisted operations, local execution, and report context.

MeteorTest is built around one practical loop: let a platform or AI assistant import test projects, register suites, create tasks, trigger local execution, and bring logs, reports, and failure context back into one place.
A MeteorTest Local Agent task executed iOS-Automation-Framework `api_smoke` against the deterministic local mock API and collected task-specific logs plus Allure result artifacts.
The public website still uses a browser-side mock demo, and the live Web preview keeps execution private. Public connected execution is a later design topic after authentication, data isolation, and executor safety are designed.
The first practical test-code carrier and platform integration sample for MeteorTest.
GitHubEach entry links to public code and states how far it has been validated. Several repositories behind these systems are still private.
An English speaking practice app built as three cooperating repositories: a SwiftUI iOS client, a uni-app x cross-platform client, and a FastAPI + LangGraph backend.
View detailsBuild control planes that connect projects, suites, tasks, local executors, logs, reports, and follow-up actions.
Keep UI automation and API smoke tests maintainable through clear fixtures, runtime isolation, and platform integration contracts.
Use AI as an operation partner that can import projects, prepare tasks, inspect results, guide voice practice, and suggest concrete next actions.
Build spoken interaction loops where ASR, endpointing, TTS, session state, and feedback controls stay observable across web and mobile.
Prefer small, observable execution loops that can run locally first, then become website validation results or platform workflows later.
JC Meteor is currently organized around public engineering work. GitHub is the best place to understand the projects, follow progress, and discuss project-specific questions.
For private details such as credentials, internal URLs, device identifiers, or test accounts, use a private channel when one is published.