{"id":8615,"date":"2018-05-04T05:25:27","date_gmt":"2018-05-04T05:25:27","guid":{"rendered":"http:\/\/www.esds.co.in\/blog\/?p=8615"},"modified":"2021-03-03T11:08:56","modified_gmt":"2021-03-03T11:08:56","slug":"manual-testing-process-lifecycle","status":"publish","type":"post","link":"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/","title":{"rendered":"Manual Testing &#8211; Process Lifecycle"},"content":{"rendered":"\n<h1 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Software_Testing_Life_Cycle\"><\/span>Software Testing Life Cycle<span class=\"ez-toc-section-end\"><\/span><\/h1>\n\n\n\n<div class=\"wp-block-image\"><figure class=\"aligncenter size-full\"><a href=\"https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing.jpg\"><img loading=\"lazy\" decoding=\"async\" width=\"1200\" height=\"628\" src=\"https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing.jpg\" alt=\"Software Testing Life Cycle\" class=\"wp-image-8616\" srcset=\"https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing.jpg 1200w, https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing-150x79.jpg 150w, https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing-300x157.jpg 300w, https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing-1024x536.jpg 1024w, https:\/\/www.esds.co.in\/blog\/wp-content\/uploads\/2018\/05\/Mannual-Testing-660x345.jpg 660w\" sizes=\"auto, (max-width: 1200px) 100vw, 1200px\" \/><\/a><\/figure><\/div>\n\n\n\n<h2 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Manual_Software_Testing\"><\/span>Manual Software Testing<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p>Manual Testing is a process of finding out the defects, bugs in a software program. A tester performs the end-user role and verifies if all the features are working properly or not. Tester manually executes the test cases. Manual testing is the process of using the features of an application as an end-user. With manual testing, a tester manually conducts tests on the <strong><a href=\"https:\/\/www.esds.co.in\/softwares\" target=\"_blank\" rel=\"noreferrer noopener\">software<\/a><\/strong>. This process is carried out to find defects\/bugs. Manual Testing is a basic type of testing in the application under test.<\/p><div id=\"ez-toc-container\" class=\"ez-toc-v2_0_76 counter-hierarchy ez-toc-counter ez-toc-grey ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><a href=\"#\" class=\"ez-toc-pull-right ez-toc-btn ez-toc-btn-xs ez-toc-btn-default ez-toc-toggle\" aria-label=\"Toggle Table of Content\"><span class=\"ez-toc-js-icon-con\"><span class=\"\"><span class=\"eztoc-hide\" style=\"display:none;\">Toggle<\/span><span class=\"ez-toc-icon-toggle-span\"><svg style=\"fill: #999;color:#999\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" class=\"list-377408\" width=\"20px\" height=\"20px\" viewBox=\"0 0 24 24\" fill=\"none\"><path d=\"M6 6H4v2h2V6zm14 0H8v2h12V6zM4 11h2v2H4v-2zm16 0H8v2h12v-2zM4 16h2v2H4v-2zm16 0H8v2h12v-2z\" fill=\"currentColor\"><\/path><\/svg><svg style=\"fill: #999;color:#999\" class=\"arrow-unsorted-368013\" xmlns=\"http:\/\/www.w3.org\/2000\/svg\" width=\"10px\" height=\"10px\" viewBox=\"0 0 24 24\" version=\"1.2\" baseProfile=\"tiny\"><path d=\"M18.2 9.3l-6.2-6.3-6.2 6.3c-.2.2-.3.4-.3.7s.1.5.3.7c.2.2.4.3.7.3h11c.3 0 .5-.1.7-.3.2-.2.3-.5.3-.7s-.1-.5-.3-.7zM5.8 14.7l6.2 6.3 6.2-6.3c.2-.2.3-.5.3-.7s-.1-.5-.3-.7c-.2-.2-.4-.3-.7-.3h-11c-.3 0-.5.1-.7.3-.2.2-.3.5-.3.7s.1.5.3.7z\"\/><\/svg><\/span><\/span><\/span><\/a><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1 ' ><li class='ez-toc-page-1 ez-toc-heading-level-1'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Software_Testing_Life_Cycle\" >Software Testing Life Cycle<\/a><ul class='ez-toc-list-level-2' ><li class='ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Manual_Software_Testing\" >Manual Software Testing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Software_testing_process_flow\" >Software testing process flow<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Requirement_SRS_ReviewAnalysis\" >Requirement (SRS Review\/Analysis)<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Test_Plan_Creation\" >Test Plan Creation<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Actual_Testing\" >Actual Testing<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-7\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Before_Release\" >Before Release<\/a><\/li><\/ul><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-8\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Steps_in_Requirements_to_Release\" >Steps in Requirements to Release<\/a><ul class='ez-toc-list-level-3' ><li class='ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-9\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Writing_of_Test_Cases\" >Writing of Test Cases<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-10\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Decision_to_release_the_product\" >Decision to release the product<\/a><ul class='ez-toc-list-level-4' ><li class='ez-toc-heading-level-4'><a class=\"ez-toc-link ez-toc-heading-11\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Conclusion\" >Conclusion<\/a><\/li><\/ul><\/li><li class='ez-toc-page-1 ez-toc-heading-level-3'><a class=\"ez-toc-link ez-toc-heading-12\" href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/#Whats_best_for_ESDS\" >What&#8217;s best for ESDS?<\/a><\/li><\/ul><\/li><\/ul><\/li><\/ul><\/nav><\/div>\n\n\n\n\n<h2 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Software_testing_process_flow\"><\/span><strong>Software testing process flow<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<h4 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Requirement_SRS_ReviewAnalysis\"><\/span><strong>Requirement (SRS Review\/Analysis)<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>A software requirements specification (SRS) is a document that contains a complete description of how the system is expected to perform. After completing, it is signed off at the end of the requirements. SRS review is nothing but going through the functional requirements specification document and trying to understand what the target application is going to be like.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Challenges<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>We cannot gather all information at one time<\/li><li>Lots of discussions needed<\/li><li>Sometimes the speed of discussion would be too fast or too slow to understand<\/li><\/ul>\n\n\n\n<p class=\"has-text-align-left\"><strong>Best Practice<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>We should pay attention and listen carefully<\/li><li>Keep note book or laptop for writing notes<\/li><li>Draw diagram or rough block code for better understanding and for reference<\/li><\/ul>\n\n\n\n<h4 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Test_Plan_Creation\"><\/span><strong>Test Plan Creation<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>It\u2019s a document developed by the test manager. It is a set of ideas that guide and is created to inform all the managers, testers, developers about the testing process.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Challenges<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Strategy is not the thing which can be changed frequently<\/li><li>It has very high importance<\/li><\/ul>\n\n\n\n<p class=\"has-text-align-left\"><strong>Best Practice<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Make list of different environment where applications can be deployed<\/li><li>Make a list of all the third party tools needed for application<\/li><li>List of all Operating system like Win 7, Win 10, Win Server<\/li><\/ul>\n\n\n\n<p>Test plan contains detailed understanding of workflow. It consist test templates which has introduction, scope, test strategy, environment requirements, test schedule, functions to be tested, resources and responsibilities, deliverables,&nbsp;suspension\/ exit criteria, resumption criteria, dependencies, risks, tools, documentation and approvals.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Challenges<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Success or failure will depend upon how the test is been carried out. This phase is important in testing software life cycle.<\/li><\/ul>\n\n\n\n<p class=\"has-text-align-left\"><strong>Best Practice<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Create a matrix environment where the software can be tested in all environments.<\/li><li>Configure the test setups for Win 7, Win 8, Win 10 and Android<\/li><li>Keep the databases (MySQL, Oracle, SQLServer) in the test matrix in such a way that they are too integrated with some test.<\/li><\/ul>\n\n\n\n<h4 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Actual_Testing\"><\/span>Actual Testing<span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>In this phase, the application build is ready and out to find bugs. Actual testing is done and bugs are reported. Testing is done in many ways like Functional (Unit testing, Integration testing, Smoke, Localization), Non-Functional (Performance, volume, Load), Maintenance (Regression).<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Challenges<\/strong><\/p>\n\n\n\n<p>Testing is a heavy process which itself is error regrettable! One finds many challenges while testing an application.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Best Practice<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Follow navigation path of software (AUT)<\/li><li>Ask doubt to developer before going to product owner<\/li><li>Take help of developer when required<\/li><\/ul>\n\n\n\n<h4 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Before_Release\"><\/span>Before Release<span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>Before releasing the software in the market, quality of product is ensured. Once a software is built, it is tested several times.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Challenges<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>Software should be tested carefully in many parameters i.e. functional, behavioural, performance and scalability.<\/li><\/ul>\n\n\n\n<p class=\"has-text-align-left\"><strong>Best Practice<\/strong><\/p>\n\n\n\n<ul class=\"wp-block-list\"><li>All the features on all platform should be tested<\/li><li>Highlight the data which is not tested<\/li><li>Application health card should be present to stakeholder<\/li><\/ul>\n\n\n\n<h2 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Steps_in_Requirements_to_Release\"><\/span><strong>Steps in Requirements to Release<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"has-text-align-left\"><strong>SRS Review<\/strong><\/p>\n\n\n\n<p>SRS is a description of a software&nbsp;system to be developed. It contains functional and non-functional&nbsp;requirements.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Objectives<\/strong><\/p>\n\n\n\n<p>Objectives are set for major and minor releases.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Target Date<\/strong><\/p>\n\n\n\n<p>Target date is the date in which the build is released<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Detailed Project Plan<\/strong><\/p>\n\n\n\n<p>Detailed Project Plan is nothing but the project build, it includes design and decision specifications<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Develop Test Plan<\/strong><\/p>\n\n\n\n<p>Develop Test Plan is&nbsp;based on design specifications<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Test Plan<\/strong><\/p>\n\n\n\n<p>This includes objectives, testing schedule, the methodology adopted while testing, features to be and not to be tested, multi-platform support risk criteria, and the resource allocation for testing.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Test Specifications<\/strong><\/p>\n\n\n\n<p>Test Specifications document includes technical details (software requirements)&nbsp;required prior to testing.<\/p>\n\n\n\n<h3 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Writing_of_Test_Cases\"><\/span><strong>Writing of Test Cases<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Test cases are of different types like smoke test cases, sanity test case, regression tests cases, negative test cases<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Development<\/strong><\/p>\n\n\n\n<p>In the development phase modules are developed one by one<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Installers Binding<\/strong><\/p>\n\n\n\n<p>It is used for building individual product<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Build procedure<\/strong><\/p>\n\n\n\n<p>A build includes Installers of the available products \u2013 multiple platforms.<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Testing<\/strong><\/p>\n\n\n\n<p>Testing of new features. Cross browser and cross platform testing. Stress testing and memory leakage testing<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Test summary report<\/strong><\/p>\n\n\n\n<p>Test report, bug and other report are created in Test summary report<\/p>\n\n\n\n<p class=\"has-text-align-left\"><strong>Code freezing<br><\/strong><\/p>\n\n\n\n<p>In Code freezing no more lines of code can be added<\/p>\n\n\n\n<h3 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Decision_to_release_the_product\"><\/span><strong>Decision to release the product<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p>Here decision is made to release or postponed release of the product<\/p>\n\n\n\n<h4 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Conclusion\"><\/span><strong>Conclusion<\/strong><span class=\"ez-toc-section-end\"><\/span><\/h4>\n\n\n\n<p>The existence of both manual testing and automation testing forces us to think about our choice of tools, their cost, and the&nbsp;benefit they will provide. There&nbsp;is a time and place for both methods of testing. Manual testing helps us understand the entire problem and explore other angles of tests with flexibility. Automated testing helps save time in the long run by&nbsp;accomplishing a large number of surface level tests in a short time. It\u2019s up to you to determine when and where each method of testing is used.<\/p>\n\n\n\n<h3 class=\"has-text-align-center wp-block-heading\"><span class=\"ez-toc-section\" id=\"Whats_best_for_ESDS\"><\/span>What&#8217;s best for ESDS?<span class=\"ez-toc-section-end\"><\/span><\/h3>\n\n\n\n<p><a href=\"https:\/\/www.esds.co.in\">ESDS<\/a> is involved in manual testing since 2 years including functional testing, smoke testing, regression testing, sanity testing, unit testing, integration testing and system testing.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Software Testing Life Cycle Manual Software Testing Manual Testing is a process of finding out the defects, bugs in a software program. A tester performs the end-user role and verifies if all the features are working properly or not. Tester manually executes the test cases. Manual testing is the process of using the features of&#8230; <\/p>\n<div class=\"clear\"><\/div>\n<p><a href=\"https:\/\/www.esds.co.in\/blog\/manual-testing-process-lifecycle\/\" class=\"gdlr-button small excerpt-read-more\">Read More<\/a><\/p>\n","protected":false},"author":53,"featured_media":8616,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[187],"tags":[1717,1722,1712,1715,1714,1719,1720,1718,1713,1723,1716,1721],"class_list":["post-8615","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-general","tag-functional-testing","tag-integration-testing","tag-manual-testing","tag-manual-testing-lifecycle","tag-manual-testing-process-lifecycle","tag-regression-testing","tag-sanity-testing","tag-smoke-testing","tag-software-testing","tag-system-testing","tag-testing","tag-unit-testing"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/posts\/8615","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/users\/53"}],"replies":[{"embeddable":true,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/comments?post=8615"}],"version-history":[{"count":8,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/posts\/8615\/revisions"}],"predecessor-version":[{"id":11859,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/posts\/8615\/revisions\/11859"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/media\/8616"}],"wp:attachment":[{"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/media?parent=8615"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/categories?post=8615"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.esds.co.in\/blog\/wp-json\/wp\/v2\/tags?post=8615"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}