Test/sftp to wasb operator coverage

[kyungjunleeme]

Related to

This PR addresses https://github.com/apache/airflow/issues/3190971584](https://github.com/apache/airflow/pull/52618) by adding missing unit tests for the dry_run() method in SFTPToWasbOperator.

What this PR adds

• test_dry_run_logs_and_skips_real_action
  Verifies that in Airflow 3+:

  • dry_run() logs the “Process will upload…” and “Executing delete…” messages
  • No actual load_file or delete_file calls are made

• test_dry_run_raises_not_implemented
  Mocks AIRFLOW_V_3_0_PLUS = False to simulate Airflow < 3.0, and asserts that dry_run() raises NotImplementedError with the message:

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in airflow-core/newsfragments.

[kyungjunleeme]

At first, I wasn’t aware there was a rule regarding the use of caplog, so I thought it absolutely had to be changed. But now I'm curious to hear the opinion of the Airflow maintainers on this.

[kyungjunleeme]

I think this message is more clear than before. How about ur opinion?

[kyungjunleeme]

@kaxil hello,

This issue is related to the previous PR(#52618 ) and the message section. I have added a test case to cover this scenario.
Could you please take a look when you have a moment?

[kyungjunleeme]

@potiuk

I’m still getting used to how things work in open-source, so I wanted to ask:
Is it okay to mention someone to request a review if a PR hasn’t received any feedback yet?

The PR is related to a recently merged one, so I thought it might make sense to get input from someone involved in that.

and If no reviewer is assigned to a PR, is it okay to mention someone?
I'm wondering if there's an implicit rule around that.
When I open a PR and no reviewer gets assigned, I’m a bit worried it might get overlooked.

---

Could you review my PR ?

[potiuk]

and If no reviewer is assigned to a PR, is it okay to mention someone?
I'm wondering if there's an implicit rule around that.
When I open a PR and no reviewer gets assigned, I’m a bit worried it might get overlooked.

Better to just "remind" but not mention anyone. This will put it on the top and someone who is actually looking might have another chance not to overlook it.

[potiuk]

Unless someone already commented and you continue conversation of course.

[kyungjunleeme]

I just wanted to check — when you say "just remind", do you mean adding a comment without tagging anyone, like "Just a gentle reminder in case this was overlooked"?

[potiuk]

yes

[potiuk]

Generally - it's up to you as author to lead your PR to completion. But you have to be mindful that people here are volunteers - so you neded to figure out what's best on your own, that's the beauty and difficulty of being in opesource that in many cases this is all about humans and empathy and communication and you will not get ready recipes what to do.

Eventually - use your own judgment what is best. And sometimes you will make mistakes and be corrected or reminded - but eventually - you are responsible to do what's good.

[kyungjunleeme]

Yes, I'm learning a lot from various aspects while contributing to open source. Thank you for your thoughtful advice.

[kyungjunleeme]

@kaxil
If you have some time, I'd really appreciate it if you could review this PR.
I’d like to take full responsibility for finishing it properly, and your feedback would be invaluable to ensure everything is in good shape.

Thank you in advance for your time and support!

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed in 5 days if no further activity occurs. Thank you for your contributions.