Debugging airflow tasks using airflow test vs using DebugExecutor

I'm searching for best way to run/debug tasks and dags in my IDE. I see that there are two ways of doing this. I can run airflow test command in debug mode for particular dag and optionally task. Other way is to use DebugExecutor and run particular dag. I see that both ways require that Airflow database is up and running and that all pools are configured (probably queues as well). My questions are:

1. What is the main difference between these two?
2. Does airflow test uses DebugExecutor under the hood?
3. Is there a way to run/debug dags and tasks without running Airflow database and creating dependent pools and queues?