Unix commands such as for file browsing

Unix commands are what almost every dev environment, CI runner, and Docker container speaks natively, no GUI required. You don't need to master all of them; a working knowledge of a couple dozen goes a very long way.

ls = list files and directories
cd = change directory
mv = move a file or directory
more = view a file's text, one page at a time
nano = edit a file's text, with simple commands
grep = find text in files
chmod = change mode of file permissions
curl = call a URL such as an http web address
claude = AI agent

Here's why that belongs on a testing page: grep and sed are how you find one specific failure in thousands of lines of test output or a log file, instead of scrolling. curl is how you sanity-check an API by hand — the same endpoint a UI test might also exercise — before writing the real test. chmod +x is how a test script becomes directly runnable. And piping a few commands together is often how a CI step gets built without reaching for a "real" programming language just to glue two tools together.

Learn more at Software Carpentry's Unix shell lesson, or watch NetworkChuck's "60 Linux Commands you NEED to know (in 10 minutes)" for a fast-paced video introduction.

Examples you can ask AI

I've never used a command line before — what are the handful of Unix commands actually worth learning first for someone getting into testing?
How would I use grep to find every failing test in a huge CI log without scrolling through it by hand?
How do I chain a few Unix commands together into a small, reliable script for a CI step, instead of reaching for a full programming language?