[GitHub] [airflow] potiuk commented on issue #18758: Deprecate 'airflow dags test' and merge the use case into 'airflow dags backfill' and 'airflow dags trigger'

[GitBox <gi...@apache.org>]

potiuk commented on issue #18758:
URL: https://github.com/apache/airflow/issues/18758#issuecomment-974681486


   One comment to that is (via #19578) that users also use (and quite often) `airflow tasks test` to run single tasks for a particular DAG. I think while we could get-by with backfil on `dags test` , this will not be the case for `tasks test`- and we need to figure out how to pass the data_interval to that comand as well. I think from the [docs](https://airflow.apache.org/docs/apache-airflow/stable/howto/timetable.html?highlight=timetables#define-scheduling-logic) the intention was that `infer_data_interval` for the custom timetable will do that, but it does not seem to be plugged-in currently (and `tasks test` with custom timetables fails as it cannot infer the interval).
   
   I think if we solve it for `tasks test`, the same solution could be used for `dags test`. 
   
   One good thing about `dags test` also is that it uses "DebugExecutor" and did not leave traces in the DB after it was executed (or so I thought at least - and for sure that was the itention of the `dag tests` command. I am not sure if this assumption holds true still - or needs to be 'fixed". But the idea was that you run the whole dag this way, but that it will not be stored in the database. I am not sure if this is something that we want to `mix` with backfill - though. For me `dags tests` still has a good use here.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org