Everything the UI does, the airflow command line can do too, and in deployment scripts and on servers without a browser it is often the only way in. The commands you will use most:
airflow dags list and airflow dags list-import-errors show what the Dag processor found, and what it could not load.
airflow dags pause and airflow dags unpause switch a Dag off and on.
airflow dags trigger <dag_id> creates a manual run, with --logical-date and --conf when you need them.
airflow dags test <dag_id> [date] runs a whole Dag run in one process, ignoring the pause switch: the quickest way to try a change.
airflow tasks test <dag_id> <task_id> [date] runs one task on its own. It records no state and runs no upstream tasks, so a task that reads another task's output gets None.
The terminal in this workspace knows these commands and a few more; type help.
Look, test one task for a past day, then test the whole Dag for that day.