mirror of
https://github.com/kuhyx/testsAndMisc.git
synced 2026-11-10 18:07:06 +01:00
Krzysztof kuhy Rudnicki
094c4765f3
Location/curfew goes to daemon_location.sh, the derived state files to daemon_state.sh, the app layer to daemon_apps.sh. All 23 functions moved verbatim -- nothing restructured, which matters more here than anywhere else in this session. focus_daemon.sh has five `while IFS= read -r pkg; do ... done <file` loops and EVERY body calls pm. Piping any of them in lets pm inherit and drain the loop's stdin, so it would process one package instead of all of them -- measured elsewhere in this repo as 1 of 54. That audit ran BEFORE the extraction, not after coverage came back short, and all five moved untouched with a note above them saying why. CURRENT_MODE and _CURFEW_TICK_CACHED are each written in both the entry script and a library, so both stay declared with main, same call as NET_BUILT in the curfew split. 110 assertions and 33 mutations, all killed. Two survived the first run and both were defects in my own tests: the whitelist and sysprotect exactness checks used a SUPERSTRING of a listed entry, which fails under grep -qF and grep -qxF alike and so proved nothing about which was in use. Two subjects are NOT at 100%, and the numbers are reported as measured: daemon_state.sh 67/67 = 100.00% daemon_location.sh 26/40 = 65.00% daemon_apps.sh 71/76 = 93.42% Both shortfalls are kcov attribution failures, shown to be artifacts rather than gaps. daemon_location.sh's missing lines are all inside the embedded awk Haversine; mutating the Earth radius and dropping the longitude term both fail the suite, and an isolated probe shows a one-line awk measuring 100% where the identical multi-line one measures 0%. Collapsing the formula to satisfy the tool would cost the readability of the only real mathematics in the repo, so it stays. daemon_apps.sh's five are the trailing `done <file` of the very loops described above. That is the same artifact piping fixed in curfew_net.sh, and it is exactly what must NOT be done here. Redirecting two of them from /dev/null fails the suite, so the lines run; all three are pinned in the mutation spec instead. Over-cap count 19 -> 18. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011w2Pj4Ek3ZNMQVYcFHgXDY
144 lines
5.1 KiB
Bash
Executable File
144 lines
5.1 KiB
Bash
Executable File
#!/usr/bin/env bash
|
|
# lib/tests/daemon_cases_apps.sh — assertions for daemon_apps.sh: which
|
|
# packages survive the focus-mode sweep, and what happens on the way in and
|
|
# out of focus mode.
|
|
#
|
|
# Sourced by test_daemon_libs.sh after daemon_libs_harness.sh, which owns the
|
|
# stubs, the subjects and the PASS/FAIL counters this file adds to.
|
|
#
|
|
# is_allowed is the single decision that determines whether an app keeps
|
|
# working. Everything below is a way of getting it wrong: the wrong list at
|
|
# night, a prefix that matches too much, a guard that resurrects a browser
|
|
# during curfew, or a default handler that gets disabled and leaves the phone
|
|
# without a keyboard after a reboot.
|
|
set -euo pipefail
|
|
|
|
_seed_lists() {
|
|
printf 'com.allowed.day\ncom.both\n' >"${STATE_DIR}/whitelist.txt"
|
|
printf 'com.both\n' >"${STATE_DIR}/night_whitelist.txt"
|
|
printf 'com.android.\n' >"${STATE_DIR}/sysprotect.txt"
|
|
: >"${STATE_DIR}/default_handlers.txt"
|
|
: >"${STATE_DIR}/default_browser.txt"
|
|
}
|
|
|
|
# --- is_allowed, day --------------------------------------------------------
|
|
|
|
_reset_dev
|
|
_seed_lists
|
|
NIGHT_CURFEW_ENABLED=0
|
|
|
|
if is_allowed "com.allowed.day"; then
|
|
_t_pass "a day-whitelisted package is allowed outside curfew"
|
|
else
|
|
_t_fail "the day whitelist must apply outside curfew"
|
|
fi
|
|
|
|
if ! is_allowed "com.random.app"; then
|
|
_t_pass "an unlisted package is not allowed"
|
|
else
|
|
_t_fail "an unlisted package must not be allowed"
|
|
fi
|
|
|
|
# Exact match on the whitelist. The query has to be a SUBSTRING of a listed
|
|
# entry, not a superstring: grep -qF "com.allowed" would match the line
|
|
# "com.allowed.day" and let an unlisted package through, while
|
|
# "com.allowed.dayplanner" fails under both -qF and -qxF and so proves
|
|
# nothing about which is in use.
|
|
if ! is_allowed "com.allowed"; then
|
|
_t_pass "whitelist matching is exact, not by substring"
|
|
else
|
|
_t_fail "a substring of a whitelist entry must not be allowed"
|
|
fi
|
|
if ! is_allowed "com.allowed.dayplanner"; then
|
|
_t_pass "a superstring of a whitelist entry is not allowed"
|
|
else
|
|
_t_fail "a superstring of a whitelist entry must not be allowed"
|
|
fi
|
|
|
|
# The sysprotect list IS a prefix list, deliberately, so a whole namespace
|
|
# stays reachable.
|
|
if is_allowed "com.android.settings"; then
|
|
_t_pass "the sysprotect list matches by prefix"
|
|
else
|
|
_t_fail "sysprotect must match by prefix"
|
|
fi
|
|
|
|
# Anchored at the START, not matched anywhere: "org.evil.com.android.thing"
|
|
# contains the protected prefix but is not in that namespace, and an
|
|
# unanchored match would silently protect any package that mentions it.
|
|
if ! is_allowed "org.evil.com.android.thing"; then
|
|
_t_pass "a sysprotect prefix must match at the start, not anywhere"
|
|
else
|
|
_t_fail "a sysprotect prefix must be anchored at the start"
|
|
fi
|
|
if ! is_allowed "org.android.fake"; then
|
|
_t_pass "a package outside the protected namespace is not protected"
|
|
else
|
|
_t_fail "only the protected namespace may match sysprotect"
|
|
fi
|
|
|
|
# The default-handler guard is independent of the whitelist, so a config edit
|
|
# can never disable the dialer, SMS app, launcher or keyboard.
|
|
printf 'com.dialer.app\n' >"${STATE_DIR}/default_handlers.txt"
|
|
if is_allowed "com.dialer.app"; then
|
|
_t_pass "a default handler is allowed even when not whitelisted"
|
|
else
|
|
_t_fail "the default-handler guard must override the whitelist"
|
|
fi
|
|
|
|
# The browser guard applies only outside curfew.
|
|
printf 'com.browser.app\n' >"${STATE_DIR}/default_browser.txt"
|
|
if is_allowed "com.browser.app"; then
|
|
_t_pass "the default browser is allowed outside curfew"
|
|
else
|
|
_t_fail "the default browser must be allowed outside curfew"
|
|
fi
|
|
|
|
# --- is_allowed, night curfew ----------------------------------------------
|
|
|
|
_reset_dev
|
|
_seed_lists
|
|
printf 'com.browser.app\n' >"${STATE_DIR}/default_browser.txt"
|
|
NIGHT_CURFEW_ENABLED=1
|
|
_set_now "0000"
|
|
|
|
# The strict list replaces the permissive one — this is the whole point of the
|
|
# curfew, and getting it backwards would leave the night unrestricted.
|
|
if is_allowed "com.both"; then
|
|
_t_pass "a night-whitelisted package is allowed during curfew"
|
|
else
|
|
_t_fail "the night whitelist must apply during curfew"
|
|
fi
|
|
|
|
if ! is_allowed "com.allowed.day"; then
|
|
_t_pass "a day-only package is blocked during curfew"
|
|
else
|
|
_t_fail "the day list must NOT apply during curfew"
|
|
fi
|
|
|
|
# The browser guard must not resurrect a browser at night.
|
|
if ! is_allowed "com.browser.app"; then
|
|
_t_pass "the default browser is blocked during curfew"
|
|
else
|
|
_t_fail "the browser guard must not re-allow a browser during curfew"
|
|
fi
|
|
|
|
# The sysprotect and default-handler guards still apply on top of the strict
|
|
# list, or the curfew could disable the keyboard.
|
|
if is_allowed "com.android.settings"; then
|
|
_t_pass "sysprotect still applies during curfew"
|
|
else
|
|
_t_fail "sysprotect must apply during curfew too"
|
|
fi
|
|
|
|
printf 'com.ime.app\n' >"${STATE_DIR}/default_handlers.txt"
|
|
if is_allowed "com.ime.app"; then
|
|
_t_pass "the default-handler guard still applies during curfew"
|
|
else
|
|
_t_fail "the keyboard must stay reachable during curfew"
|
|
fi
|
|
|
|
NIGHT_CURFEW_ENABLED=0
|
|
_t_eq "0" "${NIGHT_CURFEW_ENABLED}" \
|
|
"the curfew is switched back off for the sweep cases"
|