Skip to content

test(remote): cover the unknown-group fall-through and relocate group store tests #103

Description

@Ariestar

Two cleanup items surfaced during the origin/group refactor (PRs #101/#102); both are post-merge polish, nothing blocks the stack.

1. GroupQuery(None) has no direct test

The daemon answers None when a group query targets an unknown group, letting the CLI continue its scope cascade (mount → group → local origin) instead of erroring. The branch itself is a let-else with compile-time type safety, but it is the one new behavior with no unit coverage — a store-level smoke test asserting the handler path would pin it.

2. Group store tests live in state/mod.rs, code in state/group.rs

After the state split, src/remote/state/group.rs holds the group store logic but its ~400 lines of tests still sit in state/mod.rs's test module, interleaved with two share tests. Working today, but relocating the group tests next to their code would make the split self-contained.

Stack context: #70#98#100#101#102.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions