From 25ba1427b1be432b8f03ff69ecc224116f7a5e15 Mon Sep 17 00:00:00 2001
From: Jun-te Kim <juntekim@googlemail.com>
Date: Tue, 2 Jun 2026 15:30:58 +0000
Subject: [PATCH] seperate ddd tests

---
 .github/workflows/unit_tests.yml | 15 ++++-----------
 1 file changed, 4 insertions(+), 11 deletions(-)

diff --git a/.github/workflows/unit_tests.yml b/.github/workflows/unit_tests.yml
index 15d4cfe9..12d836d0 100644
--- a/.github/workflows/unit_tests.yml
+++ b/.github/workflows/unit_tests.yml
@@ -61,14 +61,7 @@ jobs:
             -e DB_PORT=5432 \
             model-test pytest -vv -m 'not integration'
 
-      # The DDD rewrite (tests/) defines SQLModel table classes that map to the
-      # same physical tables as the legacy backend models. Both sets share the
-      # one global SQLModel.metadata, so they cannot be imported into the same
-      # pytest process. It runs as a separate invocation until the legacy
-      # models are retired. Its DB is spawned in-process by pytest-postgresql,
-      # so no DB service or env is required.
-      - name: Run DDD tests
-        run: |
-          docker run --rm \
-            --network host \
-            model-test pytest -vv tests/
+      # The DDD rewrite (tests/) runs in its own workflow (ddd_tests.yml): its
+      # SQLModel table classes map to the same physical tables as the legacy
+      # backend models and share the one global SQLModel.metadata, so the two
+      # suites cannot be imported into the same pytest process.