Refactor default_worker_tasks fixture in pytest

[imSanko]

Updated the default_worker_tasks fixture in pytest to remove circular dependency and improve readability. The fixture now correctly initializes the set and adds tasks from the tests module.

• Refactored the default_worker_tasks fixture in pytest to address a circular dependency issue and improve readability. Previously, the fixture had a circular dependency problem where it tried to reference itself within its definition, which could lead to unexpected behavior.

• The updated code initializes the default_worker_tasks set correctly and then adds tasks from the tests module. This change ensures that the fixture is correctly defined and provides a clear separation of concerns, making the code more maintainable and easier to understand.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 26.49%. Comparing base (6449d98) to head (57c35ca).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #215   +/-   ##
=======================================
  Coverage   26.49%   26.49%           
=======================================
  Files          36       36           
  Lines        1057     1057           
  Branches      213      213           
=======================================
  Hits          280      280           
  Misses        751      751           
  Partials       26       26           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[Nusnus]

Hey there, did you have any actual problems with the original code? Something didn't work as expected?

The tasks set needs to be received as an argument for the pytest fixtures mechanism to work properly, removing it breaks the flow, as the failing tests show.

What did you try to achieve? Maybe I can assist.

P.s
Check out: https://docs.pytest.org/en/latest/reference/fixtures.html#fixtures

[Nusnus]

By receiving the set from "itself", you can populate the set in different fixture availability scopes to control which test has which tasks.

It's a feature not a bug :)