grabbit
a2d49137f9
Integration tests (tests/): - 9 categories covering config, lifecycle, signals, supervision, cache, writeback, network faults, crash recovery, and CLI - Shell-based harness with mock NAS (network namespace + SFTP), fault injection (tc netem), and power loss simulation - TAP format runner (run-all.sh) with proper SKIP detection Rust unit tests (warpgate/src/): - 110 tests across 14 modules, all passing in 0.01s - Config parsing, defaults validation, RestartTracker logic, RC API response parsing, rclone arg generation, service config generation, CLI output formatting, warmup path logic Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
24 lines
727 B
Bash
Executable File
24 lines
727 B
Bash
Executable File
#!/usr/bin/env bash
|
|
set -euo pipefail
|
|
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
|
|
source "$SCRIPT_DIR/../harness/helpers.sh"
|
|
|
|
setup_test_env
|
|
trap teardown_test_env EXIT
|
|
|
|
# Generate syntactically invalid TOML (unclosed section header, unclosed string).
|
|
source "$HARNESS_DIR/config-gen.sh"
|
|
_gen_broken_config bad_toml
|
|
|
|
# The binary should fail to parse the config and exit non-zero.
|
|
output=$("$WARPGATE_BIN" status -c "$TEST_CONFIG" 2>&1) && {
|
|
echo "FAIL: warpgate status should have exited non-zero for bad TOML"
|
|
echo " output: $output"
|
|
exit 1
|
|
}
|
|
|
|
# The error should contain the standard config parse failure message.
|
|
assert_output_contains "$output" "Failed to parse config TOML"
|
|
|
|
echo "PASS: $(basename "$0" .sh)"
|