test: improve Postman test script with retry logic and better error handling for Rails server startup

Author: davidagustin

travis/postman.sh

@@ -5,16 +5,46 @@ set -ex
 # Set up fresh db
 bundle exec rake db:setup db:populate
 
-bundle exec rails server &
+# Start Rails server in background
+bundle exec rails server -b 0.0.0.0 &
 rails_pid=$!
-sleep 10  # Make sure server is up before continuing
 
 # Kill Rails process on exit
-trap "kill $rails_pid" EXIT
+trap "kill $rails_pid 2>/dev/null || true" EXIT
+
+# Wait for Rails server to be ready with retry logic
+echo "Waiting for Rails server to start..."
+max_attempts=30
+attempt=0
+while [ $attempt -lt $max_attempts ]; do
+  if curl -f -s http://localhost:3000/resources?category_id=1 >/dev/null 2>&1; then
+    echo "Rails server is ready!"
+    break
+  fi
+  
+  # Check if the server process is still running
+  if ! kill -0 $rails_pid 2>/dev/null; then
+    echo "ERROR: Rails server process died unexpectedly"
+    wait $rails_pid || true
+    exit 1
+  fi
+  
+  attempt=$((attempt + 1))
+  echo "Server not ready yet, waiting... (attempt $attempt/$max_attempts)"
+  sleep 2
+done
+
+if [ $attempt -eq $max_attempts ]; then
+  echo "ERROR: Rails server did not become ready after $max_attempts attempts"
+  echo "Checking server logs..."
+  kill $rails_pid 2>/dev/null || true
+  wait $rails_pid || true
+  exit 1
+fi
 
 # Hit a page to force Rails to cache the loading of modules, avoiding a timeout
 # failure on the first Postman test.
-curl -v http://localhost:3000/resources?category_id=1 >/dev/null
+curl -f -v http://localhost:3000/resources?category_id=1 >/dev/null
 
 newman run postman/AskDarcel%20API.postman_collection.json -g postman/globals.postman_globals.json
 newman run postman/AskDarcel%20Admin%20API.postman_collection.json -g postman/globals.postman_globals.json