ReachableCEO
ce60ffcb1f
- Move settings file to config/ directory - Move control script to code/ directory - Remove create-network.sh script as requested - Create comprehensive .gitignore file to handle test logs and artifacts - Update all scripts to reference new file locations - Update STATUS.md to reflect new file structure Co-authored-by: Qwen-Coder <qwen-coder@alibabacloud.com>
45 lines
1.3 KiB
Bash
Executable File
45 lines
1.3 KiB
Bash
Executable File
#!/bin/bash
|
|
|
|
# Unit test for docker-socket-proxy component
|
|
# Following TDD: Write test → Execute test → Test fails → Write minimal code to pass test
|
|
|
|
set -e
|
|
|
|
# Load environment settings
|
|
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")/.." && pwd)"
|
|
CONFIG_DIR="${SCRIPT_DIR}/config"
|
|
ENV_FILE="${CONFIG_DIR}/TSYSDevStack-SupportStack-Demo-Settings"
|
|
|
|
if [ ! -f "$ENV_FILE" ]; then
|
|
echo "Error: Environment settings file not found at $ENV_FILE"
|
|
exit 1
|
|
fi
|
|
|
|
source "$ENV_FILE"
|
|
|
|
# Test function to validate docker-socket-proxy
|
|
test_docker_socket_proxy() {
|
|
echo "Testing docker-socket-proxy availability and functionality..."
|
|
|
|
# Check if the container exists and is running
|
|
if docker ps | grep -q "$DOCKER_SOCKET_PROXY_NAME"; then
|
|
echo "✓ docker-socket-proxy container is running"
|
|
else
|
|
echo "✗ docker-socket-proxy container is NOT running"
|
|
return 1
|
|
fi
|
|
|
|
# Additional tests can be added here to validate the proxy functionality
|
|
# For example, testing if it can access the Docker socket and respond appropriately
|
|
echo "✓ Basic docker-socket-proxy test passed"
|
|
return 0
|
|
}
|
|
|
|
# Execute the test
|
|
if test_docker_socket_proxy; then
|
|
echo "✓ docker-socket-proxy test PASSED"
|
|
exit 0
|
|
else
|
|
echo "✗ docker-socket-proxy test FAILED"
|
|
exit 1
|
|
fi |