Karvio Roadmap

This roadmap describes the intended direction for Karvio. Specific delivery dates depend on project priorities, user feedback, and task readiness in GitHub.

GitHub issues: github.com/karahcheev/karvio/issues

Current Focus

  • Improve the daily QA workflow: faster test run creation, result updates, and progress analysis.
  • Expand Release Scope: stronger risk, coverage, and release readiness signals.
  • Improve CI, Jira, and notification integrations.
  • Strengthen production operations: observability, backup and restore guidance, background jobs, and troubleshooting.

Planned

Product and Release Management

  • More flexible test plan generation from products, components, risks, and milestones.
  • Expanded release readiness reports.
  • Better visualization for uncovered and high-risk components.
  • Additional component relationship types.

Test Management

  • Richer bulk actions for test cases and run items.
  • Better automated test import diagnostics for unmatched and ambiguous cases.
  • Expanded filters by owners, tags, components, and results.
  • Improved change history for test cases and execution results.

Integrations

  • More CI-friendly API workflows for automated result import.
  • Expanded Jira synchronization and issue status handling.
  • Additional notification events.
  • Better webhook channel support.

Reporting and Analytics

  • More exports and report views.
  • Trends for pass rate, defects, and test stability.
  • Performance trend dashboards.
  • Milestone and release scope quality summaries.

Administration and Operations

  • More detailed diagnostics for queues and background jobs.
  • Improved health checks.
  • Documented backup and restore procedures for multiple infrastructure setups.
  • Expanded retention settings.

Ideas Under Consideration

  • SSO/OIDC.
  • Fine-grained permissions beyond current project roles.
  • Test case import and export between projects.
  • Public read-only reports.
  • Additional performance adapters.
  • More built-in report templates.

How to Propose Changes

  1. Create a GitHub issue: github.com/karahcheev/karvio/issues/new.
  2. Describe the problem, target user, and expected workflow.
  3. Add sample data, screenshots, or API payloads when they help explain the scenario.
  4. For larger changes, propose an MVP and later phases.