1 / 8

Test Scheme

Test Scheme. Ⅵ. Requirements Definition and Analysis Phase. Technical Design Phase. Development Phase. Pre-Production Phase. Ⅵ . Test Scheme. Test Process by Stages. Test Requirements Analysis. Project Management Test Requirements Analysis. Test Strategy Establishment.

branxton
Download Presentation

Test Scheme

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Test Scheme Ⅵ

  2. Requirements Definition and Analysis Phase Technical Design Phase Development Phase Pre-Production Phase Ⅵ. Test Scheme Test Process by Stages Test Requirements Analysis Project Management Test Requirements Analysis Test Strategy Establishment Master Test Plan Detailed Test Plan Test Execution Plan Test Execution Plan Test Plan Environment Set-Up Environment Development Test Preparation Performing Tests Test Tool Analysis Test Tool Selection and Installation Unit Test User Acceptance Test Administration Test(Non-Functional) IntegrationTest Test Process Status Report Result Report Result Report Test Completion 298

  3. Purpose of Unit Test Unit Test Execution Factors Unit Test Procedure Defect Test Case and Data Revise test scheme and perform test Defect on Data Debug data and perform test Module Specification Defect or Misinterpretation  Report to PM and PL Repeat execution until the actual result match with expected result on unit test scheme Execute prepared test case and data based on prepared Unit test scheme scenario Ⅵ. Test Scheme Unit Test Unit test is a procedure used to validate that individual units of source code are working properly. Test cases and sample data will be prepared to carry out the test properly. Based on prepared unit test scheme scenario execute the prepared test cases and data • Comply with procedure and standard to induce zero-error program development • Through test scheme check whether there are any disagreements or defects compared to the design specification. • Confirm whether a developer understood detailed design principle and applied the principle Compare actual test result with prepared test scenario result. If two results don’t match, investigate on reason for failure 299

  4. Purpose of Integration Test Integration Test Execution Factors Integration Test Procedure Ⅵ. Test Scheme IntegrationTest Integration test will be carried out to verify the application satisfies functional, performance and reliability requirements placed on major design items. Test cases and sample data will be prepared to carry out the test properly. Based on prepared Integration test scheme scenario execute the prepared test cases and data • Confirm whether the system development is according to the design specification • Test interoperability between individual software modules • Verify performance and reliability requirements are met • Fix bugs in between system interfaces Compare actual test result with prepared test scenario result. If two results don’t match, investigate on reason for failure Minor Defect  After test termination, fix the problem and test Major Defect  After test termination, fix the problem and test Critical Defect  Stop the test, fix the problem and test The test is completed when all test scenarios are passed without any problem. 300

  5. Purpose of UAT UAT Execution Factors UAT Procedure Based on prepared undertaking test scheme scenario execute the prepared test cases and data Compare actual test result with prepared test scenario result. If two results don’t match, investigate on reason for failure Defect Test Case and Data Revise test scheme and perform test Defect on Data Debug data and perform test Defect on Design specification  Revise the design specification and redo from codingprocess The test is completed when all test scenarios are passed without any problem and all non-functional requirements are satisfactorily fulfilled. Ⅵ. Test Scheme User Acceptance Test (UAT) UAT is the final verification of the required business function and proper functioning of the system, emulating real-world usage conditions. • Confirm whether ultimately the system is meeting customer company’s functional needs and quality assurance goal 301

  6. Test Result Test Scope Test Step Test Results, Problems and Issues • Verification of interoperability with external systems • Verification of all functional and non-functional requirements Test-Drive • Testing of non-functional requirements • Verification of integration between functions • Run through test scenarios • Testing of individual modules Integration Test Unit Test • Verification of unit programming function Error Handling Test Management and Maintenance Error Assign developer to fix the error Test Execution Log a ticket Analysis of the error Testing Results Follow up Debug Make sure that details of errors and fixes are recorded Close the ticket Regression Test Upload fixes Ⅵ. Test Scheme Problem and Issue Management Problems and issues found from test results will be categorized and managed until they are corrected to ensure the quality of applications. System Completion Level Test Step Description Unit Test Integration Test Test-Drive 1. Accept user requests on improvement 2. Confirm validity of the technology 3. Inform improvement request to developers 4. Process improvement by developers 5. Execute unit test 6. Report unit test result 1. Accept test result 2. Analyze test result 3. Verification of integration with other systems 4. Test on integration with other systems 5. If there is improvement to make, request for developer 1. Accept integration test result 2. Analyze integration test result 3. Apply Test-Drive procedure 4. Check Test-Drive result 5. If error occurred, request for further analysis Repair Procedure 302

  7. Detailed Test Stage Ⅵ. Test Scheme Test Schedule Unit tests will be carried out as the developers complete each unit and integration test will take place to verify functional requirements as well as integrating with external systems. Below is a suggested test schedule. Customizing in H.K. U.S. H.K. 303

  8. Perform test using development server • Based on administration data establish unit & integration test data • Detect problems prior to the user test and analyze risk factors • Set up test environment similar to the administration environment • Execute unit test using 2 development servers • Set up to concurrently execute unit test and fix detected errors • Install test data from administration system • Before installing undertaking test to the administration system perform rehearsal using test server and training server to minimize errors • Perform undertaking test in an environment separate from administration system • Before undertaking test confirm the version of administration system OS so the test environment is identical to the administration environment 1 1 2 2 Test Data Test Data Ⅵ. Test Scheme Test Environment Unit test and integration test will be performed on development servers but UAT will be performed on the dedicated test servers to emulate real-world environment. Dvlm.Server#1 Dvlm.Server#2 Unit & Integration Test Unit & Integration Test Administration SupportingPC Developer’sPC Unit & Integration Test Environment UATEnvironment Training Server Undertaking Testing PC Test Server UAT tester perform the test in the test environment UAT` Tester who couldn’t participate in the test in the test environment connect to the test server and training server from a remote location to perform the UAT UAT Remote location 304

More Related