Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[test]: cover `ancestry --json` rejections in the CLI tests

Open Beginner friendly
  • Is something wrong?
#23 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@khoap1220-hue is already working on this.

Since Oct 26, 2026.

  • #29 by @khoap1220-hue — closed without merging

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
rust
Domain
cli, testing

Research direction

Read CONTRIBUTING.md for the repository's checks, then inspect the existing ancestry tests in crates/externalize-cli/tests/cli.rs. Add JSON-mode rejection cases for the missing header file and the certified ledger, checking parsed verified and error fields and exit status 1. Done means both cases pass with cargo test -p externalize-cli and fail if rejection output is text.

Written by the indexing model from the issue text.

Description

area/cli complexity:trivial good first issue Stellar Wave test
Context

crates/externalize-cli/tests/cli.rs checks externalize ancestry when it succeeds (text and --json), and when a header file is missing (text). A script reading --json gets no test for the failure shape.

Scope

Add tests that run ancestry --json and parse stdout as JSON:

  • with only ledger-03dca33f.xdr.gz: verified is false, error mentions header missing, exit status 1;
  • with --ledger 64791359 (the certified ledger itself): error mentions not older, exit status 1.
Done when
  • Both tests pass with cargo test -p externalize-cli.
  • They fail if ancestry printed a rejection as text in --json mode.

Comment to be assigned before starting. Read CONTRIBUTING.md for the checks this repository runs.

Dominant language
Rust
Stars
1
Forks
1
Avg merge
3d 13h
Merged PRs (30d)
5

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Externalize-Labs/externalize

All issues in Externalize-Labs/externalize

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.