Bài tập lớn Kiểm tra phần mềm - Công cụ tạo đề thi trắc nghiệm

Nội dung text: Bài tập lớn Kiểm tra phần mềm - Công cụ tạo đề thi trắc nghiệm

1. TEST PLAN FOR “CÔNG CỤ TẠO ĐỀ THI TRẮC NGHIỆM” ___ INDEX 1. OVERVIEW 1.1 Product name 1.2 Product revision 1.3 Project lead 1.4 Test project staff 1.5 Product overview 2. TEST PLAN OBJECTIVE 3. TESTING STRATEGY 3.1 System test 3.2 Performance test 3.3 Stress and volume test 3.4 Recovery test 3.5 Documentation test 3.6 Installation test General testing process approach • Items to be tested • Items not to be tested 4. HARDWARE / SOFTWARE RESOURCES 4.1 Hardware requirements 4.2 Software requirements 4.3 Reference material 5. TYPE OF TESTING 5.1 Feature test • Features to be tested • Features not to be tested 5.2 Installation test 6. RISKS AND CONTINGENCIES 7. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS 8. TEST SCHEDULE AND RESOURCES 8.1 Test schedule 8.2 Resources 9. ROLES AND RESPONSIBILITIES 10. DELIVERABLES Group 4 – Software testing Page 2 12/30/2022
2. TEST PLAN FOR “CÔNG CỤ TẠO ĐỀ THI TRẮC NGHIỆM” ___ 3.1 System Test The System tests will focus on the behavior of the visualizing system. User scenarios will be executed against the system as well as screen interacting and error message testing. Overall, the system tests will test the integrated system and verify that it meets the requirements defined in the requirements document. 3.2 Performance Test Performance test will be conducted to ensure that the visualizing system’s response time meet the user expectations and does not exceed the specified performance criteria. During these tests, response times will be measured under heavy stress and/or volume. 3.3 Stress and Volume Test We will subject the payroll system to high input conditions and a high volume of data during the peak times. 3.4 Recovery Test Recovery tests will force the system to fail in a various ways and verify the recovery is properly performed. It is vitally important that all data is recovered after a system failure & no corruption of the data occurred. 3.5 Documentation Test Tests will be conducted to check the accuracy of the output Microsoft word documentation. These tests will ensure that no features are missing, and the contents can be easily understood. 3.6 Installation Test The application will be installed on some environments (Windows XP SP2, SP3 and Windows Vista) and we will check its compatibility with those environments. In the other hand, we will test the process of removing the application from the system. General Testing Process Approach 1. Review project document. 2. Design test strategy and Determine test requirements. 3. Create test plan. 4. Design test case template. 5. Design and build test case. 6. Execute test plan. 7. Create test report. 3.7. Items to be tested 3.7.1. “Soạn câu hỏi” function. 3.7.2. “Sinh đề thi” function. 3.7.3. “Quản lý kỳ thi/Bộ đề” function. 3.8. Items not to be Tested 3.8.1. “Quản lý môn học / Chương mục” function. Group 4 – Software testing Page 4 12/30/2022
3. TEST PLAN FOR “CÔNG CỤ TẠO ĐỀ THI TRẮC NGHIỆM” ___ - Delete existing question in exam question - Update order of question in exam question - View exam question ‘s solution - Delete all questions in exam question - Automatically create exam question. - Manually create exam question 5.1.1.3. “Quản lý kỳ thi / bộ đề”function - Create new examination - Delete existing examination - Mix all questions in “question book” - Add question to “question book”. - To export Microsoft Word document. 5.1.2. Features not to be tested: 5.1.2.1. Application building 5.1.2.2. Stop running application 5.1.2.3. Vietnamese support 5.1.2.4. Copyright, license 5.2. INSTALLATION TEST 5.2.1. Build program while current Windows is updating. 5.2.2. Redo all test case in Futures testing while Windows is updating. 6. RISKS AND CONTINGENCIES STT Risk Contingency plan 1 Requirement changes affect to human Re-edit test plan to meet new requirements resources and test strategy 2 Application is not able to be built on Re-build in other PCs and testing team must time follow the schedule strictly 3 Virus effectively Highlight this to every one in team, update newest version for anti virus program 4 Executed test case lost Hand in executed testcase report / document to team leader by the end of day via e-mail 7. SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS Suspension criteria: Group 4 – Software testing Page 6 12/30/2022
4. TEST PLAN FOR “CÔNG CỤ TẠO ĐỀ THI TRẮC NGHIỆM” ___ Recommended Test leader 30% Provides management oversight Đỗ Xuân chung Responsibilities: • Provide Technical direction • Acquire appropriate resources • Management reporting • Ensure test environment and assets are managed and mantained. Test Designer Identifies, prioritizes, and implement test cases Đỗ Xuân Chung 30% Responsibilities: Phạm Đức Long 50% • Generate test case Nguyễn Thái Vân Long 50% • Evaluate effectiveness of test effort Trịnh Xuân Khoa 50% • Prepare test data Tester Execute the tests Đỗ Xuân Chung 40% Responsibilities: Phạm Đức Long 50% • Execute tests Nguyễn Thái Vân Long 50% • Log results Trịnh Xuân Khoa 50% • Recover from errors • Document defects 10. DELIVERABLES Deliverable Responsibility Completion Date Develop Test cases Testers 15/06/10 Test Case Review Test Leader, Testers 16/06/10 Execute manual Test Leader, Testers 19/06/10 Complete Defect Reports Test Leader, Testers 19/06/10 Group 4 – Software testing Page 8 12/30/2022