A testing control plane that connects project contracts, AI-assisted operations, local execution, and report context.

- ImportProject contract and suites
- PrepareTask, environment, build
- ExecutePrivate Local Agent
- AnalyzeReport context and next action
Project hub
Build testing systems that can be repeated, observed, and improved.
A project-led engineering portfolio centered on repeatable testing systems, voice interaction products, local execution loops, and practical agent workflows.
This is a simplified AI-assisted operation model, not a screenshot of the current MeteorTest web console.
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.
GitHubBuild 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.