fix(tests): prevent tag inheritance tests from polluting production Celery queue (#14493)

product_tags_post_add_remove dispatches propagate_tags_on_product via dojo_dispatch_task.
When the signal fires outside a request context (e.g. during test setUp), get_current_user()
returns None, so we_want_async() always returns True regardless of block_execution — the task
goes to the shared Redis queue. The real Celery worker then picks it up and runs against the
live database, causing multi-hour tag propagation runs over large products.

Fix: add @override_settings(CELERY_TASK_ALWAYS_EAGER=True) to the three test classes that
enable system-wide product tag inheritance. This makes Celery run tasks inline in the test
process, keeping tasks off the shared Redis queue and ensuring assertions see propagated tags.

Author: valentijnscholten

unittests/test_tags.py

@@ -4,7 +4,7 @@
 
 from django.conf import settings
 from django.contrib.auth.models import User
-from django.test import Client
+from django.test import Client, override_settings
 from django.urls import reverse
 
 from dojo.models import Finding, Product, Test
@@ -454,6 +454,7 @@ def reimport_scan_with_params(self, test_id, filename, scan_type="ZAP Scan", min
             return {"test": new_test_id}
 
 
+@override_settings(CELERY_TASK_ALWAYS_EAGER=True)
 @versioned_fixtures
 class InheritedTagsTests(DojoAPITestCase):
 
@@ -610,6 +611,7 @@ def test_remove_tag_from_product_then_add_tag_to_product(self):
         self.assertEqual(product_tags_post_addition, self._convert_instance_tags_to_list(objects.get("finding")))
 
 
+@override_settings(CELERY_TASK_ALWAYS_EAGER=True)
 @versioned_fixtures
 class InheritedTagsImportTestAPI(DojoAPITestCase, InheritedTagsImportMixin):
 
@@ -626,6 +628,7 @@ def setUp(self):
         InheritedTagsImportMixin.setUp(self)
 
 
+@override_settings(CELERY_TASK_ALWAYS_EAGER=True)
 @versioned_fixtures
 class InheritedTagsImportTestUI(DojoAPITestCase, InheritedTagsImportMixin):