smix-sdk 2.0.0

smix-sdk — user-facing public surface for the smix Rust library. App + ergonomic selector helpers + matchers. Wraps SimctlDriver + SimctlClient + HttpRunnerClient.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88

//! What the device actually printed, kept so the parse stays checkable.
//!
//! Every Android launch used to run `am start -n <pkg>/.MainActivity`.
//! On an API 33 emulator that is:
//!
//! ```text
//! Error type 3
//! Error: Activity class {com.android.settings/com.android.settings.MainActivity} does not exist.
//! ```
//!
//! Settings' launcher activity is `.Settings`, and the package manager
//! says so. The fixtures beside this file are `cmd package
//! resolve-activity --brief -c android.intent.category.LAUNCHER`'s
//! output verbatim — one hit, one miss — captured 2026-07-22 from
//! `sim-smix-android-01` (API 33, Android 13).
//!
//! Committing them turns a device observation into something the
//! workspace suite re-checks on every run, which is the point: the
//! failure mode this guards is a shell output format changing shape
//! and the parse quietly falling back to the convention that does not
//! work.

use smix_sdk::parse_resolved_activity;

const HIT: &str = include_str!("fixtures/resolve-activity-settings-2026-07-22.txt");
const MISS: &str = include_str!("fixtures/resolve-activity-absent-2026-07-22.txt");

#[test]
fn the_component_line_yields_a_relative_activity() {
    assert_eq!(
        parse_resolved_activity(HIT, "com.android.settings").as_deref(),
        Some(".Settings"),
        "the captured output is:\n{HIT}"
    );
}

/// The fixture is still the two-line shape a device produced.
///
/// A check on the fixture, not on the parse: reduced to its component
/// line it would still parse, and would no longer stand for what a
/// device prints. That is the way this file could quietly stop meaning
/// anything.
#[test]
fn the_captured_output_still_has_its_header() {
    assert!(
        HIT.lines().count() >= 2,
        "the fixture lost its header line and no longer stands for real output"
    );
    assert!(
        HIT.lines().next().unwrap().starts_with("priority="),
        "the fixture's first line is no longer the header a device printed"
    );
}

/// A package with no launcher activity — and, identically, one that is
/// not installed.
#[test]
fn no_activity_found_yields_nothing() {
    assert_eq!(parse_resolved_activity(MISS, "com.example.nosuchapp"), None);
}

/// A fully-qualified component collapses to the relative form.
///
/// `AdbClient::start_activity` prefixes the package itself, so
/// returning the absolute name would send `<pkg>/<pkg>.Settings`.
#[test]
fn a_fully_qualified_component_is_relativised() {
    assert_eq!(
        parse_resolved_activity(
            "com.example.app/com.example.app.SplashActivity",
            "com.example.app"
        )
        .as_deref(),
        Some(".SplashActivity")
    );
}

/// Output this does not recognise leaves the caller where it was.
#[test]
fn an_unrecognised_shape_yields_nothing() {
    for text in ["", "Exception: something went wrong", "com.other.app/.Main"] {
        assert_eq!(
            parse_resolved_activity(text, "com.android.settings"),
            None,
            "{text:?} was read as an activity"
        );
    }
}