Roadmap

Current Observer roadmap themes and target windows

Observer Roadmap

This page captures the current product direction for Observer. Targets are approximate and may shift as implementation details firm up.

Status Legend

  • Planned
  • In Progress
  • Blocked
  • Released

Now

ItemTargetStatusNotes
Pytest supportQ3 2026PlannedPrioritize parity with the existing Playwright reporter flow before expanding framework coverage.

Next

ItemTargetStatusNotes
MCP ServerQ3 2026PlannedFocus on a minimal, stable interface that can expose Observer data and actions safely.
Manager ViewQ4 2026PlannedTailor the experience for higher-level run summaries and team-level reporting.
JUnit 5 supportQ4 2026PlannedAlign the reporter model with JUnit 5 lifecycle events and metadata.
GitHub Actions integrationQ4 2026PlannedKeep setup lightweight so it is easy to adopt in existing CI workflows.

Later

ItemNotes
Executive Summary ViewHigh-level reporting for stakeholders
OpenTelemetry integrationFuture observability export path
JUnit XML importerBroader test result ingestion support
.NET ecosystemPotential new reporter surface
Prometheus / GrafanaMetrics export and dashboarding
Datadog integrationThird-party observability compatibility
Slack integrationAlerting and notifications
CypressAdditional test framework support
AI-assisted failure clusteringFailure root-cause inference
AI-assisted test health assessmentAnalyze tests in detail to produce optimization an improvement suggestions
Duration-based shard balancingTS Playwright-specific: receive an input of tests that are intended to be run and a desired number of shards, return shard test files balanced by execution time and not count
CI/CD cost optimizationProvide recommendations on CI/CD configuration to reduce execution time and save on infra costs

Cross-Cutting Themes

  • Reliability and correctness
  • Developer experience
  • Deployment and operations
  • Performance and scale
  • Security and hardening

Dependencies and Risks

  • Dependency: External reporter and framework support maturity

    • Impact: May affect target dates for new integrations
    • Mitigation: Keep roadmap items modular and independently shippable
  • Risk: Scope growth in cross-framework support

    • Impact: Can delay core Observer improvements
    • Mitigation: Prioritize the smallest useful integration slice first