trcli 1.13.3__tar.gz → 1.14.0__tar.gz

{trcli-1.13.3 → trcli-1.14.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: trcli
-Version: 1.13.3
+Version: 1.14.0
 License-File: LICENSE.md
 Requires-Dist: click<8.2.2,>=8.1.0
 Requires-Dist: pyyaml<7.0.0,>=6.0.0

{trcli-1.13.3 → trcli-1.14.0}/README.md

@@ -33,7 +33,7 @@ trcli
 ```
 You should get something like this:
 ```
-TestRail CLI v1.13.3
+TestRail CLI v1.14.0
 Copyright 2025 Gurock Software GmbH - www.gurock.com
 Supported and loaded modules:
     - parse_junit: JUnit XML Files (& Similar)
@@ -51,7 +51,7 @@ CLI general reference
 --------
 ```shell
 $ trcli --help
-TestRail CLI v1.13.3
+TestRail CLI v1.14.0
 Copyright 2025 Gurock Software GmbH - www.gurock.com
 Usage: trcli [OPTIONS] COMMAND [ARGS]...
 
@@ -196,7 +196,7 @@ For further detail, please refer to the
 
 ### Using Glob Patterns for Multiple Files
 
-TRCLI supports glob patterns to process multiple report files in a single command. This feature is available for **JUnit XML** and **Cucumber JSON** parsers.
+TRCLI supports glob patterns to process multiple report files in a single command. This feature is available for **JUnit XML**, **Robot Framework**, and **Cucumber JSON** parsers.
 
 #### Important: Shell Quoting Requirement
 
@@ -239,6 +239,7 @@ When a glob pattern matches **multiple files**, TRCLI automatically:
 3. **Merges test results** into a single combined report
 4. **Writes merged file** to current directory:
    - JUnit: `Merged-JUnit-report.xml`
+   - Robot Framework: `Merged-Robot-report.xml`
    - Cucumber: `merged_cucumber.json`
 5. **Processes the merged file** as a single test run upload
 
@@ -263,6 +264,23 @@ trcli parse_junit \
   --case-matcher auto
 ```
 
+**Robot Framework - Multiple output files:**
+```bash
+# Merge multiple Robot Framework test runs
+trcli -y \
+  -h https://example.testrail.com \
+  --project "My Project" \
+  parse_robot \
+  -f "reports/robot-*.xml" \
+  --title "Merged Robot Tests"
+
+# Recursive search for all Robot outputs
+trcli parse_robot \
+  -f "test-results/**/output.xml" \
+  --title "All Robot Results" \
+  --case-matcher property
+```
+
 **Cucumber JSON - Multiple test runs:**
 ```bash
 # Merge multiple Cucumber JSON reports
@@ -864,6 +882,40 @@ the `--special-parser saucectl` command line option.
 Please refer to the [SauceLabs and saucectl reports](https://support.gurock.com/hc/en-us/articles/12719558686484)
 documentation for further information.
 
+#### Cross-suite test plans with multisuite parser
+
+If your test automation spans multiple TestRail suites, the multisuite parser allows you to create a single test plan with one run per suite from a single JUnit XML report. The CLI automatically detects which suite each test case belongs to, groups them accordingly, and creates or updates a test plan with the appropriate structure.
+
+**Requirements:**
+- All test cases must have case IDs (C123 format in test names or `test_id` properties)
+- Must use `--case-matcher name` or `--case-matcher property` (not `auto`)
+- All cases must belong to the same project (cross-project cases are skipped with warnings)
+
+**Basic usage (create new plan):**
+```bash
+trcli parse_junit \
+  --special-parser multisuite \
+  --title "Cross-Suite Test Plan" \
+  --file results.xml \
+  --case-matcher property
+```
+
+**Add to existing plan:**
+```bash
+trcli parse_junit \
+  --special-parser multisuite \
+  --plan-id 1234 \
+  --file results.xml \
+  --case-matcher property
+```
+
+The parser automatically:
+- Fetches suite information for each case ID concurrently (fast performance)
+- Groups cases by their suite
+- Creates a test plan with one run per suite
+- Uploads results to the correct run within the plan
+- Includes suite names and test counts in the plan description
+
 #### Creating new test runs
 
 When a test run MUST created before using one of the parse commands, use the `add_run` command. For example, if
@@ -1623,7 +1675,7 @@ Options:
 ### Reference
 ```shell
 $ trcli add_run --help
-TestRail CLI v1.13.3
+TestRail CLI v1.14.0
 Copyright 2025 Gurock Software GmbH - www.gurock.com
 Usage: trcli add_run [OPTIONS]
 
@@ -1640,6 +1692,18 @@ Options:
   --run-end-date         The expected or scheduled end date of this test run in MM/DD/YYYY format
   --run-assigned-to-id   The ID of the user the test run should be assigned
                          to.  [x>=1]
+  --clear-run-assigned-to-id  Clear the assignee of the test run (only valid
+                         when updating with --run-id).
+  --clear-run-description  Clear the description of the test run (only valid
+                         when updating with --run-id).
+  --clear-milestone-id   Clear the milestone association of the test run (only
+                         valid when updating with --run-id).
+  --clear-run-start-date  Clear the start date of the test run (only valid
+                         when updating with --run-id).
+  --clear-run-end-date   Clear the end date of the test run (only valid when
+                         updating with --run-id).
+  --clear-run-case-ids   Clear all case IDs from the test run (only valid when
+                         updating with --run-id).
   --run-include-all      Use this option to include all test cases in this test run.
   --auto-close-run       Use this option to automatically close the created run.
   --run-case-ids         Comma separated list of test case IDs to include in
@@ -1712,29 +1776,103 @@ trcli -y -h https://example.testrail.io/ --project "My Project" \
 - **Action Requirements**: `update` and `delete` actions require an existing run (--run-id must be provided)
 - **Validation**: Invalid reference formats are rejected with clear error messages
 
-#### Examples
+### Managing Assignees in Test Runs
+
+The `add_run` command supports comprehensive assignee management for test runs. You can assign runs to users when creating or updating them, and clear assignees when needed.
+
+#### Assigning Runs to Users
+
+When creating a new test run or updating an existing one, you can assign it to a user using the `--run-assigned-to-id` option:
 
-**Complete Workflow Example:**
 ```bash
-# 1. Create run with initial references
-trcli -y -h https://example.testrail.io/ <--username and --password or --key> --project "My Project" \
-  add_run --title "Sprint 1 Tests" --run-refs "JIRA-100,JIRA-200" -f "run_config.yml"
+# Create a new run and assign to user ID 5
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --title "My Test Run" --run-assigned-to-id 5
 
-# 2. Add more references (from the config file)
-trcli -y -h https://example.testrail.io/ <--username and --password or --key>  --project "My Project" \
-  -c run_config.yml add_run --run-refs "JIRA-300,REQ-001" --run-refs-action "add"
+# Update an existing run and change the assignee
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --run-assigned-to-id 10
+```
+
+#### Clearing Assignees from Test Runs
+
+To remove the assignee from an existing test run, use the `--clear-run-assigned-to-id` flag:
+
+```bash
+# Clear the assignee from an existing run
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-run-assigned-to-id
+```
 
-# 3. Replace all references with new ones
-trcli -y -h https://example.testrail.io/ <--username and --password or --key>  --project "My Project" \
-  -c run_config.yml add_run --run-refs "FINAL-100,FINAL-200" --run-refs-action "update"
+#### Assignee Management Rules
 
-# 4. Remove specific references
-trcli -y -h https://example.testrail.io/ <--username and --password or --key>  --project "My Project" \
-  -c run_config.yml add_run --run-refs "FINAL-100" --run-refs-action "delete"
+- **Update Mode Only**: The `--clear-run-assigned-to-id` flag can only be used when updating an existing run (requires `--run-id`)
+- **Mutually Exclusive**: You cannot use both `--run-assigned-to-id` and `--clear-run-assigned-to-id` in the same command
 
-# 5. Clear all references
-trcli -y -h https://example.testrail.io/ <--username and --password or --key>  --project "My Project" \
-  -c run_config.yml add_run --run-refs-action "delete"
+### Clearing Run Attributes
+
+The `add_run` command provides `--clear-*` flags to remove (set to null) various run attributes during updates. All clear flags require `--run-id` and are mutually exclusive with their corresponding set parameters.
+
+#### Available Clear Flags
+
+| Flag | Clears | API Effect | Mutually Exclusive With |
+|------|--------|------------|------------------------|
+| `--clear-run-description` | Description text | Sets `description: null` | `--run-description` |
+| `--clear-milestone-id` | Milestone association | Sets `milestone_id: null` | `--milestone-id` |
+| `--clear-run-start-date` | Start date | Sets `start_on: null` | `--run-start-date` |
+| `--clear-run-end-date` | End date | Sets `due_on: null` | `--run-end-date` |
+| `--clear-run-case-ids` | All case selections | Sets `include_all: false, case_ids: []` | `--run-case-ids`, `--run-include-all` |
+
+#### Clear Description Example
+
+```bash
+# Clear the description from a run
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-run-description
+```
+
+#### Clear Milestone Example
+
+```bash
+# Remove milestone association
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-milestone-id
+```
+
+#### Clear Dates Example
+
+```bash
+# Clear start date
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-run-start-date
+
+# Clear end date
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-run-end-date
+
+# Clear both dates at once
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-run-start-date --clear-run-end-date
+```
+
+#### Clear Case Selection Example
+
+```bash
+# Clear all case selections (empty run)
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "My Test Run" --clear-run-case-ids
+```
+
+#### Clear Multiple Attributes Example
+
+```bash
+# Clear multiple attributes in one command
+trcli -y -h https://example.testrail.io/ --project "My Project" \
+  add_run --run-id 123 --title "Clean Run" \
+  --clear-run-description \
+  --clear-milestone-id \
+  --clear-run-start-date \
+  --clear-run-end-date
 ```
 
 Generating test cases from OpenAPI specs
@@ -1747,7 +1885,7 @@ providing you with a solid base of test cases, which you can further expand on T
 ### Reference
 ```shell
 $ trcli parse_openapi --help
-TestRail CLI v1.13.3
+TestRail CLI v1.14.0
 Copyright 2025 Gurock Software GmbH - www.gurock.com
 Usage: trcli parse_openapi [OPTIONS]
 

{trcli-1.13.3 → trcli-1.14.0}/tests/test_api_request_handler.py

@@ -1114,20 +1114,256 @@ class TestApiRequestHandler:
         assert 50 in payload["case_ids"], "Should include existing case ID"
 
     @pytest.mark.api_handler
-    def test_upload_attachments_413_error(self, api_request_handler: ApiRequestHandler, requests_mock, tmp_path):
-        """Test that 413 errors (file too large) are properly reported."""
-        run_id = 1
+    def test_update_run_clears_description(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run can clear description by setting it to null"""
+        run_id = 300
+        run_name = "Test Run"
+
+        # Mock get_run response with existing description
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "Existing description",
+            "refs": "",
+            "include_all": True,
+            "plan_id": None,
+            "config_ids": [],
+        }
+
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run with description=None to clear it
+        run_data, error = api_request_handler.update_run(run_id, run_name, description=None)
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload sent to update_run
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["description"] is None, "description should be null"
+
+    @pytest.mark.api_handler
+    def test_update_run_clears_milestone(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run can clear milestone_id by setting it to null"""
+        run_id = 301
+        run_name = "Test Run"
+
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "",
+            "refs": "",
+            "include_all": True,
+            "plan_id": None,
+            "config_ids": [],
+        }
+
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run with milestone_id=None to clear it
+        run_data, error = api_request_handler.update_run(run_id, run_name, milestone_id=None)
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["milestone_id"] is None, "milestone_id should be null"
+
+    @pytest.mark.api_handler
+    def test_update_run_clears_start_date(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run can clear start_date by setting it to null"""
+        run_id = 302
+        run_name = "Test Run"
+
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "",
+            "refs": "",
+            "include_all": True,
+            "plan_id": None,
+            "config_ids": [],
+        }
+
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run with start_date=None to clear it
+        run_data, error = api_request_handler.update_run(run_id, run_name, start_date=None)
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["start_on"] is None, "start_on should be null"
+
+    @pytest.mark.api_handler
+    def test_update_run_clears_end_date(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run can clear end_date by setting it to null"""
+        run_id = 303
+        run_name = "Test Run"
+
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "",
+            "refs": "",
+            "include_all": True,
+            "plan_id": None,
+            "config_ids": [],
+        }
+
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run with end_date=None to clear it
+        run_data, error = api_request_handler.update_run(run_id, run_name, end_date=None)
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["due_on"] is None, "due_on should be null"
+
+    @pytest.mark.api_handler
+    def test_update_run_clears_case_ids(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run can clear case_ids by setting to empty array"""
+        run_id = 304
+        run_name = "Test Run"
+
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "",
+            "refs": "",
+            "include_all": False,
+            "plan_id": None,
+            "config_ids": [],
+        }
 
-        # Mock get_tests endpoint
-        mocked_tests_response = {
+        get_tests_response = {
             "offset": 0,
             "limit": 250,
-            "size": 1,
+            "size": 2,
             "_links": {"next": None, "prev": None},
-            "tests": [{"id": 1001, "case_id": 100}],
+            "tests": [{"id": 1, "case_id": 10, "status_id": 1}, {"id": 2, "case_id": 20, "status_id": 1}],
+        }
+
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.get(create_url(f"get_tests/{run_id}"), json=get_tests_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run with case_ids=[] and include_all=False to clear all cases
+        run_data, error = api_request_handler.update_run(run_id, run_name, include_all=False, case_ids=[])
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["include_all"] == False, "include_all should be False"
+        assert payload["case_ids"] == [], "case_ids should be empty array"
+
+    @pytest.mark.api_handler
+    def test_update_run_clears_multiple_attributes(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run can clear multiple attributes at once"""
+        run_id = 305
+        run_name = "Test Run"
+
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "Old description",
+            "refs": "REF-1",
+            "include_all": True,
+            "plan_id": None,
+            "config_ids": [],
+        }
+
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run clearing multiple attributes
+        run_data, error = api_request_handler.update_run(
+            run_id, run_name, description=None, milestone_id=None, start_date=None, end_date=None
+        )
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["description"] is None, "description should be null"
+        assert payload["milestone_id"] is None, "milestone_id should be null"
+        assert payload["start_on"] is None, "start_on should be null"
+        assert payload["due_on"] is None, "due_on should be null"
+
+    @pytest.mark.api_handler
+    def test_update_run_preserves_values_with_sentinel(self, api_request_handler: ApiRequestHandler, requests_mock):
+        """Test that update_run preserves values when sentinel (...) is used"""
+        run_id = 306
+        run_name = "Test Run"
+
+        get_run_response = {
+            "id": run_id,
+            "name": "Original Run",
+            "description": "Keep this description",
+            "refs": "REF-1",
+            "include_all": True,
+            "plan_id": None,
+            "config_ids": [],
         }
-        requests_mock.get(create_url(f"get_tests/{run_id}"), json=mocked_tests_response)
 
+        update_run_response = {"id": run_id, "name": run_name}
+
+        requests_mock.get(create_url(f"get_run/{run_id}"), json=get_run_response)
+        requests_mock.post(create_url(f"update_run/{run_id}"), json=update_run_response)
+
+        # Execute update_run with sentinel (...) for all clearable attributes
+        run_data, error = api_request_handler.update_run(run_id, run_name)
+
+        assert error == "", "No error should occur"
+
+        # Verify the payload preserves existing description
+        request_history = requests_mock.request_history
+        update_request = [r for r in request_history if "update_run" in r.url and r.method == "POST"][0]
+        payload = update_request.json()
+
+        assert payload["description"] == "Keep this description", "description should be preserved"
+        assert payload["refs"] == "REF-1", "refs should be preserved"
+
+    @pytest.mark.api_handler
+    def test_upload_attachments_413_error(self, api_request_handler: ApiRequestHandler, requests_mock, tmp_path):
+        """Test that 413 errors (file too large) are properly reported."""
         # Create a temporary test file
         test_file = tmp_path / "large_attachment.jpg"
         test_file.write_text("test content")
@@ -1141,10 +1377,10 @@ class TestApiRequestHandler:
 
         # Prepare test data
         report_results = [{"case_id": 100, "attachments": [str(test_file)]}]
-        results = [{"id": 2001, "test_id": 1001}]
+        case_id_to_result_id = {100: 2001}
 
         # Call upload_attachments
-        api_request_handler.upload_attachments(report_results, results, run_id)
+        api_request_handler.upload_attachments(report_results, case_id_to_result_id)
 
         # Verify the request was made (case-insensitive comparison)
         assert requests_mock.last_request.url.lower() == create_url("add_attachment_to_result/2001").lower()
@@ -1152,18 +1388,6 @@ class TestApiRequestHandler:
     @pytest.mark.api_handler
     def test_upload_attachments_success(self, api_request_handler: ApiRequestHandler, requests_mock, tmp_path):
         """Test that successful attachment uploads work correctly."""
-        run_id = 1
-
-        # Mock get_tests endpoint
-        mocked_tests_response = {
-            "offset": 0,
-            "limit": 250,
-            "size": 1,
-            "_links": {"next": None, "prev": None},
-            "tests": [{"id": 1001, "case_id": 100}],
-        }
-        requests_mock.get(create_url(f"get_tests/{run_id}"), json=mocked_tests_response)
-
         # Create a temporary test file
         test_file = tmp_path / "test_attachment.jpg"
         test_file.write_text("test content")
@@ -1173,10 +1397,10 @@ class TestApiRequestHandler:
 
         # Prepare test data
         report_results = [{"case_id": 100, "attachments": [str(test_file)]}]
-        results = [{"id": 2001, "test_id": 1001}]
+        case_id_to_result_id = {100: 2001}
 
         # Call upload_attachments
-        api_request_handler.upload_attachments(report_results, results, run_id)
+        api_request_handler.upload_attachments(report_results, case_id_to_result_id)
 
         # Verify the request was made (case-insensitive comparison)
         assert requests_mock.last_request.url.lower() == create_url("add_attachment_to_result/2001").lower()
@@ -1184,24 +1408,55 @@ class TestApiRequestHandler:
     @pytest.mark.api_handler
     def test_upload_attachments_file_not_found(self, api_request_handler: ApiRequestHandler, requests_mock):
         """Test that missing attachment files are properly reported."""
-        run_id = 1
-
-        # Mock get_tests endpoint
-        mocked_tests_response = {
-            "offset": 0,
-            "limit": 250,
-            "size": 1,
-            "_links": {"next": None, "prev": None},
-            "tests": [{"id": 1001, "case_id": 100}],
-        }
-        requests_mock.get(create_url(f"get_tests/{run_id}"), json=mocked_tests_response)
-
         # Prepare test data with non-existent file
         report_results = [{"case_id": 100, "attachments": ["/path/to/nonexistent/file.jpg"]}]
-        results = [{"id": 2001, "test_id": 1001}]
+        case_id_to_result_id = {100: 2001}
 
         # Call upload_attachments - should not raise exception
-        api_request_handler.upload_attachments(report_results, results, run_id)
+        api_request_handler.upload_attachments(report_results, case_id_to_result_id)
+
+    @pytest.mark.api_handler
+    def test_upload_attachments_empty_run_scenario(
+        self, api_request_handler: ApiRequestHandler, requests_mock, tmp_path
+    ):
+        """Test that attachments work correctly when results are added to an empty run.
+
+        This test covers the bug fix for issue where TRCLI failed to upload attachments
+        when using --run-id with an empty run (created via API with include_all: false
+        and no case_ids). The fix uses case_id to result_id mapping instead of fetching
+        tests from the run.
+        """
+        # Create test attachment files
+        attachment1 = tmp_path / "screenshot1.png"
+        attachment1.write_text("screenshot content 1")
+        attachment2 = tmp_path / "screenshot2.png"
+        attachment2.write_text("screenshot content 2")
+
+        # Mock successful attachment uploads
+        requests_mock.post(create_url("add_attachment_to_result/5001"), status_code=200, json={"attachment_id": 9001})
+        requests_mock.post(create_url("add_attachment_to_result/5002"), status_code=200, json={"attachment_id": 9002})
+
+        # Prepare test data - two cases with attachments
+        report_results = [
+            {"case_id": 100, "attachments": [str(attachment1)]},
+            {"case_id": 101, "attachments": [str(attachment2)]},
+        ]
+
+        # Case ID to result ID mapping (this is built from add_results_for_cases response)
+        case_id_to_result_id = {100: 5001, 101: 5002}
+
+        # Call upload_attachments
+        api_request_handler.upload_attachments(report_results, case_id_to_result_id)
+
+        # Verify both attachments were uploaded correctly
+        history = requests_mock.request_history
+        upload_requests = [req for req in history if "add_attachment_to_result" in req.url]
+        assert len(upload_requests) == 2, "Should have uploaded 2 attachments"
+
+        # Verify correct result IDs were used
+        urls = [req.url.lower() for req in upload_requests]
+        assert any("add_attachment_to_result/5001" in url for url in urls), "Should upload to result 5001"
+        assert any("add_attachment_to_result/5002" in url for url in urls), "Should upload to result 5002"
 
     @pytest.mark.api_handler
     def test_caching_reduces_api_calls(self, api_request_handler: ApiRequestHandler, requests_mock):