TESTHARNESS by SPNORTH
A toolkit for E2E fleets: journey library, selector guide, flaky anti-patterns.
Problem
Test suites rust: selectors break, flakiness frustrates, nobody maintains them.
Intended users
Product teams with Playwright/Cypress suites.
Documented capabilities
- Journey library
- Selector isolation patterns
- Flaky-test strategy
- CI report page
- Maintenance cadence guide
Governance and human boundary
Agents propose; named humans remain responsible for architecture, approvals and regulatory interpretation.
Evidence Flow
Synthetic exampleSynthetic example: illustrated demo with sample data; no customer system and no live telemetry.
- Source
Approved source with version and rights (sample dataset)
- Requirement/Control
Derived requirement with control target and owner
- Human Review
Named approver reviews context, conflicts and evidence
- Test/Evidence
Evaluation against ground truth; reproducible result
- Approval
Signed decision with date and evidence index
Limits and assumptions
- No automation without a named maintainer
- Status: proposed
Related services
FAQ
Is this available in production?
Status: proposed. SPNORTH does not guarantee compliance, certification, regulatory approval or error-free AI output.
How does this relate to the services?
Relevant services are linked below; entry happens through the documented offers.