Add unit tests for document template rendering service #74

New issue

Closed

opened 2026-04-08 17:04:14 -04:00 by pook · 1 comment

pook commented

2026-04-08 17:04:14 -04:00

Owner

Stale issue #38 (full test suite) is too broad. This task covers only the core template rendering logic.

Implement:

Create test file for the document generation/template service
Test each document type template renders valid HTML output
Test that required input fields (company name, jurisdiction, etc.) are interpolated correctly
Test that missing required fields throw a validation error
Test that HTML output contains no raw template placeholders

Acceptance criteria:

At least one test per supported document type (privacy policy, ToS, cookie policy)
Tests for valid input produce HTML with interpolated values
Tests for missing required fields produce clear error
No placeholder strings (e.g. {{company_name}}) remain in output
Tests run with npm test and pass

Generated by CEO Planner (priority: 3)

Stale issue #38 (full test suite) is too broad. This task covers only the core template rendering logic. Implement: 1. Create test file for the document generation/template service 2. Test each document type template renders valid HTML output 3. Test that required input fields (company name, jurisdiction, etc.) are interpolated correctly 4. Test that missing required fields throw a validation error 5. Test that HTML output contains no raw template placeholders Acceptance criteria: - At least one test per supported document type (privacy policy, ToS, cookie policy) - Tests for valid input produce HTML with interpolated values - Tests for missing required fields produce clear error - No placeholder strings (e.g. {{company_name}}) remain in output - Tests run with npm test and pass --- *Generated by CEO Planner (priority: 3)*

pook added the

agent-task

label

2026-04-08 17:04:14 -04:00

pook commented

2026-04-10 14:48:30 -04:00

Author

Owner

Bulk-closed 2026-04-10 during pipeline triage.

Context: CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch agent/dispatch/* because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key.

What to do next:

Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge
CEO should halt new task creation until open PRs drop below 10
Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks)

This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

Bulk-closed 2026-04-10 during pipeline triage. **Context:** CEO agent had created 100 open agent-task issues against compliancebot, largely duplicates of each other and of the 50 currently-open PRs. Root cause traced to a git-push race in agent-worker executor (dispatch jobs collided on branch `agent/dispatch/*` because jobId prefix truncated to literal "dispatch"). Fix deployed: runId is now threaded from Paperclip shim through /dispatch → TaskJob → executor, and branches are keyed on a 12-char unique run key. **What to do next:** 1. Triage the 50 open PRs at https://192.168.183.110:3000/pook/compliancebot/pulls — many are ready to merge 2. CEO should halt new task creation until open PRs drop below 10 3. Surviving kept issues: #313, #314, #315, #341, #342, #350, #351, #352 (PR review/merge tasks) This issue was superseded, not abandoned. Reopen if still relevant after PR triage.

pook closed this issue

2026-04-10 14:48:30 -04:00

No labels

agent-task

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

pook/compliancebot#74

No description provided.

Rows
Columns