{"id":24970,"date":"2020-10-21T15:44:03","date_gmt":"2020-10-21T15:44:03","guid":{"rendered":"https:\/\/www.process.st\/templates\/test-plan-template\/"},"modified":"2024-05-14T10:53:39","modified_gmt":"2024-05-14T10:53:39","slug":"test-plan-template","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/test-plan-template\/","title":{"rendered":"Test Plan Template"},"content":{"rendered":"\n<section id=\"introduction-to-test-plan-template\">\n <h2>Introduction to Test Plan Template:<\/h2>\n <div class=\"image-content\">\n  <figure>\n   <a href=\"https:\/\/ps-attachments.s3.amazonaws.com\/7d69b3c2-18d2-4de0-8d2d-ce6255100329\/n3i05nYiLI-qBtBunABEhg.png\" alt=\"Introduction to Test Plan Template:\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/ps-attachments.s3.amazonaws.com\/7d69b3c2-18d2-4de0-8d2d-ce6255100329\/n3i05nYiLI-qBtBunABEhg.png\"> <\/a><!-- No caption -->\n  <\/figure>\n <\/div>\n <div class=\"text-content\">\n  <p><span style=\"color: #007db6;\"><em>*Disclaimer: This Test Plan Template is based upon a <strong>unit test level test.<\/strong><\/em><\/span><\/p>\n  <hr>\n  <p class=\"style-blockquote\">\u201c<em>A test plan is a document describing the scope, approach, resources, and schedule of intended test activities.<\/em>\u201d <a href=\"https:\/\/glossary.istqb.org\/en\/term\/test-plan-3\" rel=\"nofollow noopener\" target=\"_blank\">&nbsp;ISQTB, <em>Test Plan<\/em><\/a><\/p>\n  <p>The Test Plan Template documents and tracks the necessary information required to effectively define the approach to be used in the testing of a software project's product.<\/p>\n  <p><span style=\"text-decoration: underline;\">Here are some<strong> top tips to consider when editing this Test Plan Template<\/strong> Checklist:&nbsp;<\/span><\/p>\n  <ul>\n   <li>Ensure the plan is concise. Be strict with your plan: If a section isn\u2019t bringing actionable value to the plan, delete it<\/li>\n   <li>Be specific. A test plan template is designed to be edited to meet the specific requirements of that particular test. Be precise and detail exactly which feature you are testing (for example)<\/li>\n   <li>Make sure the test plan is scannable: Avoid long paragraphs and use lists and tables when possible<\/li>\n   <li>A successful test plan requires a team effort: have the test plan reviewed at least once. And, always remember to send it for approval<\/li>\n   <li>Always check you are running the most up-to-date plan. Have you ever started editing something only to find you\u2019ve already made the edits in another location? I certainly have and it wastes so much time!<\/li>\n  <\/ul>\n  <hr>\n  <p>If you are <strong>new to<a href=\"https:\/\/www.process.st\/\" rel=\"nofollow noopener\" target=\"_blank\"> Process Street<\/a> <\/strong>and would like a bit on an <strong>introduction<\/strong> to the app: <strong>Check out the video<\/strong> below.<\/p>\n  <p>Or, for <strong>help on using the awesome features<\/strong> to their full capacity <strong>visit our <a href=\"https:\/\/www.process.st\/help\/\" rel=\"nofollow noopener\" target=\"_blank\">help site.<\/a><\/strong><\/p>\n  <p><\/p>\n  <p><em><\/em><\/p>\n  <hr>\n  <p><em>Just to re-cap the disclaimer before we begin, this Test Plan Template only covers <strong>unit testing<\/strong> (testing the code to make sure that it works when standing alone).<\/em><\/p>\n  <hr>\n  <p><strong>Let's get started! \ud83d\ude80<\/strong><\/p>\n <\/div>\n <div class=\"video-content\">\n  <div class=\"iframe-container\">\n   <iframe src=\"https:\/\/www.youtube.com\/embed\/CyDHCV1YBb0?modestbranding=1&amp;showinfo=0\" frameborder=\"0\" allowfullscreen=\"true\"> <\/iframe>\n  <\/div>\n  <div class=\"description\">\n   Process Street - Demo Video\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"preparation\">\n <h2>Preparation:<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-success\">Preparing for the test is vital for ensuring that a record is kept of exactly who made changes and when they did so.<\/p>\n <\/div>\n<\/section>\n<section id=\"record-the-basic-details\">\n <h2>Record the basic details<\/h2>\n <div class=\"text-content\">\n  <p>First up you need to record the<strong> details of this test<\/strong> in order to fully document the process.<\/p>\n  <p>Do so by <strong>filling in the form fields<\/strong> below.<\/p>\n <\/div>\n <div class=\"text-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Testing technician <\/label> <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\">\n  <\/div>\n <\/div>\n <div class=\"text-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> User story link <\/label> <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\">\n  <\/div>\n <\/div>\n <div class=\"textarea-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> User story description <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea>\n  <\/div>\n <\/div>\n <div class=\"date-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Testing date <\/label>\n   <div class=\"date-container\">\n    <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-calendar btn-icon\"><\/i> Date will be set here <\/button>\n   <\/div>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"assign-team-members-for-inclusion-in-the-test\">\n <h2>Assign team members for inclusion in the test<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-info\">Identify which team members (if any) will be collaborating with you in the testing process. This includes any members that will need to authorize this test at a later stage.&nbsp;<\/p>\n  <p>Use the <strong>Assign Members form field below to incorporate team members into this testing process<\/strong>.<\/p>\n <\/div>\n <div class=\"members-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Assign members <\/label> <select disabled class=\"form-control\"> <option value=\"A member or group will be selected here\">A member or group will be selected here<\/option> <\/select>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"test-plan-template--determine-scope\">\n <h2>Test Plan Template - Determine Scope:<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-success\">Use this step to state the purpose of the test plan template. This is where you identify the level of the plan this section is essentially the executive summary.&nbsp;<\/p>\n <\/div>\n<\/section>\n<section id=\"identify-the-scope-of-the-plan\">\n <h2>Identify the scope of the plan<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-info\">Identify the Scope of the Test Plan Template in relation to the overall software project that it relates to.<\/p>\n  <p><strong>Check off the subtasks<\/strong>&nbsp;to<strong> ensure you cover all bases<\/strong> when defining the scope of this test.&nbsp;<\/p>\n  <p>Then, in the <strong>form field<\/strong> below, <strong>summarize the scope<\/strong> of the test.<\/p>\n <\/div>\n <div class=\"multi-select-content form-field-content\">\n  <div class=\"form-group\">\n   <label> (Subtasks) <\/label>\n  <\/div>\n  <ul class=\"items\">\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      1\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Resource and budget constraints\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      2\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     The scope of the testing effort\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      3\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Relation to other evaluation activities\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      4\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     The process to be used for change control\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      5\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     The process to be used for coordination of key activities.\n    <\/div><\/li>\n  <\/ul>\n <\/div>\n <div class=\"textarea-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Summarize scope <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"reference-other-relevant-items\">\n <h2>Reference other relevant items<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-info\">Use this task to include any references to other plans, documents, or items that contain information relevant to this project\/process.<\/p>\n  <p>Note down the <strong>relevance this test has to other items<\/strong> in the<strong> form field<\/strong> below.<\/p>\n <\/div>\n <div class=\"textarea-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Reference to other items <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"test-plan-template--identify-test-items\">\n <h2>Test Plan Template - Identify Test Items:<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-success\">This is where you identify what it is being tested- what you intend to test within the scope of this test plan. In software testing, you will test each code individually, so if you are testing multiple codes you would run this checklist for each piece of code being tested.&nbsp;<\/p>\n <\/div>\n<\/section>\n<section id=\"log-in-to-your-code-repository\">\n <h2>Log in to your code repository<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-info\">Now you need to<strong> log <\/strong>in to<strong> your code repository<\/strong>.&nbsp;<\/p>\n  <p>Whether you use <a href=\"https:\/\/github.com\/\" rel=\"nofollow noopener\" target=\"_blank\">GitHub<\/a>, <a href=\"https:\/\/bitbucket.org\/\" rel=\"nofollow noopener\" target=\"_blank\">Bitbucket<\/a>, or <a href=\"http:\/\/www.cloudforge.com\/\" rel=\"nofollow noopener\" target=\"_blank\">CloudForge<\/a>, (or something entirely different) head on over to your repo of choice and log in to your account.<\/p>\n <\/div>\n <div class=\"select-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Have you logged into your code repository? <\/label> <select disabled class=\"form-control\"> <option value=\"An option will be selected here\">An option will be selected here<\/option> <\/select>\n  <\/div>\n  <ul class=\"items\">\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      1\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Yes \u2705\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      2\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     No \u274c\n    <\/div><\/li>\n  <\/ul>\n <\/div>\n<\/section>\n<section id=\"identify-what-it-is-you-are-testing\">\n <h2>Identify what it is you are testing<\/h2>\n <div class=\"text-content\">\n  <p>Once logged in you will need to find the<strong> relevant fork or branch of code to conduct your tests on<\/strong>. This should be well-documented, and so there should be no confusion as to what you are doing.<\/p>\n  <p><strong>Record a link<\/strong> to the relevant fork or branch using the <strong>form field<\/strong> below.<\/p>\n <\/div>\n <div class=\"text-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Project Link <\/label> <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\">\n  <\/div>\n <\/div>\n <div class=\"text-content\">\n  <p class=\"style-warning\">If you are having trouble finding the relevant code, ensure that you are searching in the correct section of your test environment. Once you've found it, <strong>open up the project<\/strong>. \ud83d\ude80<\/p>\n <\/div>\n<\/section>\n<section id=\"test-plan-template--strategy\">\n <h2>Test Plan Template - Strategy:<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-info\">Now that you have the correct version of code in front of you, the next step is to<strong> identify the area which you will be testing<\/strong>. Much like finding the relevant version of code, this should be fairly obvious, owing to the fact that you should have already know what you are testing.<\/p>\n <\/div>\n<\/section>\n<section id=\"identify-testing-strategy\">\n <h2>Identify testing strategy<\/h2>\n <div class=\"image-content\">\n  <figure>\n   <a href=\"https:\/\/st-process-production.s3.amazonaws.com\/cd9aa8b5-0df6-4960-b41d-2b82efc13c65\/mIg6tL8QHKL1trEynedEhA.png\" alt=\"Test Plan Template\" target=\"_blank\" rel=\"noopener\"> <img decoding=\"async\" loading=\"lazy\" src=\"https:\/\/st-process-production.s3.amazonaws.com\/cd9aa8b5-0df6-4960-b41d-2b82efc13c65\/mIg6tL8QHKL1trEynedEhA.png\"> <\/a>\n   <figcaption>\n    Test Plan Template\n   <\/figcaption>\n  <\/figure>\n <\/div>\n <div class=\"text-content\">\n  <p><strong>Identify the strategy <\/strong>you intend to use as part of this test.<\/p>\n  <p>For example, if you have been assigned the task of unit testing a particular feature, you should have the information to identify where the features codes can be found. Ergo, you can isolate the section of code that has been changed. <strong>Use breakpoints to isolate the area<\/strong> and move on.<\/p>\n  <p class=\"style-success\">Use the <strong>form field below to identify the testing strategy.<\/strong><\/p>\n <\/div>\n <div class=\"textarea-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Testing strategy <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"test-plan-template--criteria\">\n <h2>Test Plan Template - Criteria:<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-success\">What are the completion criteria for this test plan? This is a critical aspect of any test plan, the goal is to identify whether or not a test item (or code) has passed the test process.<\/p>\n <\/div>\n<\/section>\n<section id=\"set-up-the-conditions\">\n <h2>Set up the conditions<\/h2>\n <div class=\"text-content\">\n  <p>In order for your unit test to... perform an actual <em>test<\/em>, you need to <strong>set up the conditions or criteria for it to run<\/strong> on.<\/p>\n  <p class=\"style-info\">Unfortunately, we can't give you a set of conditions to abide by, as this will <em>always<\/em> vary, depending on the test you are running and that specific circumstance.<\/p>\n  <p>We can however give you some pointers,<strong> use the sub checklist<\/strong> below <strong>as a guide<\/strong> to determining your test criteria.<\/p>\n  <p>Then, <strong>record the conditions<\/strong> you specify using the<strong> form field<\/strong> below.<\/p>\n <\/div>\n <div class=\"multi-select-content form-field-content\">\n  <div class=\"form-group\">\n   <label> (Subtasks) <\/label>\n  <\/div>\n  <ul class=\"items\">\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      1\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     All test cases completed\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      2\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     A specified percentage of cases completed with a percentage containing some number of minor defects\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      3\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     The code coverage tool indicates all code covered\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      4\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Enter variables to test a basic function\n    <\/div><\/li>\n  <\/ul>\n <\/div>\n <div class=\"textarea-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Testing criteria <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea>\n  <\/div>\n <\/div>\n <div class=\"text-content\">\n  <p class=\"style-warning\">Make sure that you <strong>double-check<\/strong> these criteria and conditions, as the unit test will be no good if the test itself is broken or calling on incorrect information.<\/p>\n <\/div>\n<\/section>\n<section id=\"test-plan-template--deliverables--tasks\">\n <h2>Test Plan Template - Deliverables &amp; Tasks:<\/h2>\n <div class=\"text-content\">\n  <p><strong>What is to be delivered as part of this plan?&nbsp;<\/strong><\/p>\n  <p><strong>What is your desired outcome of the test?<\/strong><\/p>\n  <p class=\"style-success\">The deliverables or milestones are important as they give the test purpose and something to aim for. For each deliverable, you should assign a task... Think:&nbsp; <em>if this deliverable happens this way then I will run this task.<\/em><\/p>\n <\/div>\n<\/section>\n<section id=\"ensure-that-the-test-verifies-your-results\">\n <h2>Ensure that the test verifies your results<\/h2>\n <div class=\"text-content\">\n  <p>Rather than just testing to see if you can visibly get the desired outcome, your unit test needs to <strong>verify that your predicted outcome takes place<\/strong>.&nbsp;<\/p>\n  <p class=\"style-info\">Once again, the method of implementing this test varies greatly, but in general, just ensure that your unit test specifically confirms that your desired outcome is present. Usually, this will entail the use of a <strong>\"system.assert()\" function<\/strong>.<\/p>\n  <p>Below is a <strong>sub checklist of the possible deliverables<\/strong> you could use to verify your results. Use it <strong>as a guide to choosing your deliverable\/s<\/strong>.<\/p>\n  <p>Then, use the <strong>form field<\/strong> to note down the<strong> deliverables for this test.<\/strong><\/p>\n <\/div>\n <div class=\"multi-select-content form-field-content\">\n  <div class=\"form-group\">\n   <label> (Subtasks) <\/label>\n  <\/div>\n  <ul class=\"items\">\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      1\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test data\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      2\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test plan\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      3\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test design specifications\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      4\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test case specifications\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      5\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test procedure specifications\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      6\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test item transmittal reports\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      7\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test logs\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      8\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test Incident Reports\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      9\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test Summary reports\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      10\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Test Incident reports\n    <\/div><\/li>\n  <\/ul>\n <\/div>\n <div class=\"text-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Record deliverables <\/label> <input type=\"text\" placeholder=\"Something will be typed here...\" disabled class=\"form-control\">\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"assign-a-task-to-each-deliverable\">\n <h2>Assign a task to each deliverable<\/h2>\n <div class=\"text-content\">\n  <p><strong>Assign a task to each deliverable.&nbsp;<\/strong><\/p>\n  <p class=\"style-info\">There should be tasks identified for each test deliverable. Include all inter-task dependencies, skill levels, etc. These tasks should also have corresponding tasks and milestones in the overall software project.<\/p>\n  <p><span style=\"text-decoration: underline;\">To refresh your memory, these are your deliverable\/s:<\/span><\/p>\n  <p>{{form.Record_deliverables}}<\/p>\n  <p>Use the <strong>form field<\/strong> below to <strong>assign a task<\/strong> to each deliverable.<\/p>\n <\/div>\n <div class=\"textarea-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Assign tasks to deliverables <\/label> <textarea placeholder=\"Something will be typed here...\" rows=\"3\" disabled class=\"form-control\"><\/textarea>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"run-the-test\">\n <h2>Run the test<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-success\">So by now, you should have the code under review, the unit test should be written (and double-checked)... meaning that is now <strong>time to run your unit test<\/strong>.<\/p>\n  <p>This will, once again, depend on the kind of test you are running. So, go ahead and<strong> run your test<\/strong> in whichever way <strong>suits<\/strong> your <strong>specific requirements<\/strong>.<\/p>\n <\/div>\n<\/section>\n<section id=\"test-plan-template--assessment\">\n <h2>Test Plan Template - Assessment:<\/h2>\n <div class=\"text-content\">\n  <p class=\"style-success\">Now that you've run your unit test and have the<strong>&nbsp;results<\/strong>, you'll need to <strong>save and organize them<\/strong>. This may be done automatically, depending on your method of testing, but if so then you should still check for the presence of the save. Depending on your specific requirements you may also need to&nbsp;<strong>send these results to a team member&nbsp;<\/strong>or have&nbsp;<strong>the results approved -<\/strong><em><span style=\"text-decoration: underline;\"> the following tasks cover these bases.<\/span><\/em><\/p>\n <\/div>\n<\/section>\n<section id=\"save-your-test-results\">\n <h2>Save your test results<\/h2>\n <div class=\"text-content\">\n  <p><strong>Save and organize your test results here<\/strong>.&nbsp;<\/p>\n  <p class=\"style-success\">By saving your results you can then assign them for approval or send them in an email in the following tasks.<\/p>\n  <p><strong>Upload a copy<\/strong> of your test results to the<strong> form field<\/strong> below.<\/p>\n <\/div>\n <div class=\"file-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Test Results <\/label>\n   <div class=\"file-container\">\n    <button type=\"button\" disabled class=\"btn btn-default\"> <i class=\"fa fa-upload btn-icon\"><\/i> File will be uploaded here <\/button>\n   <\/div>\n  <\/div>\n <\/div>\n <div class=\"text-content\">\n  <p class=\"style-warning\"><strong>Pro-tip: <\/strong>If your unit test does not automatically save your results (and you have not already entered a command at the end of the test to rectify this), you'll need to alter your test code to save the results to a file of your choice. After doing this, re-run your test and ensure that your results have been saved.<\/p>\n <\/div>\n<\/section>\n<section id=\"assess-the-code\">\n <h2>Assess the code<\/h2>\n <div class=\"text-content\">\n  <p>The final step of the test, before sending it off for approval or review, is to<strong> assess your test results<\/strong>. Compare the outputs from the test to what&nbsp;<em>should<\/em> have happened (the deliverables), and if the new code doesn't make the cut, then so be it.<\/p>\n  <p><strong>Record the status<\/strong> of the code using the <strong>dropdown field<\/strong> below.<\/p>\n <\/div>\n <div class=\"select-field-content form-field-content\">\n  <div class=\"form-group\">\n   <label> Code status <\/label> <select disabled class=\"form-control\"> <option value=\"An option will be selected here\">An option will be selected here<\/option> <\/select>\n  <\/div>\n  <ul class=\"items\">\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      1\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Ready to publish\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      2\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Minor edits required\n    <\/div><\/li>\n   <li class=\"item\">\n    <div class=\"step-number-container\">\n     <div class=\"step-number\">\n      3\n     <\/div>\n    <\/div>\n    <div class=\"step-checkbox-container\">\n     <div class=\"step-checkbox\"><\/div>\n    <\/div>\n    <div class=\"item-name-static\">\n     Major edits required\n    <\/div><\/li>\n  <\/ul>\n <\/div>\n<\/section>\n<section id=\"approval-assign-test-for-approval\">\n <h2>Approval: Assign test for approval<\/h2>\n <div class=\"approval-content\">\n  <div class=\"header\">\n   <div class=\"list-title\">\n    Will be submitted for approval:\n   <\/div>\n  <\/div>\n  <div class=\"approval-rule-subject-tasks-list\">\n   <ul class=\"list\">\n    <li>\n     <div class=\"approval-rule-subject-tasks-list-item\">\n      <div class=\"item\">\n       <div class=\"container\">\n        <span class=\"title\">Save your test results<\/span>\n        <div class=\"body\">\n         Will be submitted\n        <\/div>\n       <\/div>\n      <\/div>\n     <\/div><\/li>\n    <li>\n     <div class=\"approval-rule-subject-tasks-list-item\">\n      <div class=\"item\">\n       <div class=\"container\">\n        <span class=\"title\">Assess the code<\/span>\n        <div class=\"body\">\n         Will be submitted\n        <\/div>\n       <\/div>\n      <\/div>\n     <\/div><\/li>\n   <\/ul>\n  <\/div>\n <\/div>\n<\/section>\n<section id=\"send-test-results\">\n <h2>Send test results<\/h2>\n <div class=\"text-content\">\n  <p>Once your test is approved you can <strong>send the results via emai<\/strong>l to your colleagues.&nbsp;<\/p>\n  <p class=\"style-success\"><strong>Use the email widget below to send the test.<\/strong><\/p>\n <\/div>\n<\/section>\n<section id=\"sources\">\n <h2>Sources:<\/h2>\n <div class=\"text-content\">\n  <p><a href=\"https:\/\/www.ecs.csun.edu\/~rlingard\/comp480\/TestPlanTemplate.pdf\" rel=\"nofollow noopener\" target=\"_blank\">Software Quality Engineering - Test Plan Template<\/a><\/p>\n  <p><a href=\"http:\/\/\thttps:\/\/reqtest.com\/testing-blog\/how-to-write-a-test-plan-2\/\" rel=\"nofollow noopener\" target=\"_blank\">Ulf Eriksson - How Can a Test Plan Software Help in IEEE 829 Standard Compliance?<\/a>\u2003<br><br><a href=\"https:\/\/www.profitbricks.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Drue Placette<\/a> -&nbsp;<a href=\"https:\/\/blog.profitbricks.com\/top-source-code-repository-hosts\/\" rel=\"nofollow noopener\" target=\"_blank\">45 of the Top Source Code Repository Hosts<\/a><\/p>\n  <p><a href=\"http:\/\/www.tutorialspoint.com\/\" rel=\"nofollow noopener\" target=\"_blank\">TutorialsPoint<\/a> -&nbsp;<a href=\"http:\/\/www.tutorialspoint.com\/software_testing\/\" rel=\"nofollow noopener\" target=\"_blank\">Software Testing Tutorial<\/a><\/p>\n  <p><a href=\"http:\/\/programmers.stackexchange.com\/\" rel=\"nofollow noopener\" target=\"_blank\">StackExchange<\/a> -&nbsp;<a href=\"http:\/\/programmers.stackexchange.com\/questions\/79068\/what-is-the-difference-between-debugging-and-testing\" rel=\"nofollow noopener\" target=\"_blank\">What is the Difference Between Debugging and Testing? [Thread]<\/a><\/p>\n  <p><a href=\"https:\/\/developer.salesforce.com\/page\/User:Jesse_Lorenz\" rel=\"nofollow noopener\" target=\"_blank\">Jesse Lorenz<\/a> -&nbsp;<a href=\"https:\/\/developer.salesforce.com\/page\/How_to_Write_Good_Unit_Tests\" rel=\"nofollow noopener\" target=\"_blank\">How to Write Good Unit Tests<\/a><\/p>\n  <p><a href=\"http:\/\/stackoverflow.com\/\" rel=\"nofollow noopener\" target=\"_blank\">StackOverflow<\/a> -&nbsp;<a href=\"http:\/\/stackoverflow.com\/questions\/3258733\/new-to-unit-testing-how-to-write-great-tests\" rel=\"nofollow noopener\" target=\"_blank\">New to Unit Testing, How To Write Great Tests? [Closed Thread]<\/a><\/p>\n  <p><a href=\"https:\/\/twitter.com\/tommcfarlin\" rel=\"nofollow noopener\" target=\"_blank\">Tom McFarlin<\/a> -&nbsp;<a href=\"http:\/\/code.tutsplus.com\/articles\/the-beginners-guide-to-unit-testing-what-is-unit-testing--wp-25728\" rel=\"nofollow noopener\" target=\"_blank\">The Beginner\u2019s Guide to Unit Testing: What Is Unit Testing?<\/a><\/p>\n  <p><a href=\"https:\/\/msdn.microsoft.com\/en-us\" rel=\"nofollow noopener\" target=\"_blank\">Microsoft Developer Network<\/a> -&nbsp;<a href=\"https:\/\/msdn.microsoft.com\/en-us\/library\/hh694602.aspx\" rel=\"nofollow noopener\" target=\"_blank\">Unit Test Basics<\/a><\/p>\n  <p><a href=\"http:\/\/blog.stevensanderson.com\/\" rel=\"nofollow noopener\" target=\"_blank\">Steve Sanderson<\/a> -&nbsp;<a href=\"http:\/\/blog.stevensanderson.com\/2009\/08\/24\/writing-great-unit-tests-best-and-worst-practises\/\" rel=\"nofollow noopener\" target=\"_blank\">Writing Great Unit Tests: Best and Worst Practices<\/a><\/p>\n  <p><a href=\"https:\/\/www.toptal.com\/resume\/sergey-kolodiy\" rel=\"nofollow noopener\" target=\"_blank\">Sergey Kolodiy<\/a> -&nbsp;<a href=\"https:\/\/www.toptal.com\/qa\/how-to-write-testable-code-and-why-it-matters\" rel=\"nofollow noopener\" target=\"_blank\">Unit Tests, How to Write Testable Code and Why it Matters<\/a><\/p>\n <\/div>\n<\/section>\n<section id=\"related-checklists\">\n <h2>Related Checklists:<\/h2>\n <div class=\"text-content\">\n  <p><a href=\"https:\/\/www.process.st\/checklist\/git-workflow\/\" target=\"_blank\" rel=\"nofollow noopener\">Git Workflow<\/a><\/p>\n  <p><a href=\"https:\/\/www.process.st\/checklist\/user-story-template\/\" target=\"_blank\" rel=\"nofollow noopener\">User Story Template<\/a><\/p>\n  <p><a href=\"https:\/\/www.process.st\/checklist\/sprint-planning\/\" target=\"_blank\" rel=\"nofollow noopener\">Sprint Planning<\/a><\/p>\n  <p><a href=\"https:\/\/www.process.st\/checklist\/scrum-project-management\/\" target=\"_blank\" rel=\"nofollow noopener\">Scrum Project Management<\/a><\/p>\n  <p><a href=\"https:\/\/www.process.st\/checklist\/software-deployment\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Deployment<\/a><\/p>\n  <p><a href=\"https:\/\/www.process.st\/checklist\/software-debugging-process\/\" target=\"_blank\" rel=\"nofollow noopener\">Software Debugging Process<\/a><\/p>\n <\/div>\n<\/section>\n","protected":false},"excerpt":{"rendered":"<p>Introduction to Test Plan Template: *Disclaimer: This Test Plan Template is based upon a unit test level test. \u201cA test plan is a document describing the scope, approach, resources, and schedule of intended test activities.\u201d &nbsp;ISQTB, Test Plan The Test Plan Template documents and tracks the necessary information required to effectively define the approach to [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":24971,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"ep_exclude_from_search":false,"cover_icon_emoji":"","cover_icon_url":"","tasks_count":"25","template_description":"Run this checklist on a regular basis to ensure blip free functioning of your software and its features.","template_id":"kFNNUsWCVgRiHj34o6dBvg","task_0":"Introduction to Test Plan Template:","task_slug_0":"introduction-to-test-plan-template","task_1":"Preparation:","task_slug_1":"preparation","task_2":"Record the basic details","task_slug_2":"record-the-basic-details","task_3":"Assign team members for inclusion in the test","task_slug_3":"assign-team-members-for-inclusion-in-the-test","task_4":"Test Plan Template - Determine Scope:","task_slug_4":"test-plan-template--determine-scope","task_5":"Identify the scope of the plan","task_slug_5":"identify-the-scope-of-the-plan","task_6":"Reference other relevant items","task_slug_6":"reference-other-relevant-items","task_7":"Test Plan Template - Identify Test Items:","task_slug_7":"test-plan-template--identify-test-items","task_8":"Log in to your code repository","task_slug_8":"log-in-to-your-code-repository","task_9":"Identify what it is you are testing","task_slug_9":"identify-what-it-is-you-are-testing","task_10":"Test Plan Template - Strategy:","task_slug_10":"test-plan-template--strategy","task_11":"Identify testing strategy","task_slug_11":"identify-testing-strategy","task_12":"Test Plan Template - Criteria:","task_slug_12":"test-plan-template--criteria","task_13":"Set up the conditions","task_slug_13":"set-up-the-conditions","task_14":"Test Plan Template - Deliverables & Tasks:","task_slug_14":"test-plan-template--deliverables--tasks","task_15":"Ensure that the test verifies your results","task_slug_15":"ensure-that-the-test-verifies-your-results","task_16":"Assign a task to each deliverable","task_slug_16":"assign-a-task-to-each-deliverable","task_17":"Run the test","task_slug_17":"run-the-test","task_18":"Test Plan Template - Assessment:","task_slug_18":"test-plan-template--assessment","task_19":"Save your test results","task_slug_19":"save-your-test-results","task_20":"Assess the code","task_slug_20":"assess-the-code","task_21":"Approval: Assign test for approval","task_slug_21":"approval-assign-test-for-approval","task_22":"Send test results","task_slug_22":"send-test-results","task_23":"Sources:","task_slug_23":"sources","task_24":"Related Checklists:","task_slug_24":"related-checklists","task_25":"","task_slug_25":"","task_26":"","task_slug_26":"","task_27":"","task_slug_27":"","task_28":"","task_slug_28":"","task_29":"","task_slug_29":"","task_30":"","task_slug_30":"","task_31":"","task_slug_31":"","task_32":"","task_slug_32":"","task_33":"","task_slug_33":"","task_34":"","task_slug_34":"","task_35":"","task_slug_35":"","task_36":"","task_slug_36":"","task_37":"","task_slug_37":"","task_38":"","task_slug_38":"","task_39":"","task_slug_39":"","task_40":"","task_slug_40":"","task_41":"","task_slug_41":"","task_42":"","task_slug_42":"","task_43":"","task_slug_43":"","task_44":"","task_slug_44":"","task_45":"","task_slug_45":"","task_46":"","task_slug_46":"","task_47":"","task_slug_47":"","task_48":"","task_slug_48":"","task_49":"","task_slug_49":"","task_50":"","task_slug_50":"","task_51":"","task_slug_51":"","task_52":"","task_slug_52":"","task_53":"","task_slug_53":"","task_54":"","task_slug_54":"","task_55":"","task_slug_55":"","task_56":"","task_slug_56":"","task_57":"","task_slug_57":"","task_58":"","task_slug_58":"","task_59":"","task_slug_59":"","task_60":"","task_slug_60":"","task_61":"","task_slug_61":"","task_62":"","task_slug_62":"","task_63":"","task_slug_63":"","task_64":"","task_slug_64":"","task_65":"","task_slug_65":"","task_66":"","task_slug_66":"","task_67":"","task_slug_67":"","task_68":"","task_slug_68":"","task_69":"","task_slug_69":"","task_70":"","task_slug_70":"","task_71":"","task_slug_71":"","task_72":"","task_slug_72":"","task_73":"","task_slug_73":"","task_74":"","task_slug_74":"","task_75":"","task_slug_75":"","task_76":"","task_slug_76":"","task_77":"","task_slug_77":"","task_78":"","task_slug_78":"","task_79":"","task_slug_79":"","task_80":"","task_slug_80":"","task_81":"","task_slug_81":"","task_82":"","task_slug_82":"","task_83":"","task_slug_83":"","task_84":"","task_slug_84":"","task_85":"","task_slug_85":"","task_86":"","task_slug_86":"","task_87":"","task_slug_87":"","task_88":"","task_slug_88":"","task_89":"","task_slug_89":"","task_90":"","task_slug_90":"","task_91":"","task_slug_91":"","task_92":"","task_slug_92":"","task_93":"","task_slug_93":"","task_94":"","task_slug_94":"","task_95":"","task_slug_95":"","task_96":"","task_slug_96":"","task_97":"","task_slug_97":"","task_98":"","task_slug_98":"","task_99":"","task_slug_99":"","footnotes":""},"categories":[55,5,31],"tags":[],"class_list":["post-24970","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-corporate-social-responsibility","category-featured","category-software"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/24970","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/comments?post=24970"}],"version-history":[{"count":0,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/posts\/24970\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media\/24971"}],"wp:attachment":[{"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/media?parent=24970"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/categories?post=24970"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.process.st\/templates\/wp-json\/wp\/v2\/tags?post=24970"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}