[{"data":1,"prerenderedAt":52},["ShallowReactive",2],{"wiki-test-management-what-is-a-test-management-system-en":3},{"meta":4,"html":8,"headings":9,"words":51},{"title":5,"description":6,"published":7,"updated":7},"What is a test management system","A test management system: core entities (test case, suite, run, result, defect), roles, how it differs from a bug tracker, links to automated tests and CI.","2026-11-03","\u003Cp>A \u003Cstrong>test management system\u003C/strong> (TMS) is software for planning, recording and tracking testing. It stores \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-case\">test cases\u003C/span>, groups them into test suites, executes them in \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-run\">test runs\u003C/span>, records the result of every execution and links tests with requirements, \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"defect\">defects\u003C/span> and automated tests. The ISTQB glossary describes the corresponding class of software as a test management tool: a tool that supports the management and control part of the test process.\u003C/p>\n\u003Cp>No standard defines what a test management system must contain. The vocabulary of its entities comes from the ISTQB glossary and from the ISO/IEC/IEEE 29119 series of software testing standards, whose part 3 (test documentation, current edition 2021) describes the documents that a testing process produces. Systems differ in names and details, but the core entities and the relations between them are the same in most of them.\u003C/p>\n\u003Ch2 id=\"the-problem-a-test-management-system-solves\" class=\"wiki-heading\">The problem a test management system solves\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"the-problem-a-test-management-system-solves\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cp>Testing produces two kinds of information. The first is the description of the tests: what is checked, under which conditions, with which steps and which \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"expected-result\">expected results\u003C/span>. The second is the record of execution: which tests were run, on which version of the product, in which environment, by whom and with what outcome.\u003C/p>\n\u003Cp>Both kinds of information can be kept in documents and spreadsheets. As the number of tests, releases and testers grows, this approach runs into limits:\u003C/p>\n\u003Cul>\n\u003Cli>the same test is executed many times, and a spreadsheet keeps either the description or the history of results, not both in a form that can be queried;\u003C/li>\n\u003Cli>several testers work on the same set of tests at the same time, and edits conflict;\u003C/li>\n\u003Cli>a failed test needs a link to a defect, and the defect needs a link back to the test and to the build where it was found;\u003C/li>\n\u003Cli>managers need progress figures during testing, not after it, and these figures are collected by hand;\u003C/li>\n\u003Cli>questions like "which requirements were checked on build 2.4.1" or "when did this test last pass" require searching through many files.\u003C/li>\n\u003C/ul>\n\u003Cp>A test management system separates the description of a test from the records of its execution and keeps both in one data model. Progress, coverage and history are then computed from the data instead of being collected by hand.\u003C/p>\n\u003Ch2 id=\"core-entities\" class=\"wiki-heading\">Core entities\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"core-entities\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cp>The entities below are present in most test management systems. Their names vary: a test run is also called a test execution or a test cycle, a test suite is also called a folder or a section.\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-3\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Entity\u003C/th>\n\u003Cth>What it is\u003C/th>\n\u003Cth>Detailed article\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Project\u003C/td>\n\u003Ctd>Container for all entities of one product or team: tests, runs, settings, access rights\u003C/td>\n\u003Ctd>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test case\u003C/td>\n\u003Ctd>Description of one check: preconditions, steps, expected results\u003C/td>\n\u003Ctd>\u003Ca href=\"/en/wiki/test-management/test-case\" class=\"wiki-link wiki-link--article\">Test case\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test suite\u003C/td>\n\u003Ctd>Group of test cases, by feature, component or purpose\u003C/td>\n\u003Ctd>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test plan\u003C/td>\n\u003Ctd>Description of the scope, approach, resources and schedule of testing\u003C/td>\n\u003Ctd>\u003Ca href=\"/en/wiki/test-management/test-plan-and-test-strategy\" class=\"wiki-link wiki-link--article\">Test plan and test strategy\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test run\u003C/td>\n\u003Ctd>Execution of a selected set of test cases on a specific version of the product in a specific environment\u003C/td>\n\u003Ctd>\u003Ca href=\"/en/wiki/test-management/test-run\" class=\"wiki-link wiki-link--article\">Test run\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test result\u003C/td>\n\u003Ctd>Record of one execution of one test case within a run: status, actual result, attachments\u003C/td>\n\u003Ctd>\u003Ca href=\"/en/wiki/test-management/test-run\" class=\"wiki-link wiki-link--article\">Test run\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Defect\u003C/td>\n\u003Ctd>Record of a defect found during testing: a defect report\u003C/td>\n\u003Ctd>\u003Ca href=\"/en/wiki/test-management/defect-report\" class=\"wiki-link wiki-link--article\">Defect report\u003C/a>\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Requirement\u003C/td>\n\u003Ctd>Statement of what the product must do, which tests are linked to\u003C/td>\n\u003Ctd>\u003Ca href=\"/en/wiki/test-management/requirements-traceability\" class=\"wiki-link wiki-link--article\">Requirements traceability\u003C/a>\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Ch3 id=\"test-case-and-test-suite\" class=\"wiki-heading\">Test case and test suite\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-case-and-test-suite\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h3>\n\u003Cp>A \u003Cstrong>test case\u003C/strong> is the unit of the test description. The ISTQB glossary defines it as a set of \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"precondition\">preconditions\u003C/span>, inputs, actions, expected results and postconditions, developed based on \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-condition\">test conditions\u003C/span>. In a test management system a test case has an identifier, a title, a body (preconditions, steps, expected results) and attributes: priority, status, author, tags, custom properties.\u003C/p>\n\u003Cp>A \u003Cstrong>test suite\u003C/strong> groups test cases. The ISTQB glossary defines a test suite as a set of test scripts or test procedures to be executed in a specific test run. Test management systems usually use the word more broadly, for any named group of test cases: a feature ("Checkout"), a component ("Payment API") or a purpose ("Smoke tests"). Suites are often nested and form a tree.\u003C/p>\n\u003Ch3 id=\"test-run-and-test-result\" class=\"wiki-heading\">Test run and test result\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-run-and-test-result\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h3>\n\u003Cp>A \u003Cstrong>test run\u003C/strong> is a single execution of a selected set of test cases. A run records what was tested (the version or build of the product), where (the environment: operating system, browser, device, configuration) and when. A run contains one result for every test case included in it.\u003C/p>\n\u003Cp>A \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-result\">test result\u003C/span> belongs to one test case and one run. It holds the status (for example, passed or failed), the actual result, comments, attachments such as screenshots and logs, the time spent and the person who executed the test. A failed result is linked to a defect.\u003C/p>\n\u003Cp>The separation of test case and test result is the central idea of the data model. A test case is a specification that changes rarely. A result is a fact about one execution. One test case collects many results over time:\u003C/p>\n\u003Cdiv class=\"wiki-code wiki-code--plain\">\u003Cpre>\u003Ccode>Test case TC-12 "Pay with a saved card"\n |\n +-- Run "Release 2.4.0, Chrome"   -> passed\n +-- Run "Release 2.4.0, Safari"   -> failed  -> Defect BUG-310\n +-- Run "Release 2.4.1, Safari"   -> passed  (confirmation of the fix)\u003C/code>\u003C/pre>\u003C/div>\n\u003Ch3 id=\"test-plan\" class=\"wiki-heading\">Test plan\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-plan\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h3>\n\u003Cp>A \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-plan\">test plan\u003C/span> describes what will be tested, how, by whom and when. In some systems it is a document attached to the project. In others it is an entity that groups several test runs, for example all runs of one release on different environments, and shows their combined progress. The meaning of the document and its contents according to ISO/IEC/IEEE 29119-3 are described in the article \u003Ca href=\"/en/wiki/test-management/test-plan-and-test-strategy\" class=\"wiki-link wiki-link--article\">Test plan and test strategy\u003C/a>.\u003C/p>\n\u003Ch3 id=\"defect-and-requirement\" class=\"wiki-heading\">Defect and requirement\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"defect-and-requirement\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h3>\n\u003Cp>A defect, in the wording of the ISTQB glossary, is an imperfection or deficiency in a work product where it does not meet its requirements or specifications. In a test management system defects are either stored as its own entity or kept in an external bug tracker and linked by identifier. In both cases the link goes in both directions: from the result to the defect and from the defect to the test case, the run and the build.\u003C/p>\n\u003Cp>A requirement is a statement of what the product must do: an item of a specification, a \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"user-story\">user story\u003C/span>, an acceptance criterion. Links between requirements and test cases make it possible to compute \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"requirements-coverage\">requirements coverage\u003C/span> and to find the tests affected by a change of a requirement.\u003C/p>\n\u003Ch3 id=\"how-the-entities-are-related\" class=\"wiki-heading\">How the entities are related\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"how-the-entities-are-related\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h3>\n\u003Cp>The diagram shows the relations between the core entities. An arrow reads as "contains" or "is linked to".\u003C/p>\n\u003Cdiv class=\"wiki-code wiki-code--plain\">\u003Cpre>\u003Ccode>Project\n |\n +-- Test suites --- contain ---> Test cases <--- linked ---> Requirements\n |                                   |\n +-- Test plan --- groups ---> Test runs\n                                     |\n                                     +-- Test results (one per test case in the run)\n                                              |\n                                              +-- linked ---> Defects\u003C/code>\u003C/pre>\u003C/div>\n\u003Cp>Most test management systems also have \u003Cstrong>custom properties\u003C/strong>: fields defined by the team for test cases, runs or results, such as "Component", "Platform" or "Risk level". Custom properties are used for filtering, reporting and for mapping data between systems.\u003C/p>\n\u003Ch2 id=\"roles\" class=\"wiki-heading\">Roles\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"roles\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cp>The ISTQB Foundation Level syllabus (version 4.0.1) distinguishes two main roles in testing. The \u003Cstrong>test management role\u003C/strong> is responsible for the test process as a whole: planning, monitoring and control, completion. The \u003Cstrong>testing role\u003C/strong> is responsible for the technical side: analysis, design, implementation and execution of tests. One person can perform both roles, and in agile teams some test management tasks are taken over by the team.\u003C/p>\n\u003Cp>In a test management system these roles correspond to different sets of actions:\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-2\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Role\u003C/th>\n\u003Cth>Typical actions in the system\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Test management\u003C/td>\n\u003Ctd>Creates test plans and runs, assigns tests to testers, monitors progress, prepares reports\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Testing\u003C/td>\n\u003Ctd>Writes and reviews test cases, executes runs, records results, reports defects\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Development\u003C/td>\n\u003Ctd>Reads failed results and defects, reproduces failures, links fixes, publishes results of automated tests\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Analysis and product\u003C/td>\n\u003Ctd>Links requirements with test cases, reviews coverage and the results of acceptance testing\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Cp>Access rights in a system are usually set per project and per role: who can edit test cases, who can create runs, who can only read.\u003C/p>\n\u003Ch2 id=\"the-test-process-in-a-test-management-system\" class=\"wiki-heading\">The test process in a test management system\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"the-test-process-in-a-test-management-system\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cp>The ISTQB syllabus divides the test process into activities. Each of them produces work products that a test management system stores or computes.\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-3\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Activity\u003C/th>\n\u003Cth>What it produces\u003C/th>\n\u003Cth>Where it lives in the system\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Test planning\u003C/td>\n\u003Ctd>Test plan, scope, entry and exit criteria\u003C/td>\n\u003Ctd>Test plan, milestones\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Monitoring and control\u003C/td>\n\u003Ctd>Progress against the plan, deviations\u003C/td>\n\u003Ctd>Dashboards and reports computed from results\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test analysis\u003C/td>\n\u003Ctd>Test conditions: what needs to be tested\u003C/td>\n\u003Ctd>Requirements and their links\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test design\u003C/td>\n\u003Ctd>Test cases, test data requirements\u003C/td>\n\u003Ctd>Test cases and suites\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test implementation\u003C/td>\n\u003Ctd>Test procedures, suites for execution, environments\u003C/td>\n\u003Ctd>Selection of test cases for a run, environments and configurations\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test execution\u003C/td>\n\u003Ctd>Results, logs, defect reports\u003C/td>\n\u003Ctd>Test results, attachments, defects\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test completion\u003C/td>\n\u003Ctd>Test completion report, lessons learned\u003C/td>\n\u003Ctd>Reports over runs and plans, archive of runs\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Cp>The sequence of activities depends on the development model. In an iterative process the same cycle of design, execution and completion repeats in every iteration, and the system keeps the history across iterations.\u003C/p>\n\u003Ch2 id=\"automated-tests-and-ci\" class=\"wiki-heading\">Automated tests and CI\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"automated-tests-and-ci\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cp>Automated tests are code. They live in a code repository and run in a \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"continuous-integration\">continuous integration\u003C/span> (CI) system on every change. A test management system does not replace the test framework or the CI system. It receives the results of automated test runs and stores them together with the results of manual testing.\u003C/p>\n\u003Cp>The common data flow:\u003C/p>\n\u003Cdiv class=\"wiki-code wiki-code--plain\">\u003Cpre>\u003Ccode>Code repository --> CI pipeline --> Test framework --> Report file\n                                                          |\n                                                          v\n                                        Test management system: test run with results\u003C/code>\u003C/pre>\u003C/div>\n\u003Cp>The most widespread exchange format is \u003Cstrong>JUnit XML\u003C/strong>. It was popularized by the JUnit project and is supported by most test frameworks, CI systems and test management systems. There is no official specification of the format, and tools produce slightly different variants of it. The core structure is stable:\u003C/p>\n\u003Cdiv class=\"wiki-code\" data-language=\"xml\">\u003Cdiv class=\"wiki-code__header\">\u003Cspan class=\"wiki-code__language\">xml\u003C/span>\u003Cbutton type=\"button\" class=\"wiki-code__copy\" data-wiki-copy data-copied-label=\"Copied\">\u003Csvg class=\"wiki-code__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M216,28H88A12,12,0,0,0,76,40V76H40A12,12,0,0,0,28,88V216a12,12,0,0,0,12,12H168a12,12,0,0,0,12-12V180h36a12,12,0,0,0,12-12V40A12,12,0,0,0,216,28ZM156,204H52V100H156Zm48-48H180V88a12,12,0,0,0-12-12H100V52H204Z\"/>\u003C/svg>\u003Csvg class=\"wiki-code__icon wiki-code__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003Cspan class=\"wiki-code__label\">Copy\u003C/span>\u003Cspan class=\"wiki-code__label wiki-code__label--done\">Copied\u003C/span>\u003C/button>\u003C/div>\u003Cpre>\u003Ccode><?xml version="1.0" encoding="UTF-8"?>\n<testsuites name="checkout" tests="3" failures="1" errors="0" skipped="1" time="4.21">\n  <testsuite name="Checkout.Payment" tests="3" failures="1" errors="0" skipped="1" time="4.21">\n    <testcase classname="Checkout.Payment" name="pay_with_saved_card" time="1.62"/>\n    <testcase classname="Checkout.Payment" name="pay_with_expired_card" time="2.59">\n      <failure message="Expected error message was not shown" type="AssertionError"/>\n    </testcase>\n    <testcase classname="Checkout.Payment" name="pay_with_gift_card" time="0">\n      <skipped message="Gift cards are disabled in this environment"/>\n    </testcase>\n  </testsuite>\n</testsuites>\u003C/code>\u003C/pre>\u003C/div>\n\u003Cp>A \u003Ccode>testcase\u003C/code> element without a child element is a passed test. \u003Ccode>failure\u003C/code> means that a check in the test failed, \u003Ccode>error\u003C/code> means an unexpected problem during execution, \u003Ccode>skipped\u003C/code> means that the test was not executed.\u003C/p>\n\u003Cp>To link an automated test with a test case in the system, its result needs an identifier that both sides know. The usual options are the full name of the test (\u003Ccode>classname\u003C/code> and \u003Ccode>name\u003C/code>), the identifier of the test case written in the name or in a property of the test, or a mapping table maintained in the system. Besides importing files, test management systems provide an API through which a CI job creates a run and sends results directly.\u003C/p>\n\u003Cp>How automated tests are organized by level is described in the article \u003Ca href=\"/en/wiki/test-automation/automation-levels-and-test-pyramid\" class=\"wiki-link wiki-link--article\">Test automation levels and the test pyramid\u003C/a>. How they run in CI and how their results reach test runs is described in the article \u003Ca href=\"/en/wiki/test-automation/automated-tests-in-ci\" class=\"wiki-link wiki-link--article\">Automated tests in CI\u003C/a>.\u003C/p>\n\u003Ch2 id=\"test-management-system-bug-tracker-and-task-tracker\" class=\"wiki-heading\">Test management system, bug tracker and task tracker\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-management-system-bug-tracker-and-task-tracker\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cp>A test management system is often used together with a bug tracker and a task tracker, and their functions partly overlap.\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-4\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>\u003C/th>\n\u003Cth>Test management system\u003C/th>\n\u003Cth>Bug tracker\u003C/th>\n\u003Cth>Task tracker\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Main object\u003C/td>\n\u003Ctd>Test case and its results\u003C/td>\n\u003Ctd>Defect\u003C/td>\n\u003Ctd>Task, user story\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Unit of history\u003C/td>\n\u003Ctd>Result of an execution of a test on a build\u003C/td>\n\u003Ctd>Change of the status of a defect\u003C/td>\n\u003Ctd>Change of the status of a task\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Repeated use\u003C/td>\n\u003Ctd>A test case is executed many times, in many runs\u003C/td>\n\u003Ctd>A defect is fixed and closed once; it can be reopened\u003C/td>\n\u003Ctd>A task is completed once\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Typical questions\u003C/td>\n\u003Ctd>What was tested on this build, what passed, what is covered\u003C/td>\n\u003Ctd>Which defects are open, who fixes them, how severe they are\u003C/td>\n\u003Ctd>What is planned, who does it, what is done\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Link to the others\u003C/td>\n\u003Ctd>Results link to defects, test cases to requirements\u003C/td>\n\u003Ctd>Defects link to results and to commits\u003C/td>\n\u003Ctd>Tasks link to requirements and to defects\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Cp>The key difference is repetition. A defect or a task has one life cycle that ends with closing. A test case is not closed after execution: it is executed again on every build, in every environment, in every regression cycle, and the value lies in the history of these executions.\u003C/p>\n\u003Cp>A bug tracker can store test cases as a special type of issue, and some teams do so. In this case each execution is either recorded as a change of the issue, which loses the history of earlier results, or as a separate issue, which mixes tests with their results. A test management system models the test case, the run and the result as separate entities, so the history of each test and the state of each run can be queried directly.\u003C/p>\n\u003Cp>In practice the systems are integrated: a defect is created from a failed result and stored in the bug tracker; requirements come from the task tracker; the test management system keeps the links and computes coverage and progress.\u003C/p>\n\u003Ch2 id=\"terms\" class=\"wiki-heading\">Terms\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"terms\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cdiv class=\"wiki-table wiki-table--cols-2\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Term\u003C/th>\n\u003Cth>Meaning\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Test management system\u003C/td>\n\u003Ctd>Software for planning, recording and tracking testing: test cases, runs, results and their links\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test case\u003C/td>\n\u003Ctd>Set of preconditions, inputs, actions, expected results and postconditions, developed based on test conditions\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test suite\u003C/td>\n\u003Ctd>Named group of test cases, by feature, component or purpose\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test run\u003C/td>\n\u003Ctd>Execution of a selected set of test cases on a specific version of the product in a specific environment\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test result\u003C/td>\n\u003Ctd>Record of one execution of one test case within a test run\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Defect\u003C/td>\n\u003Ctd>Imperfection or deficiency in a work product where it does not meet its requirements or specifications\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Requirement\u003C/td>\n\u003Ctd>Statement of what the product must do, which tests are linked to\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Custom property\u003C/td>\n\u003Ctd>Field defined by the team for test cases, runs or results\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>JUnit XML\u003C/td>\n\u003Ctd>De facto standard XML format for exchanging results of automated tests\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Ch2 id=\"sources\" class=\"wiki-heading\">Sources\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"sources\" aria-label=\"Copy link to section\" data-copied-label=\"Link to section copied\">\u003Csvg class=\"wiki-heading__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M117.18,188.74a12,12,0,0,1,0,17l-5.12,5.12A58.26,58.26,0,0,1,70.6,228h0A58.62,58.62,0,0,1,29.14,127.92L63.89,93.17a58.64,58.64,0,0,1,98.56,28.11,12,12,0,1,1-23.37,5.44,34.65,34.65,0,0,0-58.22-16.58L46.11,144.89A34.62,34.62,0,0,0,70.57,204h0a34.41,34.41,0,0,0,24.49-10.14l5.11-5.12A12,12,0,0,1,117.18,188.74ZM226.83,45.17a58.65,58.65,0,0,0-82.93,0l-5.11,5.11a12,12,0,0,0,17,17l5.12-5.12a34.63,34.63,0,1,1,49,49L175.1,145.86A34.39,34.39,0,0,1,150.61,156h0a34.63,34.63,0,0,1-33.69-26.72,12,12,0,0,0-23.38,5.44A58.64,58.64,0,0,0,150.56,180h.05a58.28,58.28,0,0,0,41.47-17.17l34.75-34.75a58.62,58.62,0,0,0,0-82.91Z\"/>\u003C/svg>\u003Csvg class=\"wiki-heading__icon wiki-heading__icon--done\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M232.49,80.49l-128,128a12,12,0,0,1-17,0l-56-56a12,12,0,1,1,17-17L96,183,215.51,63.51a12,12,0,0,1,17,17Z\"/>\u003C/svg>\u003C/button>\u003C/h2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https://www.istqb.org/wp-content/uploads/2024/11/ISTQB_CTFL_Syllabus_v4.0.1.pdf\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">ISTQB Certified Tester Foundation Level Syllabus v4.0.1, ISTQB, 2024\u003Csvg class=\"wiki-link__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M228,104a12,12,0,0,1-24,0V69l-59.51,59.51a12,12,0,0,1-17-17L187,52H152a12,12,0,0,1,0-24h64a12,12,0,0,1,12,12Zm-44,24a12,12,0,0,0-12,12v64H52V84h64a12,12,0,0,0,0-24H48A20,20,0,0,0,28,80V208a20,20,0,0,0,20,20H176a20,20,0,0,0,20-20V140A12,12,0,0,0,184,128Z\"/>\u003C/svg>\u003Cspan class=\"wiki-visually-hidden\">(opens in a new tab)\u003C/span>\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://glossary.istqb.org/\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">ISTQB Glossary\u003Csvg class=\"wiki-link__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M228,104a12,12,0,0,1-24,0V69l-59.51,59.51a12,12,0,0,1-17-17L187,52H152a12,12,0,0,1,0-24h64a12,12,0,0,1,12,12Zm-44,24a12,12,0,0,0-12,12v64H52V84h64a12,12,0,0,0,0-24H48A20,20,0,0,0,28,80V208a20,20,0,0,0,20,20H176a20,20,0,0,0,20-20V140A12,12,0,0,0,184,128Z\"/>\u003C/svg>\u003Cspan class=\"wiki-visually-hidden\">(opens in a new tab)\u003C/span>\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://www.iso.org/standard/79429.html\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">ISO/IEC/IEEE 29119-3:2021, Software testing, Part 3: Test documentation\u003Csvg class=\"wiki-link__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M228,104a12,12,0,0,1-24,0V69l-59.51,59.51a12,12,0,0,1-17-17L187,52H152a12,12,0,0,1,0-24h64a12,12,0,0,1,12,12Zm-44,24a12,12,0,0,0-12,12v64H52V84h64a12,12,0,0,0,0-24H48A20,20,0,0,0,28,80V208a20,20,0,0,0,20,20H176a20,20,0,0,0,20-20V140A12,12,0,0,0,184,128Z\"/>\u003C/svg>\u003Cspan class=\"wiki-visually-hidden\">(opens in a new tab)\u003C/span>\u003C/a>\u003C/li>\n\u003Cli>\u003Ca href=\"https://github.com/testmoapp/junitxml\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">Common JUnit XML format and examples, Testmo\u003Csvg class=\"wiki-link__icon\" viewBox=\"0 0 256 256\" width=\"16\" height=\"16\" fill=\"currentColor\" aria-hidden=\"true\" focusable=\"false\">\u003Cpath d=\"M228,104a12,12,0,0,1-24,0V69l-59.51,59.51a12,12,0,0,1-17-17L187,52H152a12,12,0,0,1,0-24h64a12,12,0,0,1,12,12Zm-44,24a12,12,0,0,0-12,12v64H52V84h64a12,12,0,0,0,0-24H48A20,20,0,0,0,28,80V208a20,20,0,0,0,20,20H176a20,20,0,0,0,20-20V140A12,12,0,0,0,184,128Z\"/>\u003C/svg>\u003Cspan class=\"wiki-visually-hidden\">(opens in a new tab)\u003C/span>\u003C/a>\u003C/li>\n\u003C/ul>\n",[10,14,17,21,24,27,30,33,36,39,42,45,48],{"id":11,"level":12,"text":13},"the-problem-a-test-management-system-solves",2,"The problem a test management system solves",{"id":15,"level":12,"text":16},"core-entities","Core entities",{"id":18,"level":19,"text":20},"test-case-and-test-suite",3,"Test case and test suite",{"id":22,"level":19,"text":23},"test-run-and-test-result","Test run and test result",{"id":25,"level":19,"text":26},"test-plan","Test plan",{"id":28,"level":19,"text":29},"defect-and-requirement","Defect and requirement",{"id":31,"level":19,"text":32},"how-the-entities-are-related","How the entities are related",{"id":34,"level":12,"text":35},"roles","Roles",{"id":37,"level":12,"text":38},"the-test-process-in-a-test-management-system","The test process in a test management system",{"id":40,"level":12,"text":41},"automated-tests-and-ci","Automated tests and CI",{"id":43,"level":12,"text":44},"test-management-system-bug-tracker-and-task-tracker","Test management system, bug tracker and task tracker",{"id":46,"level":12,"text":47},"terms","Terms",{"id":49,"level":12,"text":50},"sources","Sources",2176,1793718944034]