Feature Summary
New integrationTests/components/ directory. Single node: deploy component from GitHub, seed data, hit endpoints, assert responses. Runs on PR + merge to main. Covers the functional logic layer for all five components:
Problem This Solves
Component regressions are currently caught through manual QA. These tests automate that coverage so breakages in core Harper that affect components are caught in CI before they reach production.
Proposed Solution
One test file per component in integrationTests/components/. Each test uses harperLifecycle.ts to start a local harper instance, deploys the component via deploy_component , polls until ready, runs functional assertions against the HTTP API.
Priority/Impact
High - critical for user success
Feature Summary
New integrationTests/components/ directory. Single node: deploy component from GitHub, seed data, hit endpoints, assert responses. Runs on PR + merge to main. Covers the functional logic layer for all five components:
Problem This Solves
Component regressions are currently caught through manual QA. These tests automate that coverage so breakages in core Harper that affect components are caught in CI before they reach production.
Proposed Solution
One test file per component in
integrationTests/components/. Each test usesharperLifecycle.tsto start a local harper instance, deploys the component viadeploy_component, polls until ready, runs functional assertions against the HTTP API.Priority/Impact
High - critical for user success