#!/usr/bin/env bash
#
# Prepares the device for the macrobenchmark module, and takes it back afterwards.
#
#   ./tools/benchmark-fixture.sh            # create the folder, grant storage access
#   ./tools/benchmark-fixture.sh --remove   # delete the folder again
#
# Why this is a script rather than setup inside the benchmark: UiAutomation's executeShellCommand
# runs with the *test app's* uid, not the shell's, so it cannot write to /sdcard and cannot grant
# itself an app-op. The first version of the benchmark tried exactly that and failed with a
# RuntimeException from UiAutomationConnection, leaving no fixture and a hang. Through adb the same
# commands run as the shell user, which has the rights this needs.
#
# The folder is at the root of shared storage under a name that sorts before everything else, so the
# benchmark finds its row without scrolling.
set -euo pipefail

package=de.softwareapp_hb.filemanager
directory=/sdcard/AABenchmark
count=1000

case "${1:-create}" in
    --remove)
        adb shell "rm -rf $directory"
        echo "benchmark-fixture: removed $directory"
        ;;
    create)
        # One shell loop with builtin redirection: no fork per file, so a thousand files take a moment
        # rather than a minute.
        adb shell "rm -rf $directory; mkdir -p $directory; \
            i=0; while [ \$i -lt $count ]; do : > $directory/file-\$i.txt; i=\$((i+1)); done"
        # The benchmark build is not the debug build, so it starts with no storage grant; granting it
        # here is what lets the run be unattended. No `--uid`: that flag takes a uid, not a package
        # name, and passing a package there grants nothing while still reporting that something was
        # set — which is exactly the kind of half-truth that costs an afternoon.
        adb shell "appops set $package MANAGE_EXTERNAL_STORAGE allow"
        echo "benchmark-fixture: $count files in $directory, storage granted to $package"
        ;;
    *)
        echo "usage: $0 [--remove]" >&2
        exit 2
        ;;
esac