{"id":231,"date":"2026-02-26T19:45:21","date_gmt":"2026-02-26T19:45:21","guid":{"rendered":"https:\/\/sites.nd.edu\/softwaretesting\/?page_id=231"},"modified":"2026-03-03T20:26:12","modified_gmt":"2026-03-03T20:26:12","slug":"testing-process","status":"publish","type":"page","link":"https:\/\/sites.nd.edu\/softwaretesting\/testing-process\/","title":{"rendered":"Testing Process"},"content":{"rendered":"\n<p>Testing is a structured process that ensures software meets its functional, non-functional, and business requirements. The process typically follows several key stages:<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"1024\" height=\"243\" src=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Testing-Process-1-1024x243.jpg\" alt=\"\" class=\"wp-image-235\" srcset=\"https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Testing-Process-1-1024x243.jpg 1024w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Testing-Process-1-300x71.jpg 300w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Testing-Process-1-768x182.jpg 768w, https:\/\/sites.nd.edu\/softwaretesting\/files\/2026\/02\/Testing-Process-1.jpg 1292w\" sizes=\"auto, (max-width: 1024px) 100vw, 1024px\" \/><\/figure>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>1. Review Requirements<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Understand what the software is supposed to do, including functional, non-functional, and business requirements.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Analyze requirement documents, user stories, and acceptance criteria<\/li>\n\n\n\n<li>Identify testable elements<\/li>\n\n\n\n<li>Highlight ambiguous or missing requirements<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: A clear understanding of what needs to be validated.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>2. Formulate Test Strategy<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Define the overall approach for testing, including scope, objectives, types of testing, resources, tools, and schedule.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Determine testing techniques to be employed<\/li>\n\n\n\n<li>Allocate roles and responsibilities<\/li>\n\n\n\n<li>Define testing metrics to be created<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: A clear plan for testing activities.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>3. Develop Test Cases<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Design detailed, executable steps to verify each requirement.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Create test cases or scripts with inputs, expected results, and success criteria<\/li>\n\n\n\n<li>Map test cases to requirements<\/li>\n\n\n\n<li>Prioritize test cases based on risk and criticality<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: A comprehensive set of test cases ready for execution.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>4. Ensure Environment Setup<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Prepare the technical environment where testing will occur.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Ensure that any needed servers, databases, and software products exist and have been configured in the Test environment<\/li>\n\n\n\n<li>Confirm access and permissions for testers<\/li>\n\n\n\n<li>Ensure tools for test management and defect tracking are operational<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: A stable and production-like environment ready for testing.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>5. Create Test Data<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Provide realistic and comprehensive data for testing scenarios.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Generate sample or anonymized production data<\/li>\n\n\n\n<li>Include normal, boundary, and invalid inputs<\/li>\n\n\n\n<li>Ensure data covers all business workflows<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: Test data that allows thorough verification of all scenarios.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>6. Execute Test Cases<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Run test cases to validate system behavior and detect defects.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Execute planned tests cases<\/li>\n\n\n\n<li>Record actual results and compare with expected outcomes<\/li>\n\n\n\n<li>Log defects and communicate issues to development teams<\/li>\n\n\n\n<li>Re-test fixed defects (regression testing)<\/li>\n\n\n\n<li>Communicate test metrics (coverage, pass\/fail rates)<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: A validated system with identified and addressed defects.<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong><em>7. Close Testing<\/em><\/strong><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Purpose<\/strong>: Formally conclude testing activities and document results.<\/li>\n\n\n\n<li><strong>Activities<\/strong>:\n<ul class=\"wp-block-list\">\n<li>Verify all planned tests are executed<\/li>\n\n\n\n<li>Ensure all defects are resolved or accepted<\/li>\n\n\n\n<li>Provide input to the Project Summary<\/li>\n\n\n\n<li>Archive test artifacts for compliance or future reference<\/li>\n<\/ul>\n<\/li>\n\n\n\n<li><strong>Key Outcome<\/strong>: A formally tested system and documented evidence supporting release decisions.<\/li>\n<\/ul>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Testing is a structured process that ensures software meets its functional, non-functional, and business requirements. The process typically follows several key stages: 1. Review Requirements 2. Formulate Test Strategy 3. Develop Test Cases 4. Ensure Environment Setup 5. Create Test Data 6. Execute Test Cases 7. Close Testing<\/p>\n","protected":false},"author":4975,"featured_media":0,"parent":0,"menu_order":1,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-231","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages\/231","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/users\/4975"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/comments?post=231"}],"version-history":[{"count":4,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages\/231\/revisions"}],"predecessor-version":[{"id":417,"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/pages\/231\/revisions\/417"}],"wp:attachment":[{"href":"https:\/\/sites.nd.edu\/softwaretesting\/wp-json\/wp\/v2\/media?parent=231"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}