feat(tests): add PostgreSQL and SQLite support for atomic transaction tests

Author: HosseinNejatiJavaremi

.env.test

@@ -18,6 +18,13 @@ FASTAPI__SWAGGER_UI_PARAMS={}
 # Testcontainers Configuration
 TESTCONTAINERS_RYUK_CONTAINER_IMAGE=testcontainers/ryuk:0.14.0
 
+# Temporal Configuration
+TEMPORAL__IMAGE=temporalio/auto-setup:1.29.1
+TEMPORAL__HOST=localhost
+TEMPORAL__PORT=7233
+TEMPORAL__NAMESPACE=default
+TEMPORAL__TASK_QUEUE=test-task-queue
+
 # Redis Configuration
 REDIS__IMAGE=redis:8.4.0-alpine
 REDIS__MASTER_HOST=localhost:6379

features/atomic_transactions.feature

@@ -1,63 +1,143 @@
 @needs-postgres
 Feature: SQLAlchemy Atomic Transactions
 
-  Background:
-    Given the application database is initialized
+  Scenario Outline: Create and retrieve entity in atomic transaction
+    Given the application database is initialized for <db_type>
     And test entities are defined
-
-  Scenario: Create and retrieve entity in atomic transaction
     When a new entity is created in an atomic transaction
     Then the entity should be retrievable
 
-  Scenario: Handle transaction rollback on exception
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Handle transaction rollback on exception
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When a new entity creation fails within an atomic transaction
     Then no entity should exist in the database
     And the database session should remain usable
 
-  Scenario: Support nested atomic transactions
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Support nested atomic transactions
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When nested atomic transactions are executed
-    Then operations from successful nested transactions should not be committed
+    Then operations from successful nested transactions should be visible within outer transaction
     And operations from failed nested transactions should be rolled back
 
-  Scenario: Update entities in atomic transaction
-    Given an entity exists in the database
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Update entities in atomic transaction
+    Given the application database is initialized for <db_type>
+    And test entities are defined
+    And an entity exists in the database
     When the entity is updated within an atomic transaction
     Then the entity properties should reflect the updates
 
-  Scenario: Create entities with relationships in atomic transaction
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Create entities with relationships in atomic transaction
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When an entity with relationships is created in an atomic transaction
     Then the entity and its relationships should be retrievable
 
-  Scenario: Support different entity types in atomic transactions
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Support different entity types in atomic transactions
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When different types of entities are created in an atomic transaction
     Then all entity types should be retrievable
 
-  Scenario: Test error handling in atomic transactions
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Test error handling in atomic transactions
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When an error is triggered within an atomic transaction
     Then the appropriate error should be raised
     And the transaction should be rolled back
 
-  Scenario: Verify session consistency across multiple atomic blocks
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
+  Scenario Outline: Verify session consistency across multiple atomic blocks
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When operations are performed across multiple atomic blocks
     Then session should maintain consistency across atomic blocks
 
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
   @async
-  Scenario: Create and retrieve entity in async atomic transaction
+  Scenario Outline: Create and retrieve entity in async atomic transaction
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When a new entity is created in an async atomic transaction
     Then the async entity should be retrievable
 
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
   @async
-  Scenario: Handle transaction rollback in async atomic transaction
+  Scenario Outline: Handle transaction rollback in async atomic transaction
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When a new async entity creation fails within an atomic transaction
     Then no async entity should exist in the database
     And the async database session should remain usable
 
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
   @async
-  Scenario: Create multiple entities in async atomic transaction
+  Scenario Outline: Create multiple entities in async atomic transaction
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When multiple entities are created in an async atomic transaction
     Then all async entities should be retrievable
 
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |
+
   @async
-  Scenario: Create and manage complex entity relationships asynchronously
+  Scenario Outline: Create and manage complex entity relationships asynchronously
+    Given the application database is initialized for <db_type>
+    And test entities are defined
     When complex async operations are performed in a transaction
     Then all related entities should be accessible
+
+    Examples:
+      | db_type |
+      | postgres|
+      | sqlite  |