--- title: "Test Case Management Software for Agile Teams | Orangescrum" description: "Plan, run, and track testing in the same tool as your delivery. Test plans, suites, cases and steps, test runs with execution history." canonical: https://www.orangescrum.com/test-case-management --- # Test Case Management Software for Agile Teams | Orangescrum > For the complete documentation index, see [llms.txt](https://www.orangescrum.com/llms.txt). [Home](/) / [Features](/features) / Test Case Management Test Case Management # Test Case Management, _Inside Your Project Tool_ Stop running QA in a spreadsheet. Write test cases, group them into suites and plans, run them, and link every defect back to the task and sprint it came from. Available in[Cloud](/pricing "Cloud - included")[Self-Hosted](/self-hosted "Self-Hosted - included")Open Source [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=test-case-management)[Book a Demo](https://calendly.com/orangescrum) Free forever plan · No credit card required · Set up in minutes ## What is test case management? Test case management is how a team writes, organises, runs, and tracks its tests, and connects failures back to the work that caused them. Orangescrum keeps test plans, suites, cases, runs, and defects in the same place as your projects and sprints, so quality is tracked alongside delivery rather than in a separate tool nobody in the project can see. The problem ## Why QA _drifts away from delivery_ Tests live in spreadsheets Test cases sit in a file with no history and no link to the work. ✓ Structured cases and suites stored with the project. Defects lose their context A bug is raised with no link to the test or the task that produced it. ✓ Defects trace back to the test case, task, and sprint. Nobody knows what was tested There is no record of which cases ran, when, or with what result. ✓ Test runs keep a full execution history. What you get ## A full QA workflow, _not a bolt on_ Grouped the way testing is done: what the library holds, what a case carries, how a run is executed, what it traces to, and how results get in and out. 01Library - ### Suites, plans, and strategies Group testing into suites, assemble suites into plans, and record the strategy behind each one. - ### Scenarios and cases Write scenarios that describe what needs covering, then the individual cases that cover them. - ### A shared step library Steps are stored on their own and attached to as many cases as need them, so you write a step once. - ### Test environments Record the environments you test against and attach one to each run. - ### Service level records Keep your own service level definitions and map them onto the defects testing raises. - ### Attachments at every level Suites, plans, strategies, scenarios, cases, and defects all take file attachments. 02Test case - ### Preconditions, steps, and expected result Each case holds a precondition, a post condition, its steps, and the result you expect to see. - ### Type, priority, and severity Classify the case so a run can be narrowed down to what actually matters. - ### Behaviour and automation status Record the behaviour a case verifies and whether it is run by hand or by a machine. - ### Versions and effective dates A case carries a version and the dates it applies between, so retired cases stop being run by mistake. - ### A named approver Cases carry an approver, so somebody signs off that the test itself is correct. - ### Comments Discuss a case on the case itself rather than in a separate thread nobody can find. - ### A checklist on creation In the Cloud edition a checklist template can be attached automatically the moment a case is created. 03Test runs - ### Build a run from a plan or a project Pick cases from a test plan, or straight from the project, and turn them into a run. - ### Passed, failed, blocked, or skipped Record the outcome of each case in the run with one of four clear results. - ### A result on every step Mark individual steps as well as the case, and type in the actual result you saw. - ### Assign the run and set the environment Every run has an owner and an environment, so a result still means something months later. - ### Complete a run, or run it again Close a run when it is finished, and start it again for the next cycle. - ### Raise a defect from the run A failure turns straight into a defect without leaving the run you are executing. - ### Mark hundreds of results at once The Self-Hosted edition sets the same result across up to five hundred items in a single action. - ### Rerun only what failed The Self-Hosted edition builds a fresh run from the failed and blocked items of the last one. - ### Six result states and full history The Self-Hosted edition adds untested and retest to the four standard results, and keeps every submission. 04Traceability - ### Cases link to epics, features, and stories A case points at the work it verifies, so coverage is measured against real delivery items. - ### A traceability matrix See your cases laid out by epic and feature, with priority, severity, and automation status on each. - ### Coverage and health The Self-Hosted edition shows what is traced, what has been executed, and whether each work item is passing. - ### Defects trace back to case and step Every defect raised from testing keeps the case, and where relevant the step, that produced it. - ### Link a defect to a task Search your tasks from inside the defect and link the ones the fix belongs to. 05Defects - ### Your own severity, priority, type, and status The defect lists are data you control rather than a fixed vocabulary you have to live with. - ### Expected start and end times Map a service level onto a defect so you can tell when a fix is running late. - ### An automatic defect number Defects raised from testing are numbered automatically with their own prefix. - ### Story points and estimates Defects carry a story point and an estimate, so they can be planned like any other backlog item. - ### A configurable defect workflow The Self-Hosted edition lets you set the statuses, the allowed moves, the resolutions, and a target time per severity. 06Import and export - ### A four step import Upload a file, map your columns, preview the result, then confirm, with a summary at the end. - ### Choose what you export Tick the columns you want and send the case list out as a spreadsheet file. - ### Import defects as well The Self-Hosted edition imports defects too, and resolves projects and work items by name. - ### Draft cases in a grid The Self-Hosted edition gives you a spreadsheet style sheet for drafting cases before they become real. 07Automation - ### Post results from your pipeline The Self-Hosted edition accepts JUnit XML or JSON from a build, matched to cases by an automation reference. - ### A REST API for cases, runs, and defects The Self-Hosted edition exposes token authenticated endpoints so other tools can read and write. - ### Rotate the token The automation token can be rotated from settings without touching anything else. 08Reporting and access - ### A testing dashboard See status distribution, coverage, and defect counts for the project you are looking at. - ### A test case report Pull a report across your cases to see how the library itself is shaped. - ### Export the coverage view The Self-Hosted edition exports traceability to a spreadsheet for people who never open the tool. - ### A permission for every tab The Self-Hosted edition adds a module gate plus a separate view permission for each tab inside it. - ### Seventeen permissions in the newer module Create, edit, delete, execute, plan, import, export, and administration are all separate rights. How it works ## How a test cycle _runs_ 1 Write the cases Create test cases with steps and expected results, grouped into suites. 2 Build the plan Assemble the suites that need to run for this release or sprint. 3 Execute Run the plan, record results per case and per step, and attach evidence where needed. 4 Fix and retest Failed cases raise defects that link back to the task, and the case is rerun once fixed. Who it's for ## For teams that _have to prove quality_ Software and QA teams Teams running structured testing alongside their sprints, with traceability from case to defect. [Learn more →](/solutions/it-project-management-software) Regulated delivery Organisations that must evidence what was tested, by whom, and with what result. [Learn more →](/self-hosted) Agencies Teams proving quality to a client before a release goes out. [Learn more →](/agency-project-management) Availability ## Which edition includes _what_ Orangescrum runs as managed cloud, self-hosted on your own servers, or as the open-source Community Edition. Here is exactly what each one includes. Test Case Management is on the Premium plan and in Self-Hosted. The rows below show where the deeper parts sit. | Capability | CloudManaged SaaS | Self-HostedOn-premise / private cloud | Open SourceCommunity Edition | | Suites, plans, strategies, and scenarios | Premium | ✓ | ✗ | | Test cases with preconditions and expected results | Premium | ✓ | ✗ | | A shared, reusable step library | Premium | ✓ | ✗ | | Test environments and service level records | Premium | ✓ | ✗ | | Test runs with case and step results | Premium | ✓ | ✗ | | Raise a defect from a failed run | Premium | ✓ | ✗ | | Traceability matrix by epic and feature | Premium | ✓ | ✗ | | Approver on cases and steps | Premium | ✓ | ✗ | | CSV import wizard and column picked export | Premium | ✓ | ✗ | | Checklist attached when a case is created | Premium | ✗ | ✗ | | A view permission per module tab | ✗ | ✓ | ✗ | | Board view, bulk toolbars, and custom fields | ✗ | ✓ | ✗ | | Six result states and rerun failed only | ✗ | ✓ | ✗ | | Configurable defect workflow and severity targets | ✗ | ✓ | ✗ | | Coverage report and traceability export | ✗ | ✓ | ✗ | | CI automation results and a public REST API | ✗ | ✓ | ✗ | | Bug and issue tracking | ✓ | ✓ | ✗ | Frequently asked questions ## Test Case Management _FAQ_ ### Does Orangescrum have test case management? Yes. Orangescrum includes test plans, test suites, test strategies, scenarios, test cases with steps, test runs with results per case and per step, and defect tracking, all linked back to the tasks and sprints the tests relate to. ### Which edition and plan includes it? Test Case Manager is part of the Premium plan in the Cloud edition, and is included in the Self-Hosted edition. The self-hosted edition also carries a newer test module that adds boards, bulk actions, custom fields, coverage reporting, and automation ingest. ### How is a test case organised? A test case has a precondition, steps, an expected result, and a post condition. Cases are grouped into suites, and suites are grouped into test plans, so each release has a defined scope of testing. ### Can I reuse a test step across cases? Yes. Steps are stored on their own rather than inside one case, so the same step can be attached to as many cases as need it and you only write it once. ### Can I raise a bug from a failed test? Yes. A failed case, or a single failed step, can raise a defect directly, carrying severity, priority, and evidence, and the defect stays linked to the case and the task. ### Does it keep a history of test runs? Yes. Every run is recorded with the environment and the assignee, so you can see whether a failure is new or has been happening for several cycles. ### Can I import and export test cases? Yes. There is a four step import that lets you upload a file, map your columns, preview the result, and confirm it. Exports let you tick which columns you want. The self-hosted edition also imports defects. ### Can automated tests report their results? Yes, in the Self-Hosted edition. Your build can post JUnit XML or JSON to a token authenticated endpoint, and results are matched to cases by an automation reference. ### Is test management in the open source edition? No. The Community Edition covers core project and task management. Test Case Management is available in the Cloud Premium plan and the Self-Hosted edition. ## Track quality alongside delivery Test Case Management is included in the Premium plan and the Self-Hosted edition. [Start Free Trial →](/sign-up?utm_source=website&utm_medium=feature&utm_content=test-case-management_cta)[Book a Demo](https://calendly.com/orangescrum) ## Every part of test case management [Test caseWrite, version, and reuse cases](/test-case-management/test-case)[Test planScope, schedule, and sign off a cycle](/test-case-management/test-plan)[Test scenarioGroup cases into real user journeys](/test-case-management/test-scenario)[Test strategySet the approach before the cycle](/test-case-management/test-strategy)[Test suitesBundle cases into runnable suites](/test-case-management/test-suites)[Defect trackingRaise defects straight from a run](/test-case-management/defect-tracking) ## Related capabilities [Bug and issue trackingTrack defects end to end](/bug-and-issue-tracking)[Test planPlan a release test cycle](/test-case-management/test-plan)[Defect trackingManage defects with evidence](/test-case-management/defect-tracking)[Test caseManage, execute, and track test cases](/test-case-management/test-case)[Test scenarioHigh-level scenarios for full functional coverage](/test-case-management/test-scenario)[Test strategyAlign test strategy across teams, sprints, and releases](/test-case-management/test-strategy)[Test suitesGroup test cases into reusable suites](/test-case-management/test-suites)[Jenkins and CI/CDPipeline status on work items](/integrations/jenkins)