Full tgz-only E2E harness (scripts/e2e-full)#495
Draft
latekvo wants to merge 2 commits into
Draft
Conversation
Starts from only a swmansion-argent-*.tgz and exercises the install flow, every CLI command, all 70 tools' argument validation, and a happy-path run of every tool against real Android/Chromium targets plus the RN debugger/profiler chain against Bluesky. Runs under a sandbox HOME + npm prefix; emits a JSONL log and a markdown coverage report; exits non-zero on any failure.
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
1 participant
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.
What this is
A release-gating end-to-end harness under
scripts/e2e-full/that starts from only aswmansion-argent-*.tgzbundle and exercises the whole product: the install flow, every CLI command, all 70 tools' argument validation, and a happy-path run of every tool against real devices. Intended to be run on the real Linux box and the real Mac before a release.Everything runs under a throwaway
HOME+ npm prefix, so it never touches the machine's real~/.argent, editor MCP configs, or global packages (safe on a shared box). It emits a JSONL log + a markdown coverage report and exits non-zero if any hard assertion fails.Phases
installnpm i -g <tgz>, bundled binaries,init(global +--local),update,uninstall, telemetry, MCP-config generationintrospection--version/--help,tools describefor all 70 tools, feature flags,server start/status/logs/stop,link/unlinkvalidationandroidchromiumrn~/dev/bluesky+ Android deviceTiers auto-skip with a recorded reason when prerequisites are missing. iOS / tvOS / Vega are intentionally out of scope for now.
What I actually verified (real runs, Linux)
tools describe), validation 81✓/0✗, chromium 24✓/0✗ (real Electron app + CDP).bash -nclean on all files, all 72 android/rn JSON arg literals linted.What I did NOT verify live (please scrutinize)
androidandrntiers were never run against a live device. The Android emulator would not stay up on my box (memory-constrained shared machine; QEMU threads hung seconds after boot across ~7 attempts). The code is complete and uses the same machinery thechromiumtier exercised live, but it has not been proven end-to-end. This is the main reason for the "not certain how well it works" caveat.tools describe, not confirmed against a running Metro.Run it