2
0
mirror of https://github.com/gitwatch/gitwatch synced 2024-11-15 06:12:52 +00:00
gitwatch/tests/status-change.bats
Dave Musicant / thinkpad 5371385aa1 more linter bug squashing
2022-05-03 13:16:18 -05:00

47 lines
1.2 KiB
Bash

#!/usr/bin/env bats
# This is a testscript using the bats testing framework:
# https://github.com/sstephenson/bats
# To run it, at a command prompt:
# bats testscript.bats
load startup-shutdown
@test "commit only when git status change"
{
# Start up gitwatch and capture its output
${BATS_TEST_DIRNAME}/../gitwatch.sh "$testdir/local/remote" > "$testdir/output.txt" 3>&- &
GITWATCH_PID=$!
# Keeps kill message from printing to screen
disown
# Create a file, verify that it hasn't been added yet, then commit
cd remote
# According to inotify documentation, a race condition results if you write
# to directory too soon after it has been created; hence, a short wait.
sleep 1
echo "line1" >> file1.txt
# Wait a bit for inotify to figure out the file has changed, and do its add,
# and commit
sleep $WAITTIME
# Touch the file, but no change
touch file1.txt
sleep $WAITTIME
echo "hi there" > "$testdir/output.txt"
cat "$testdir/output.txt"
run git log -1 --oneline
echo $output
#run bash -c "grep \"nothing to commit\" $testdir/output.txt | wc -l"
run grep "nothing to commit" $testdir/output.txt
[ $status -ne 0 ]
}