Modern QA2026Directories QA Engineers Use Most — tiles
Log inJoin
2 / 55 · 19 Linux & Command Line · Linux Directory Structure← prev⊞ allnext →☰ Read as one page

1.2Directories QA Engineers Use Most

/home/user/ (Your Home Directory, ~)

This is where you work. Your scripts, test configurations, SSH keys, and shell customizations live here.

# Navigate to home directory
cd ~
# Or simply:
cd

# Common QA files in home directory
~/.ssh/config          # SSH connection shortcuts
~/.bashrc              # Shell customization (aliases, PATH)
~/.npmrc               # npm configuration
~/.env                 # Personal environment variables (not committed)
~/projects/            # Your cloned repositories

/var/log/ (Logs)

This is where you investigate failures. Application logs, system logs, and web server logs all live here.

# Common log locations
/var/log/syslog                    # System messages
/var/log/auth.log                  # Authentication events
/var/log/nginx/access.log          # Nginx access logs
/var/log/nginx/error.log           # Nginx error logs
/var/log/app/application.log       # Application-specific logs
/var/log/postgresql/postgresql.log # Database logs

/etc/ (Configuration)

Configuration files for system services and applications. When tests fail due to misconfiguration, this is where you look.

# Common configuration files
/etc/hosts                # DNS overrides (useful for test environments)
/etc/nginx/nginx.conf     # Nginx web server config
/etc/environment          # System-wide environment variables
/etc/postgresql/pg_hba.conf  # PostgreSQL access control
/etc/ssl/certs/           # SSL certificates

/tmp/ (Temporary Files)

Temporary data that is cleared on reboot. Useful for staging test data or storing intermediate results.

# Use /tmp for temporary test data
cp test-data.json /tmp/
# Run tests that use /tmp/test-data.json
# On reboot, the file is automatically cleaned up

/proc/ (Virtual Filesystem)

Not real files -- this is a window into the kernel and running processes. Useful for debugging.

# Check system memory
cat /proc/meminfo | head -5

# Check CPU information
cat /proc/cpuinfo | grep "model name" | head -1

# Check a specific process
cat /proc/1234/status | grep -E "(Name|State|VmRSS)"