Rockachopa/Timmy-time-dashboard
1
0
Fork 2
Code Issues 7 Pull Requests Actions Packages Projects Releases Wiki Activity

[Quality] Add Mock Integration Tests Emulating Gitea API Responses for Loop Scripts #1429

New Issue
Closed
opened 2026-03-24 13:04:47 +00:00 by Timmy · 1 comment
Timmy commented 2026-03-24 13:04:47 +00:00
Owner
Copy Link

Context: Shell scripts manipulating API paths currently possess zero formal testing.

Acceptance Criteria:

  • Develop Python mock boundaries executing .sh flows within temporary subshells to assert logic coverage.
  • Eliminate 'push-and-pray' architectural deployment.
**Context:** Shell scripts manipulating API paths currently possess zero formal testing. **Acceptance Criteria:** - Develop Python mock boundaries executing `.sh` flows within temporary subshells to assert logic coverage. - Eliminate 'push-and-pray' architectural deployment.
Timmy commented 2026-03-24 13:21:46 +00:00
Author
Owner
Copy Link

Implementation Instructions

Kimi, please implement mock integration tests for our shell scripts that manipulate Gitea API paths.

Step-by-step approach:

  1. Create tests/integration/test_loop_scripts.py
  2. Use unittest.mock to mock HTTP responses from Gitea API
  3. Focus on these critical scripts:
    • agent-dispatch.sh
    • hermes-claim.sh
    • kimi-loop.sh

Key test scenarios:

  • API success responses (200)
  • API error responses (401, 404, 500)
  • Network timeouts
  • Malformed JSON responses

Testing pattern:

with patch("requests.get") as mock_get:
    mock_get.return_value = Mock(status_code=200, json=lambda: {...})
    result = subprocess.run(["./agent-dispatch.sh", "arg"], capture_output=True)
    assert result.returncode == 0

Acceptance criteria:

  • Tests run with tox -e integration
  • Cover happy path and error scenarios
  • Use temporary directories for any file operations
  • Mock all external API calls
## Implementation Instructions Kimi, please implement mock integration tests for our shell scripts that manipulate Gitea API paths. **Step-by-step approach:** 1. Create `tests/integration/test_loop_scripts.py` 2. Use `unittest.mock` to mock HTTP responses from Gitea API 3. Focus on these critical scripts: - `agent-dispatch.sh` - `hermes-claim.sh` - `kimi-loop.sh` **Key test scenarios:** - API success responses (200) - API error responses (401, 404, 500) - Network timeouts - Malformed JSON responses **Testing pattern:** ```python with patch("requests.get") as mock_get: mock_get.return_value = Mock(status_code=200, json=lambda: {...}) result = subprocess.run(["./agent-dispatch.sh", "arg"], capture_output=True) assert result.returncode == 0 ``` **Acceptance criteria:** - Tests run with `tox -e integration` - Cover happy path and error scenarios - Use temporary directories for any file operations - Mock all external API calls
kimi was assigned by Timmy 2026-03-24 13:21:51 +00:00
kimi was unassigned by Timmy 2026-03-24 19:32:12 +00:00
Timmy closed this issue 2026-03-24 21:54:04 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
222-epic
Workshop: Timmy as Presence (Epic #222)
 actionable
Has a concrete code/config task extracted
 assigned-claude
Issue currently assigned to Claude agent — do not assign to another agent
 assigned-gemini
Issue currently assigned to Gemini agent — do not assign to another agent
 assigned-groq
assigned-kimi
Issue currently assigned to Kimi agent — do not assign to another agent
 assigned-manus
Issue currently assigned to Manus agent — do not assign to another agent
 claude-ready
consolidation
Part of a consolidation epic
 deprioritized
Keep open but not blocking P0 work
 deprioritized
Keep open but not blocking P0 work
 duplicate
Duplicate of another issue
 gemini-review
Auto-generated by Gemini, needs relevance review
 groq-ready
harness
Core product: agent framework, heartbeat, inference, memory
 heartbeat
Harness: Agent heartbeat loop
 inference
Harness: Inference and model routing
 infrastructure
Supporting stage: dashboard, CI/CD, deployment, DNS
 kimi-ready
Scoped and ready for Kimi to pick up
 memory-session
Harness: Memory and session crystallization
 morrowind
Harness: Morrowind embodiment
 needs-design
Needs architectural design before implementation
 needs-extraction
Philosophy with unextracted engineering work
 p0-critical
Priority 0: Must fix now
 p1-important
Priority 1: Important, next sprint
 p2-backlog
Priority 2: Backlog, do when time permits
 philosophy
Philosophical foundation — informs architecture decisions
 rejected-direction
Closed: rejected or superseded direction
 seed:know-purpose
Three Seeds: KNOW YOUR PURPOSE
 seed:serve-real
Three Seeds: SERVE THE REAL
 seed:tell-truth
Three Seeds: TELL THE TRUTH
 sovereignty
Harness: Sovereignty stack
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Timmy claude grok kimi manus perplexity Rockachopa
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Rockachopa/Timmy-time-dashboard#1429
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?