A complete test management workspace built into Orangescrum. Define test strategies and plans, organise suites and scenarios, author cases with steps and dependencies, schedule runs across environments and test data sets, capture defects with SLA enforcement, ingest CI/CD build and job results, and trace every requirement to every test to every defect — bidirectionally.
- Rating
- 4.7
- Installs
- 10.2K
- Support
- Vendor Supported
- Trust
- Self-Hosted
354 reviews
Active deployments
Priority response
Your infra, your data
Screenshots
Key Features
Test Strategy & Plans
Define release- or programme-level test strategies, then break them into test plans bound to projects, scope, and timelines. Approvers and reviewers wired in.
Test Suites & Scenarios
Organise cases into reusable suites and end-to-end scenarios. Suites cluster by feature, scenarios chain cases into user journeys.
Step-Level Authoring
Author cases with structured steps, expected results, preconditions, postconditions, attachments, and per-step comments. Readable for humans, parseable for automation.
Step Conditions & Dependencies
Conditional steps run only when prior steps pass certain values. Step and case dependencies make complex regression flows declarative, not procedural.
Test Runs
Schedule runs against test cycles, assign testers, track pass / fail / blocked / skipped status per step, and capture screenshots and logs as evidence inline.
Test Environments
Define environments (Dev, Staging, UAT, Prod, custom) with their own URL, credentials, and config. Runs are scoped to an environment so flaky vs real defects are obvious.
Test Data Management
Parameterise cases with reusable test data sets. Data-driven runs execute the same case against many input rows without duplicating authoring.
Defect Tracking
Failed steps spawn defects automatically with the failing step, expected vs actual output, screenshots, and CI/CD logs already attached. Defects link bidirectionally to cases and runs.
Configurable SLAs
Define SLA mappings per priority, severity, project, or company. Stale defects auto-escalate via email and re-route through approver chains before they slip the release.
CI/CD Integrations
Ingest builds and jobs from Jenkins, GitHub Actions, GitLab CI, CircleCI, and any webhook-based system. Failed pipelines surface as failed runs in real time.
Execution History & Regression Compare
Every run, every step, every comment — preserved. Compare any cycle against any previous one to spot regressions and track flake-rate per case.
Approver Mapping
Bind approvers to test cases and individual steps. Production-bound runs gate on approver sign-off — accountability with evidence trail.
Notes, Attachments & Comments
Per-step comments, per-case notes, per-defect evidence. Test management attachments versioned alongside the work they belong to.
Full Traceability
Requirements ⇄ test plans ⇄ test cases ⇄ test runs ⇄ defects, end-to-end. Coverage gaps stop being hypothetical and start being visible.
CSV Import
Bulk import existing test cases from CSV with templates for Zephyr, TestRail, and Xray. Migration takes minutes, not weeks.
Granular RBAC
Role-based permissions for QA Lead, Tester, Developer, Reviewer, and Viewer with case-level, step-level, and run-level access controls.
About this plugin
Why Test Case Management for Orangescrum?
QA tools that live outside your project tracker create a translation tax — every defect re-typed, every requirement re-linked. This plugin removes the tax. Test strategies, plans, suites, scenarios, cases, runs, environments, test data, defects, SLAs, and CI/CD signal all live under the same project tree as the work that ships them.
Hierarchy that mirrors how QA actually works
Strategy at the top (release goals, scope, success criteria). Plans underneath (binding to projects, sprints, or milestones). Suites cluster cases by feature. Scenarios chain cases into user journeys. Cases hold steps. Steps hold conditions, dependencies, expected results. Every level is first-class — query it, report on it, restrict access to it.
Runs across environments with real test data
Schedule runs against any defined environment (Dev, Staging, UAT, Prod, custom — with URLs, credentials, config). Parameterise cases with reusable test data sets so a single case executes against ten input rows without duplicating authoring. Failed steps capture screenshots and logs inline as defect evidence.
Defects with SLAs that finish
Failed steps spawn defects automatically — the failing step, expected vs actual output, screenshot, CI/CD log, and case context all stitched together. Configurable SLA mappings (per priority, severity, project, or company) escalate stale defects before they slip the release. Approver chains gate fixes back to QA.
Built for QA teams who ship fast
CI/CD integrations (Jenkins, GitHub Actions, GitLab CI, CircleCI, any webhook-based system) make automated test runs surface as Orangescrum cycles — manual and automated coverage live in one view. Execution history makes regression detection a UI lookup, not a forensic exercise. Flake-rate per case is a column, not a research project.
Traceability that audits love
Requirements link to test plans, plans to suites, suites to cases, cases to runs, runs to defects — bidirectionally, end-to-end. ISO 25010 and IEEE 829 evidence packs export with a click. Coverage gaps stop being hypothetical.
What's included
- Test strategies, test plans, test suites, test scenarios, and test cases
- Step-level authoring with expected results, preconditions, and postconditions
- Step conditions (run only when prior step passes condition X)
- Step dependencies and case dependencies
- Test runs scheduled per cycle, per environment, per tester
- Test environments with URL, credentials, and configuration
- Test data sets with parameterised data-driven case execution
- Test results and execution history per run
- Defect tracking with auto-creation from failed steps
- Defect evidence (screenshots, logs, attachments)
- Configurable SLA mappings (per priority, severity, project, company)
- Auto-escalation of stale defects
- CI/CD build, job, and integration ingestion
- Approver mapping for test cases and individual steps
- Test management notes, attachments, and per-step comments
- Test case ↔ project mapping with bidirectional links
- Resource mapping for steps, cases, and defects
- Bulk CSV import with templates for Zephyr, TestRail, and Xray
- Regression-comparison view across any two cycles
- Role-based access control with QA Lead / Tester / Developer / Reviewer / Viewer roles
- Full traceability matrix: Requirements → Plans → Suites → Cases → Runs → Defects
- Multi-tenant company-scoped data isolation
Compatibility
Compatible with Orangescrum Self-Hosted Core, Business, and Enterprise editions running PHP 8.2+, CakePHP 4.6+, and PostgreSQL 13+. CI/CD integration via webhooks supports Jenkins, GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, Bitbucket Pipelines, and any system that can POST a payload. Multi-tenant aware — every test artefact is company-scoped.
Installation
A self-hosted install takes a few minutes. Buy the add-on, drop the plugin into your plugins/ directory, run the migrations, and you're live.
- 1
Buy the add-on
Purchase the Test Case Management add-on from /self-hosted/pricing — $499/year per company, payable annually.
- 2
Drop the plugin into your install
Copy the TestCaseManager/ folder into plugins/ on your self-hosted Orangescrum server.
- 3
Register the plugin
Register `TestCaseManager` in src/Application.php with `routes => true, bootstrap => true`.
- 4
Run the database migrations
Run `bin/cake migrations migrate --plugin TestCaseManager` to create the strategy, plan, suite, scenario, case, run, defect, SLA, environment, test-data, and CI/CD tables.
- 5
Define your first test environments and SLAs
Configure environments (Dev, Staging, UAT, Prod). Set SLA mappings per priority and severity. Wire up CI/CD webhooks from Jenkins, GitHub Actions, or GitLab CI.
- 6
Import or author your first cases
Use Test Case Import to bring CSV exports from Zephyr, TestRail, or Xray — or author cases from scratch with the visual step builder.
- 7
Run your first cycle
Group cases into a cycle, assign testers, schedule a run against an environment + test-data combination, and track results live.
Reviews
Defect-from-failed-step automation saved my team hours a week. SLA escalations mean nothing rots in the backlog.
We finally have one tool that ties requirements, manual tests, automated tests, and defects together. Coverage gaps stopped being a guessing game.
CI/CD ingestion via webhooks just works. Looking forward to native Jenkins plugin support in a future release.
Frequently Asked Questions
What's the hierarchy — strategies, plans, suites, cases?
▾
Strategies sit at the top (release-level goals, scope, success criteria). Plans break strategies into project- or sprint-bound chunks. Suites cluster cases by feature. Scenarios chain cases into end-to-end user journeys. Cases hold steps. Steps hold conditions, expected results, and dependencies. Every level is queryable, reportable, and access-controllable.
Can I import existing test cases from another tool?
▾
Yes. CSV import is supported for cases, suites, plans, and runs. We publish ready-made templates for Zephyr, TestRail, Xray, and qTest. The CsvService handles mapping, validation, and rollback on partial failures.
Does it run automated tests directly?
▾
It doesn't execute test scripts itself — your CI/CD does that. The plugin ingests build and job results via webhook from Jenkins, GitHub Actions, GitLab CI, CircleCI, Azure Pipelines, etc. Manual and automated coverage live in one place.
What happens when a test step fails?
▾
A defect is created automatically with the failing step, the expected vs actual output, attached screenshot or log, and full case + run + environment context. The defect inherits the cycle's project, links bidirectionally back to the case, and routes through the configured SLA chain.
How do test environments and test data work together?
▾
Define environments (Dev / Staging / UAT / Prod / custom) with URLs and credentials. Define test data sets — rows of input parameters. A single test case can run against many environments × many data rows without duplicating authoring. Results are tagged so you can compare environments or isolate flaky data.
Can I customise SLA timers per defect priority?
▾
Yes. SLA mappings are fully configurable per priority, severity, project, or company. Mappings define warning thresholds, breach thresholds, and the escalation chain for each.
How does approver mapping work?
▾
Bind approvers to test cases or individual steps. Production-bound runs gate on approver sign-off before they're allowed to execute, and defects can be configured to require approver acknowledgement before being closed.
Is there a regression-comparison view?
▾
Yes. Pick any two cycles and the plugin surfaces newly-failing cases, newly-passing cases, and flake-candidates. Trend charts show flake-rate per case over time so you can fix the right things first.
Ready to deploy Test Case Management on your own infrastructure?
Talk to our team about Orangescrum Self-Hosted Enterprise — your data, your servers, full control.