mateuslatrova commented on issue #35442:
URL: https://github.com/apache/airflow/issues/35442#issuecomment-2088490071

   > @mateuslatrova Some test modules from your list do not exists or named 
differently
   > 
   > ### Exists
   > I've marked this as completed
   > 
   > * 
[tests/providers/amazon/aws/triggers/test_athena.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_athena.py)
   > * 
[tests/providers/amazon/aws/triggers/test_batch.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_batch.py)
   > * 
[tests/providers/amazon/aws/triggers/test_emr.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_emr.py)
   > * 
[tests/providers/amazon/aws/triggers/test_glue_crawler.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_glue_crawler.py)
   > * 
[tests/providers/amazon/aws/triggers/test_lambda_function.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_lambda_function.py)
   > * 
[tests/providers/amazon/aws/triggers/test_rds.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_rds.py)
   > * 
[tests/providers/amazon/aws/triggers/test_redshift_cluster.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_redshift_cluster.py)
   > * 
[tests/providers/amazon/aws/utils/test_sqs.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/utils/test_sqs.py)
   > * 
[tests/providers/amazon/aws/utils/test_tags.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/utils/test_tags.py)
   > 
   > ### Not Exists
   > * 
[tests/providers/amazon/aws/operators/test_emr.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/operators/test_emr.py)
   > * 
[tests/providers/amazon/aws/operators/test_sagemaker.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/operators/test_sagemaker.py)
   > * 
[tests/providers/amazon/aws/sensors/test_emr.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/sensors/test_emr.py)
   > * 
[tests/providers/amazon/aws/utils/test_rds.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/utils/test_rds.py)
   > * 
[tests/providers/amazon/aws/utils/test_sagemaker.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/utils/test_sagemaker.py)
   > * 
[tests/providers/amazon/aws/waiters/test_base_waiter.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/waiters/test_base_waiter.py)
   > * 
[tests/providers/amazon/aws/triggers/test_step_function.py](https://github.com/apache/airflow/tree/main/tests/providers/amazon/aws/triggers/test_step_function.py)
   
   Hi @Taragolis ! Thanks for your help.
   
   I guess I was not so clear, but the corresponding code of each of that 
non-existing files is covered in other test files, and that is why I put those 
ones on the list. 
   
   For example, one test file from the above list that does not exist is 
`tests/providers/amazon/aws/operators/test_emr.py`. This test file would cover 
the code present in `airflow/providers/amazon/aws/operators/emr.py` , right? 
But this code is being covered in other test files:
   
   - `tests/providers/amazon/aws/operators/test_emr_add_steps.py`
   - `tests/providers/amazon/aws/operators/test_emr_containers.py`
   - `tests/providers/amazon/aws/operators/test_emr_create_job_flow.py`
   - `tests/providers/amazon/aws/operators/test_emr_modify_cluster.py`
   - `tests/providers/amazon/aws/operators/test_emr_notebook_execution.py`
   - `tests/providers/amazon/aws/operators/test_emr_serverless.py`
   - `tests/providers/amazon/aws/operators/test_terminate_job_flow.py`
   
   So the `tests/providers/amazon/aws/operators/test_emr.py` should not be in 
that list.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to