try a test step

.github/workflows/gitwatch.yml

@@ -62,7 +62,6 @@ jobs:
       - name: Setup node
         uses: actions/setup-node@v3
       - name: Setup BATS
-        # Even though this says 1.2.0,it's actually using 1.2.1
         run: sudo npm install -g bats
 
       - name: Install gitwatch dependencies
@@ -89,3 +88,6 @@ jobs:
           git config --global user.email "test@email.com"
           git config --global user.name "test user"
           bats -rt tests
+
+      - name: Test step
+        run: echo "Now at test step"

tests/zcommit.bats

@@ -1,38 +0,0 @@
-#!/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
-
-function zcommit_log_messages_working { #@test
-    # Start up gitwatch with logging, see if works
-    "${BATS_TEST_DIRNAME}"/../gitwatch.sh -l 10 "$testdir/local/remote" 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"
-
-    # Make a new change
-    echo "line2" >> file1.txt
-    sleep "$WAITTIME"
-
-    # Check commit log that the diff is in there
-    run git log -1 --oneline
-    [[ $output == *"file1.txt"* ]]
-}
-