Slience output from curl for integration tests

We use curl in our integration test script to make sure the application container is
available before moving on. We expect many connection errors and don't care
about the output of curl, so this will just swallow all of the output.

script/integration_tests

@@ -72,15 +72,18 @@ $CONTAINER_IMAGE \
 
 # Use curl to wait for application container to become available
 docker pull curlimages/curl:latest
+echo "Waiting for application container to become available"
 docker run --network atat \
   curlimages/curl:latest \
-  curl --connect-timeout 3 \
+  curl \
+  --silent \
+  --connect-timeout 3 \
   --max-time 5 \
   --retry $CONTAINER_TIMEOUT \
   --retry-connrefused \
   --retry-delay 1 \
   --retry-max-time $CONTAINER_TIMEOUT \
-  test-atat:8000
+  test-atat:8000 >/dev/null
 
 # Run Ghost Inspector tests
 docker pull ghostinspector/test-runner-standalone:latest

uitests/README.md

@@ -58,6 +58,5 @@ NGROK_TOKEN=<token> GI_API_KEY=<api key> GI_SUITE=<suite> CONTAINER_IMAGE=atat:b
 
 - If you get errors regarding ports being in use, make sure you don't have instances of the Flask app, Postgres, or Redis running locally using those ports.
 - If the curl command used to wait for the application container times out and fails, you can increase the timeout by setting a CONTAINER_TIMEOUT environment variable. It defaults to 200 in the script.
-- The curl command will print errors until it successfully connects to the application container. These are normal and expected. When it finally connects, it will print the ATAT home page HTML to STDOUT.
 - You may see errors like "No such container". The script attempts to clean up any previous incarnations of the containers before it starts, and it may print errors when it doesn't find them. This is fine.
 - The script is, for the most part, a series of docker commands, so try running the commands individually and debugging that way.