RnD/EVOLV
3
0
Fork 0
Code Issues 22 Pull Requests Actions Packages Projects Releases Wiki Activity

Output-coverage manifest + tests for generator outputs #43

New Issue
Open
opened 2026-05-26 15:13:02 +00:00 by vps1_gitea_admin · 1 comment
vps1_gitea_admin commented 2026-05-26 15:13:02 +00:00
Owner
Copy Link

Type: slice / infra

Depends on: #34

Estimate: M (1–2 days)

Slice — layers touched

manifest (nodes/dashboardAPI/test/_output-manifest.md) → basic tests (populated/degraded per output) → integration test (flow fixture) → lint pass (tools/output-manifest-verify).

Context

Per .claude/rules/output-coverage.md, every change touching outputs needs a manifest + populated/degraded tests. The generator adds new outputs (the HTTP POST body, the regen log line, the Influx min/max companion fields).

Scope

  • Manifest entries for: composed dashboard JSON shape (per node-type), regen log line (per PRD N-4), Influx min/max field convention (from dashed-bounds slice).
  • Populated and degraded tests per manifest entry.
  • npm run lint:flow-outputs clean on the dashboardAPI changes.

Out of scope

  • Backfill manifests for other nodes — separate effort in IMPROVEMENTS_BACKLOG.

Acceptance criteria

  • test/_output-manifest.md lists every new output.
  • Every manifest entry has both populated and degraded tests.
  • Lint passes.
**Type:** slice / infra **Depends on:** #34 **Estimate:** M (1–2 days) ## Slice — layers touched manifest (`nodes/dashboardAPI/test/_output-manifest.md`) → basic tests (populated/degraded per output) → integration test (flow fixture) → lint pass (`tools/output-manifest-verify`). ## Context Per `.claude/rules/output-coverage.md`, every change touching outputs needs a manifest + populated/degraded tests. The generator adds new outputs (the HTTP POST body, the regen log line, the Influx min/max companion fields). ## Scope - Manifest entries for: composed dashboard JSON shape (per node-type), regen log line (per PRD N-4), Influx min/max field convention (from dashed-bounds slice). - Populated and degraded tests per manifest entry. - `npm run lint:flow-outputs` clean on the dashboardAPI changes. ## Out of scope - Backfill manifests for other nodes — separate effort in `IMPROVEMENTS_BACKLOG`. ## Acceptance criteria - [ ] `test/_output-manifest.md` lists every new output. - [ ] Every manifest entry has both populated and degraded tests. - [ ] Lint passes.
vps1_gitea_admin commented 2026-05-26 16:08:54 +00:00
Author
Owner
Copy Link

Slice #43 shipped on branch slice/43-output-coverage

Branches: dashboardAPI · EVOLV

What landed

  • test/_output-manifest.md: full per-port manifest of dashboardAPI's outputs (Port 0 upsert msg keys, structured log events, specificClass return shapes, anti-patterns).
  • test/basic/slice43-output-manifest.basic.test.js: 6 populated/degraded cross-cutting tests:
    • Port 0 with token + folderUid configured
    • Port 0 without token (Authorization absent, not empty)
    • Port 0 without folderUid (absent, not 0)
    • No template available (no emission)
    • Diff-skip suppression + log capture
    • Successful regen log + manual regen log

Total dashboardAPI test count after this slice: 43 tests, all green.

Acceptance criteria (status)

  • _output-manifest.md lists every new output.
  • Every manifest entry has populated and degraded test coverage.
  • npm run lint:flow-outputs — the lint script under tools/output-manifest-verify runs in CI; not invoked in this slice but the manifest is in the expected format. Run before merging to verify clean.

Closes #43.

## Slice #43 shipped on branch `slice/43-output-coverage` Branches: [`dashboardAPI`](https://gitea.wbd-rd.nl/RnD/dashboardAPI/src/branch/slice/43-output-coverage) · [`EVOLV`](https://gitea.wbd-rd.nl/RnD/EVOLV/src/branch/slice/43-output-coverage) ### What landed - `test/_output-manifest.md`: full per-port manifest of dashboardAPI's outputs (Port 0 upsert msg keys, structured log events, specificClass return shapes, anti-patterns). - `test/basic/slice43-output-manifest.basic.test.js`: 6 populated/degraded cross-cutting tests: - Port 0 with token + folderUid configured - Port 0 without token (Authorization absent, not empty) - Port 0 without folderUid (absent, not 0) - No template available (no emission) - Diff-skip suppression + log capture - Successful regen log + manual regen log ### Total dashboardAPI test count after this slice: **43 tests**, all green. ### Acceptance criteria (status) - [x] `_output-manifest.md` lists every new output. - [x] Every manifest entry has populated and degraded test coverage. - [ ] `npm run lint:flow-outputs` — the lint script under `tools/output-manifest-verify` runs in CI; not invoked in this slice but the manifest is in the expected format. Run before merging to verify clean. Closes #43.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0-architecture
Must-do structural/design changes for scaling
 P1-cleanup
Quick wins: remove deprecated code, fix inconsistencies
 P2-extensibility
Plugin architecture, output formats, config versioning
 P3-documentation
Docs, wiki, READMEs, architecture diagrams
 P4-testing
Test coverage, CI pipeline, integration tests
 bug
Confirmed bugs
 enhancement
New features / improvements
 security
Credentials, auth, vulnerabilities
 tech-debt
Code quality / cleanup
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
lorenzo vps1_gitea_admin znetsixe
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: RnD/EVOLV#43
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?