Alesh Dulal

DemoTest Plan Master Test Plan General Information Client Demo Prepared By Alesh Dulal Preparation Date February 12, 2021 Version 1.0.0 Status Completed Test Plan Identifier Demo_01 This test plan is the basis for formally testing Demo and contains a detailed understanding of the eventual workflow. Revision Version Revision History Version 1.0.0 Description - Created a test plan Author Date Alesh Dulal 04/18/2022 Approved By Author Date 1 Table of Contents Table of Contents 2 Introduction 3 Features to Be Tested 3 Testing Strategy Inscope Exploratory Testing Functional Testing Usability Testing(UI/UX Testing) Out Scope 4 4 4 4 4 4 Schedule 4 Risk and Assumptions Assumptions Risks 4 4 5 Test Environments 5 Roles and Responsibilities 6 Test Deliverables 6 Entry and Exit Criteria Entry Criteria Exit Criteria 7 7 7 2 Introduction This test plan is a comprehensive guide for the testing process. This document defines the strategy that will be used to verify that the product/system is developed according to its specifications and requirements. The plan includes the features to be tested, testing strategy to be implemented, test environments, schedule, test deliverables, roles, and responsibilities of the overall team towards building a quality product, and assumptions and risks to complete testing. Features to Be Tested Pages Features My Salary - Edit Salary Report Companies near you Average Salary by Location Jobs - Jobs near me Jobs details Test Cases # 3 Testing Strategy The following strategies will be done one after another to the test system: Inscope Exploratory Testing Before maintaining the test cases for the listed features the exploratory testing will be done on the system. Later while performing this test the tester will determine the test cases and list the cases. The main motive of this test on Demo_Project is to uncover the bugs that are normally ignored by other testing techniques. Functional Testing All the features mentioned on features to be tested will be tested. Test cases for every feature will be maintained in a shared google drive folder. Positive as well as negative testing will be listed in test cases. Bugs and improvements if any will be maintained in a document and will be prioritized on the basis of the criticality of the issue. Usability Testing(UI/UX Testing) Demo will be tested keeping actual users into consideration so that users don’t feel much complexity while using the system. UI/UX issues will be minimized as much as possible with this testing. Out Scope Schedule Task Schedule Test Cases In parallel with the development cycle on the sprint basis Test Execution After deployment of every new features in QA environment Bug Report At the end of the testing Risk and Assumptions Assumptions The following assumptions are made to achieve our testing goal and maintain the quality of the product: ● It is assumed that sprint planning is done correctly so that development will meet release dates. 4 ● It is assumed that story points are allocated correctly for every task so that there is enough time for developing and testing. ● It is assumed that there won’t be late requirement changes. ● It is assumed that all the blocker issues are given with high priority. ● We assume that team members have the necessary experience and training in the system, the project, and the testing process. ● We assume that the development team will deliver the features as per the scheduled date in terms of development and hotfixes ensuring that there is no blocker issue while testing. Risks S.N. Risk Impact Trigger Mitigation Plan 1 The developer may misunderstand the requirement and they might add wrong actions on any features being developed. High ● Increase in the number of bugs ● Delay on the sprint delivery Point to point understanding of the feature being developed. Provide sprint tickets to developers before the sprint starts. Developers should interact with project managers or stakeholders to understand the requirement. 1 Last-minute requirement changes may occur which will impact the development process and cause obsolescence of already written test cases. High ● Delay in the development process ● Loss of all test cases Requirements should be discussed and finalized before the sprint gets started. 2 Design mockups may not be ready for selected features for development. High ● The development process will slow down Designs for the following sprints should be prepared beforehand. 3 Estimations may not be accurate all the time. High ● Some features may not be ready to release and pushed to the next sprints Story points must be estimated incorporating the time needed to perform code reviews too. No feature should be selected for development until its requirement is clear to the team. 5 Test Environments Environment Details Server DEV, QA, UAT, Staging Browsers Chrome, Safari, Firefox, Edge, Opera Tools ---- Operating System macOS, Linux, Windows Mobile iOS 12, Android 5.0 and above Roles and Responsibilities This section helps to identify the key roles and responsibilities of the peoples involved in the Quality Assurance process for delivering a quality product. The responsibilities listed are not for the overall Project workflow but only related to quality assurance activities. Roles Stakeholders QA Responsibilities ● Keeping this section because this is important in real scenario ● ● ● ● ● ● Understand the requirements properly Prepare Test Plan and follow it Prepare Test Cases Execute the test cases Generate test report Report bugs, performance issues, and possible enhancements Project Manager Keeping this section because this is important in real scenario Software Developers Keeping this section because this is important in real scenario Designers Keeping this section because this is important in real scenario Test Deliverables Items Test Plan Description This Document 6 Test Cases Test cases for every feature mentioned will be prepared and added under the Test Cases document in google drive. Test Report Test reports of all the test cases will be created and uploaded in google drive Demo Quality Assurance section with proper visualization. Bug Report Bugs in case found will be listed in the Bug Report document and will be prioritized according to priority and severity. Entry Criteria and Exit Criteria Entry Criteria 1. 2. 3. 4. The development of the specific feature is completed. The test case document preparation is completed and all the checklists are prepared. The test environment has been set up. All necessary resources are available and are ready to be used for testing. Exit Criteria 1. 2. 3. 4. 5. All the test cases are executed. The rate of tests cases passed is satisfactory, e.g., 95% The failed test cases are not related to crucial functionality. The tests results have been accepted. Critical defects that have been reported are fixed. 7