Repository navigation
test: fix JSON docs and startup fixtures - #93
Merged
Merged
Conversation
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.
The JSON guide now matches the binary, including lowercase IDs, duration strings,
tagged outcomes, and error envelopes on stderr. It covers scheduling, job and run
commands, doctor, version, and service commands.
Added key, value, and type tests. The process test checks a live command and monitor
instead of accepting an empty result. The version and error examples are checked
against real CLI output; the outcome examples cover every variant.
CI exposed two existing fixture races. Service tests now wait for a published
identity and initialized database. The retention test stops the old supervisor,
ages the whole timeline coherently, compares the default and configured windows,
and checks the exact purge error. Failure and timeout cases use scoped cleanup.
No JSON schema or runtime behavior changes. The production peer-bootstrap timing
limit found during diagnosis remains separate SQLite work.
Checks:
scripts/check.sh fullpassed with all 532 current-tree tests.The failed CI logs and earlier local startup timeout remain recorded. This adds a
corrective commit rather than rerunning the old failures without changing anything.