20 Essential Linux Commands Every Automation Test Engineer Should Master

Last week our CI pipeline failed with only the message “Connection refused”. The developer suggested checking the server, and after logging into the test machine three simple commands ( ps -ef | grep order-service, netstat -tunlp | grep 8080, tail -f /var/log/order.log) revealed that the service had crashed and not restarted. This incident highlighted that automation testing now requires environment awareness, troubleshooting skills, and close collaboration.

1. File and Directory Operations (High‑frequency daily tasks)

ls -l

– detailed list with permissions, size, and timestamp ls -lh – human‑readable file sizes (e.g., 2.3K) ls -lt – sort by modification time, newest first cd ~/projects/api-test – change to a project directory pwd – print the current working directory cat config.yaml – display the entire file less large_log.log – paginate a large file (quit with q) head -n 20 report.html – view the first 20 lines of a file tail -f app.log – follow a log file in real time (golden command for debugging) grep "ERROR" app.log – search for error strings; additional options: -i ignore case, -n show line numbers, -A 3 -B 2 show context

2. Process and Port Management (Core service verification)

ps -ef | grep pytest

– check whether an automation process is running ps aux | grep nginx – view web‑service processes netstat -tunlp | grep 8080 – see if port 8080 is occupied ss -tuln – faster alternative to

netstat

kill -9 12345

– force‑kill a process by PID pkill -f "pytest" – kill all processes containing the string “pytest”

3. File Transfer and Compression (Deployment essentials)

scp test_order.py [email protected]:/home/qa/

– upload a script to a remote server scp [email protected]:/var/log/app.log ./ – download a log file to the local machine tar -czvf report.tar.gz reports/ – compress a directory into a gzip archive tar -xzvf report.tar.gz – extract the archive

4. Network and Service Testing (Interface verification)

curl http://api.test.com/users/1

– simple GET request

curl -X POST http://api.test.com/login -H "Content-Type: application/json" -d '{"user":"test","pwd":"123"}'

– POST a JSON payload curl -b "sessionid=abc123" http://api.test.com/profile – request with a cookie ping api.test.com – basic connectivity and DNS resolution test telnet db.test.com 3306 – test whether the database port is reachable nc -zv redis.test.com 6379 – modern port probe using netcat

5. System Monitoring (Performance triage)

top

/ htop – real‑time CPU and memory usage (htop provides a friendlier UI) df -h – display disk usage in human‑readable units du -sh ./logs – show the total size of the logs directory

6. Permissions and Ownership (Collaboration safety)

chmod +x run_tests.sh

– add execute permission to a script chmod 644 config.yaml – set a file to read‑only for others sudo chown qa:qa report.html – change file owner and group

7. Scheduling and Background Tasks (CI/CD extensions)

crontab -e

– edit cron jobs; example entry to run regression nightly:

0 2 * * * cd /project && python -m pytest --html=report.html

nohup python long_run_test.py > test.log 2>&1 &

– run a command that survives SSH disconnection

8. Miscellaneous Utilities (Productivity boosters)

which python

– locate the Python executable to avoid version confusion history | grep curl – retrieve previously used curl commands alias ll='ls -lh' – create a shortcut for a common listing alias logt='tail -f /var/log/test.log' – shortcut for tailing a log file

Key take‑aways: don’t memorize commands in isolation—understand the scenarios they solve, combine them with pipelines (e.g., grep ERROR log | wc -l), practice regularly in test environments, and keep a personal cheat sheet at hand. Mastering these commands turns the Linux shell into a powerful second workstation for every automation test engineer.