[{"data":1,"prerenderedAt":52},["ShallowReactive",2],{"wiki-test-management-test-plan-and-test-strategy-en":3},{"meta":4,"html":8,"headings":9,"words":51},{"title":5,"description":6,"published":7,"updated":7},"Test plan and test strategy","Test plan and test strategy: purpose, sections by ISO/IEC/IEEE 29119-3, entry and exit criteria, link to test runs, test policy and practices.","2026-11-03","\u003Cp>A \u003Cstrong>test plan\u003C/strong> is a document that describes the objectives of testing and the means and schedule for achieving them: what is tested, how, by whom, with which resources and by when. ISO/IEC/IEEE 29119-3 defines it as a detailed description of test objectives to be achieved and the means and schedule for achieving them. A \u003Cstrong>test strategy\u003C/strong>, in the same standard, is the part of the test plan that describes the approach to testing for a specific project, test level or test type.\u003C/p>\n\u003Cp>The structure of both documents is set by ISO/IEC/IEEE 29119-3, Software testing, Part 3: Test documentation. Its current edition was published in October 2021 and replaced the first edition of 2013. Before the 29119 series, test documentation was described by IEEE 829, first published in 1983. The ISTQB Foundation Level syllabus (version 4.0.1) uses the same structure in a shortened form.\u003C/p>\n\u003Ch2 id=\"overview\" class=\"wiki-heading\">Overview\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"overview\" 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>Property\u003C/th>\n\u003Cth>Value\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Type\u003C/td>\n\u003Ctd>Test management documents\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Current standard\u003C/td>\n\u003Ctd>ISO/IEC/IEEE 29119-3:2021, sections 6 and 7\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Previous standard\u003C/td>\n\u003Ctd>IEEE 829-2008, superseded by the ISO/IEC/IEEE 29119 series\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Organizational level\u003C/td>\n\u003Ctd>Test policy, organizational test practices\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Project level\u003C/td>\n\u003Ctd>Test plan, which includes the test strategy\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Reports based on the plan\u003C/td>\n\u003Ctd>Test status report, test completion report\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Developed by\u003C/td>\n\u003Ctd>ISO/IEC JTC 1/SC 7 together with the IEEE Computer Society\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Ch2 id=\"the-problem-a-test-plan-solves\" class=\"wiki-heading\">The problem a test plan solves\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"the-problem-a-test-plan-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 is limited by time, people and environments, and it is never complete: the number of possible checks exceeds the number that can be performed. Somebody decides what is tested and what is not, which risks are accepted and when testing stops. Without a written plan these decisions are made implicitly, by different people at different times, and nobody can check them later.\u003C/p>\n\u003Cp>A test plan records these decisions before testing starts and makes them visible to the stakeholders: the project manager, developers, analysts, customers. It serves three purposes:\u003C/p>\n\u003Cul>\n\u003Cli>\u003Cstrong>agreement\u003C/strong>: the stakeholders see the scope, the risks, the resources and the schedule and can object before the work is done;\u003C/li>\n\u003Cli>\u003Cstrong>control\u003C/strong>: progress during testing is compared with the plan, and deviations are visible;\u003C/li>\n\u003Cli>\u003Cstrong>completion\u003C/strong>: the exit criteria in the plan define when testing of a level or a release is finished.\u003C/li>\n\u003C/ul>\n\u003Ch2 id=\"history\" class=\"wiki-heading\">History\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"history\" 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>Date\u003C/th>\n\u003Cth>Event\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>18 February 1983\u003C/td>\n\u003Ctd>IEEE 829-1983, Standard for Software Test Documentation: the first standard set of test documents, including the test plan\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>16 December 1998\u003C/td>\n\u003Ctd>IEEE 829-1998, revision of the standard\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>18 July 2008\u003C/td>\n\u003Ctd>IEEE 829-2008, Standard for Software and System Test Documentation: separates the master test plan from level test plans\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>September 2013\u003C/td>\n\u003Ctd>ISO/IEC/IEEE 29119-1, -2 and -3 are published; IEEE 829-2008 is superseded\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>October 2021\u003C/td>\n\u003Ctd>Second edition of ISO/IEC/IEEE 29119-3: the concept of test conditions is replaced by test models, the organizational document is called organizational test practices\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Ch2 id=\"levels-of-test-documentation\" class=\"wiki-heading\">Levels of test documentation\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"levels-of-test-documentation\" 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>ISO/IEC/IEEE 29119-3 groups test documents by the level of the test process that produces them. The test plan is the main document of the middle level.\u003C/p>\n\u003Cdiv class=\"wiki-code wiki-code--plain\">\u003Cpre>\u003Ccode>Organizational level\n |  Test policy\n |  Organizational test practices\n |\n +-- Test management level (project, test level, test type)\n |     Test plan (includes the test strategy)\n |     Test status report\n |     Test completion report\n |\n +-- Dynamic test level\n       Test model specification, test case specification,\n       test procedure specification, test data and environment requirements,\n       readiness reports, test results, test execution log, test incident report\u003C/code>\u003C/pre>\u003C/div>\n\u003Cp>The \u003Cstrong>test policy\u003C/strong> is, in the wording of the ISTQB glossary, a high-level document describing the principles, approach and major objectives of the organization regarding testing. It applies to all projects and changes rarely.\u003C/p>\n\u003Cp>\u003Cstrong>Organizational test practices\u003C/strong> describe how testing is performed in the organization in general: which test levels and types are used, which techniques, which documents, which completion criteria. In the 2013 edition of the standard this document was called the organizational test strategy.\u003C/p>\n\u003Cp>The test plan applies the policy and the practices to a specific project, test level or test type.\u003C/p>\n\u003Ch3 id=\"master-test-plan-and-level-test-plans\" class=\"wiki-heading\">Master test plan and level test plans\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"master-test-plan-and-level-test-plans\" 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 project can have one test plan or several. IEEE 829-2008 introduced the division into a \u003Cstrong>master test plan\u003C/strong>, which covers the planning and management of testing across several test levels, and \u003Cstrong>level test plans\u003C/strong>, each of which describes the scope, approach, resources and schedule of one level: component, integration, system or acceptance testing. ISO/IEC/IEEE 29119-3 keeps this possibility: its test plan can be written for a whole project, for one test level or for one test type, such as performance testing.\u003C/p>\n\u003Cp>The division follows the responsibilities. The master test plan holds what is common to all levels: the risks of the project, the stakeholders, the overall schedule, the order of the levels and the criteria for moving from one to the next. A level test plan holds what is specific to the level: the test items, the techniques, the environments, the entry and exit criteria of the level. One plan covers all levels when they are planned and tested by one team on one schedule. Separate level plans are written when the levels are tested by different teams, on different schedules or under different exit criteria.\u003C/p>\n\u003Ch2 id=\"contents-of-a-test-plan\" class=\"wiki-heading\">Contents of a test plan\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"contents-of-a-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/h2>\n\u003Cp>ISO/IEC/IEEE 29119-3 (section 7.2) divides a test plan into the parts listed below. The standard defines two kinds of conformance, full and tailored. Tailored conformance allows the documents and their contents to be adapted to the context of the organization and the project.\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-2\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Part\u003C/th>\n\u003Cth>What it contains\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Context of testing\u003C/td>\n\u003Ctd>Project and test items, scope of testing (what is included and what is not), test basis\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Assumptions and constraints\u003C/td>\n\u003Ctd>Conditions taken as given and limits of the project: dates, budget, regulations\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Stakeholders\u003C/td>\n\u003Ctd>Who is interested in testing, their roles and responsibilities\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Communication\u003C/td>\n\u003Ctd>How and how often information about testing is shared, which reports and templates are used\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Risk register\u003C/td>\n\u003Ctd>Product risks and project risks that affect testing, with their levels\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test strategy\u003C/td>\n\u003Ctd>The approach to testing: see below\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Testing activities and estimates\u003C/td>\n\u003Ctd>Which activities are performed and the effort they need\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Staffing\u003C/td>\n\u003Ctd>Roles, people, the need for hiring and training\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Schedule\u003C/td>\n\u003Ctd>Dates and milestones of the testing activities\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Cp>Like all documents of the standard, a test plan also has common information: an identifier, the issuing organization, the approval authority, the change history, the status, an introduction, references and a glossary.\u003C/p>\n\u003Cp>The ISTQB Foundation Level syllabus (section 5.1.1) lists the typical content of a test plan in nearly the same terms: the context of testing, assumptions and constraints, stakeholders, communication, the risk register, the test approach, the budget and the schedule.\u003C/p>\n\u003Ch3 id=\"test-strategy-within-the-test-plan\" class=\"wiki-heading\">Test strategy within the test plan\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-strategy-within-the-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>The test strategy is the part of the plan that says how testing is done. The ISTQB syllabus calls the corresponding part of the plan the test approach and lists its typical content:\u003C/p>\n\u003Cul>\n\u003Cli>test levels and test types;\u003C/li>\n\u003Cli>test techniques;\u003C/li>\n\u003Cli>test deliverables: which documents and reports are produced;\u003C/li>\n\u003Cli>entry criteria and exit criteria;\u003C/li>\n\u003Cli>independence of testing: who tests the work of whom;\u003C/li>\n\u003Cli>metrics to be collected;\u003C/li>\n\u003Cli>test data requirements and \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-environment\">test environment\u003C/span> requirements;\u003C/li>\n\u003Cli>deviations from the organizational test policy and test strategy.\u003C/li>\n\u003C/ul>\n\u003Cp>Each element is chosen based on the risks of the project. A component with a high product risk gets more test levels, more rigorous techniques and stricter exit criteria than a component with a low risk.\u003C/p>\n\u003Cblockquote>\n\u003Cp>The term "test strategy" has two meanings. In ISO/IEC/IEEE 29119-3 it is the part of a project test plan. In everyday use, and in older versions of the standard and of the ISTQB glossary, it also means an organization-wide document that applies to many projects. The 2021 edition of 29119-3 calls that document organizational test practices. The ISTQB glossary defines the test approach as the implementation of the test strategy for a specific project.\u003C/p>\n\u003C/blockquote>\n\u003Ch2 id=\"entry-and-exit-criteria\" class=\"wiki-heading\">Entry and exit criteria\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"entry-and-exit-criteria\" 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>\u003Cstrong>Entry criteria\u003C/strong> are the \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"precondition\">preconditions\u003C/span> for starting a test activity. \u003Cstrong>Exit criteria\u003C/strong> define what has to be achieved for the activity to be considered complete. The ISTQB syllabus (section 5.1.3) recommends defining both for each test level and gives typical examples:\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-2\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Kind of criterion\u003C/th>\n\u003Cth>Examples\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Entry: availability of resources\u003C/td>\n\u003Ctd>People, tools, environments, test data, budget, time\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Entry: availability of testware\u003C/td>\n\u003Ctd>Test basis, testable requirements, user stories, test cases\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Entry: initial quality of the test object\u003C/td>\n\u003Ctd>Smoke tests have passed\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Exit: measures of thoroughness\u003C/td>\n\u003Ctd>Achieved level of coverage, number of unresolved defects, defect density, number of failed test cases\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Exit: completion\u003C/td>\n\u003Ctd>Planned tests have been executed, static testing has been performed, all defects found are reported, regression tests are automated\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Cp>A criterion is written so that it can be checked against data. "Testing is sufficient" cannot be checked. "All \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-case\">test cases\u003C/span> of priority High are executed, coverage of the requirements of the release is at least 95 percent, there are no open \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"defect\">defects\u003C/span> of \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"severity\">severity\u003C/span> Critical" can be checked against the results of \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-run\">test runs\u003C/span> and the list of defects.\u003C/p>\n\u003Cp>The ISTQB syllabus also notes that running out of time or budget can be treated as a valid exit criterion, if the stakeholders have reviewed and accepted the risk of releasing without further testing. In agile development the exit criteria are often expressed as the Definition of Done, and the entry criteria for a \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"user-story\">user story\u003C/span> as the Definition of Ready.\u003C/p>\n\u003Ch2 id=\"test-plan-and-test-runs\" class=\"wiki-heading\">Test plan and test runs\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-plan-and-test-runs\" 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 plan is executed through test runs. A plan for a release typically has several runs: one for each environment, one for each test level, successive runs after fixes. In a \u003Cspan class=\"wiki-term\" tabindex=\"0\" data-wiki-term=\"test-management-system\">test management system\u003C/span> a plan can be an entity that groups these runs and sums up their results.\u003C/p>\n\u003Cdiv class=\"wiki-code wiki-code--plain\">\u003Cpre>\u003Ccode>Test plan "Release 2.4"\n |  Exit criteria: all High test cases executed, no open Critical defects\n |\n +-- Run "System test, Chrome"      200 test cases\n +-- Run "System test, Safari"      200 test cases\n +-- Run "Acceptance test"           45 test cases\n +-- Run "Regression, build 2.4.1"  320 test cases\u003C/code>\u003C/pre>\u003C/div>\n\u003Cp>During testing the results of the runs are compared with the plan. The test status report, which ISO/IEC/IEEE 29119-3 describes in section 7.3, contains the test status, the reporting period, progress against the test plan, factors blocking progress, measures, new and changed risks and the testing planned for the next period. The test completion report (section 7.4) summarizes the testing performed, the deviations from the plan, the evaluation against the completion criteria, the residual risks and the lessons learned.\u003C/p>\n\u003Cp>The plan itself changes during the project. When the scope, the risks or the schedule change, the plan is revised, and the change history of the document shows what was decided and when. The structure of a run and its summary are described in the article \u003Ca href=\"/en/wiki/test-management/test-run\" class=\"wiki-link wiki-link--article\">Test run\u003C/a>.\u003C/p>\n\u003Ch2 id=\"test-plan-in-iterative-development\" class=\"wiki-heading\">Test plan in iterative development\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-plan-in-iterative-development\" 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 describes test planning as an activity that takes place in any development model. What differs is its scale and frequency. In sequential models a test plan is usually a single document written before testing starts. In iterative models the plan is revised in every iteration: the release plan sets the overall approach, and the iteration plan sets the scope of testing for the next iteration.\u003C/p>\n\u003Cp>ISO/IEC/IEEE 29119-3 is explicitly intended for all development life cycle models. Its annexes contain examples of each document for an agile project and for a traditional project. A plan in an agile team can be short, for example one page with the scope, the risks, the test levels and the Definition of Done.\u003C/p>\n\u003Ch2 id=\"test-plan-test-strategy-and-test-policy\" class=\"wiki-heading\">Test plan, test strategy and test policy\u003Cbutton type=\"button\" class=\"wiki-heading__anchor\" data-wiki-anchor=\"test-plan-test-strategy-and-test-policy\" 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 three documents are often confused because they differ in level rather than in subject.\u003C/p>\n\u003Cdiv class=\"wiki-table wiki-table--cols-4\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>\u003C/th>\n\u003Cth>Test policy\u003C/th>\n\u003Cth>Organizational test practices\u003C/th>\n\u003Cth>Test plan with test strategy\u003C/th>\n\u003C/tr>\n\u003C/thead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>Level\u003C/td>\n\u003Ctd>Organization\u003C/td>\n\u003Ctd>Organization\u003C/td>\n\u003Ctd>Project, test level or test type\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Question\u003C/td>\n\u003Ctd>Why the organization tests and what it expects from testing\u003C/td>\n\u003Ctd>How testing is generally done in the organization\u003C/td>\n\u003Ctd>What is tested in this project, how, by whom and by when\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Typical size\u003C/td>\n\u003Ctd>One or two pages\u003C/td>\n\u003Ctd>Several pages\u003C/td>\n\u003Ctd>From one page to a long document\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Changes\u003C/td>\n\u003Ctd>Rarely\u003C/td>\n\u003Ctd>When the practices of the organization change\u003C/td>\n\u003Ctd>During the project, with every change of scope or schedule\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Example statement\u003C/td>\n\u003Ctd>"Testing is independent from development for all products used by customers"\u003C/td>\n\u003Ctd>"System testing uses risk-based prioritization and is completed when all high-risk test cases are executed"\u003C/td>\n\u003Ctd>"System testing of release 2.4 covers checkout and payment, runs on Chrome and Safari, ends on 20 November"\u003C/td>\n\u003C/tr>\n\u003C/tbody>\n\u003C/table>\u003C/div>\n\u003Cp>The test plan refers to the documents of the organizational level and records deviations from them. Without an organizational level, which is common in small companies, the test plan contains the whole approach itself.\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 plan\u003C/td>\n\u003Ctd>Detailed description of test objectives to be achieved and the means and schedule for achieving them\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test strategy\u003C/td>\n\u003Ctd>Part of the test plan that describes the approach to testing for a specific project, test level or test type\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test approach\u003C/td>\n\u003Ctd>Implementation of the test strategy for a specific project\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test policy\u003C/td>\n\u003Ctd>High-level document describing the principles, approach and major objectives of the organization regarding testing\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Organizational test practices\u003C/td>\n\u003Ctd>Organization-wide description of how testing is performed; called the organizational test strategy in the 2013 edition of ISO/IEC/IEEE 29119-3\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Entry criteria\u003C/td>\n\u003Ctd>Preconditions for starting a test activity\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Exit criteria\u003C/td>\n\u003Ctd>Conditions that have to be met for a test activity to be considered complete\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Risk register\u003C/td>\n\u003Ctd>List of product and project risks with their levels\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Test status report\u003C/td>\n\u003Ctd>Report on the progress of testing against the test plan for a reporting period\u003C/td>\n\u003C/tr>\n\u003Ctr>\n\u003Ctd>Definition of Done\u003C/td>\n\u003Ctd>Exit criteria of a user story or an iteration in agile development\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.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://standards.iteh.ai/catalog/standards/iso/b4f42a41-dd8f-446c-9674-238ba5dc90f1/iso-iec-ieee-29119-3-2021\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">ISO/IEC/IEEE 29119-3:2021, preview of the standard with its table of contents and definitions, iTeh Standards\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://standards.ieee.org/ieee/829/3787/\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">IEEE 829-2008, Standard for Software and System 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://standards.ieee.org/ieee/829/1217/\" target=\"_blank\" rel=\"noopener\" class=\"wiki-link wiki-link--external\">IEEE 829-1983, Standard for Software 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://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\u003C/ul>\n",[10,14,17,20,23,27,30,33,36,39,42,45,48],{"id":11,"level":12,"text":13},"overview",2,"Overview",{"id":15,"level":12,"text":16},"the-problem-a-test-plan-solves","The problem a test plan solves",{"id":18,"level":12,"text":19},"history","History",{"id":21,"level":12,"text":22},"levels-of-test-documentation","Levels of test documentation",{"id":24,"level":25,"text":26},"master-test-plan-and-level-test-plans",3,"Master test plan and level test plans",{"id":28,"level":12,"text":29},"contents-of-a-test-plan","Contents of a test plan",{"id":31,"level":25,"text":32},"test-strategy-within-the-test-plan","Test strategy within the test plan",{"id":34,"level":12,"text":35},"entry-and-exit-criteria","Entry and exit criteria",{"id":37,"level":12,"text":38},"test-plan-and-test-runs","Test plan and test runs",{"id":40,"level":12,"text":41},"test-plan-in-iterative-development","Test plan in iterative development",{"id":43,"level":12,"text":44},"test-plan-test-strategy-and-test-policy","Test plan, test strategy and test policy",{"id":46,"level":12,"text":47},"terms","Terms",{"id":49,"level":12,"text":50},"sources","Sources",2146,1793718949741]