# Telryn

> Maintained SharePoint test scenarios for existing connectors and tests, in development.

Telryn is building a maintained SharePoint test environment. The aim is to reduce mock upkeep and repeated provider investigation. Engineers and coding agents would use the customer's existing connector and application checks against selected responses and state transitions. The website invites teams to test one recurring SharePoint scenario together; this starts a scoping conversation, not agreed access, delivery or commercial terms.

## Preview scope and intended offer

A bounded SharePoint developer preview has been produced: version 0.1.0-preview.1, a Linux AMD64 container and connection CLI for initial document fetch, additions and same-ID content updates through Microsoft Graph polling delta. Its reference-client checks do not establish real-tenant conformance or compatibility with every customer connector. Do not infer current public download availability from this description.

Maintained coverage remains in development. Expired delta-link recovery, permission changes, throttling and other failure cases need separate scope and evidence. They are not established preview coverage. Additional providers have not been selected. The intended users are document-connector teams at software vendors and internal platform teams, including search, security and classification, knowledge products and AI assistants.

## Planned responsibilities

Telryn would maintain versioned scenarios with applicable conditions and known limits. The planned validation process compares selected behavior with provider documentation and authorized SharePoint tenant runs. Real-tenant conformance remains unverified. Telryn would investigate reported mismatches and publish reviewed corrections, recording sources, dates, changed behavior and unresolved gaps. An investigation may find that no change or further investigation is warranted.

Customers configure approved test endpoints and test authentication, supply minimized fixtures, run the connector and reset application state. Customers retain application assertions, fixes and release decisions. Engineers or coding agents can run the same checks; no special agent framework is implied. Compatibility and setup effort must be measured for the connector.

## Evidence and limits

Simulator behavior, real-provider fidelity and application correctness are separate checks. The preview does not supply the full planned maintenance or coverage-reporting service. It would not judge application correctness or approve releases. Customers would review and acquire updates explicitly; a pinned scenario cannot certify current provider behavior. A passing application run covers recorded conditions, not all configurations or every cause of a historical incident. Existing mocks, simulators and sandboxes may already be sufficient. Maintenance savings and recurring demand remain unproven.

The former integration-change and release-control offers are historical. Older offer routes and download URLs lead to the current approach or brief.

## Pages

- Homepage and scenario invitation: https://telryn.com/
- Approach, preview scope and maintenance plan: https://telryn.com/approach/
- Printable brief: https://telryn.com/assets/telryn-early-access-brief.pdf
- Guide library: https://telryn.com/guides/

The featured reading path is:

1. Mocks, Provider Sandboxes or Maintained Test Environments?: https://telryn.com/guides/mocks-sandboxes-maintained-environments/
2. How to Reproduce an Integration Failure in CI: https://telryn.com/guides/reproduce-integration-failure/
3. How to Test Pagination, Rate Limits and Interrupted Syncs: https://telryn.com/guides/test-pagination-rate-limits-interrupted-syncs/
4. How to Keep Integration Tests Trustworthy as Providers Change: https://telryn.com/guides/maintain-integration-checks/

Further reading covers provider changes and migrations. These are engineering guides, not Telryn migration-service offers:

- What an API Change Can Break in Your Integration: https://telryn.com/guides/api-change-impact/
- How to Verify an API Migration Across Customer Configurations: https://telryn.com/guides/verify-integration-migration/

Guides contain hypothetical examples, sources and limits. General teaching about permissions, retries, rate limits and other providers does not imply delivered Telryn coverage. The scenarios and examples are not customer results.