Bài tập lớn Kiểm tra phần mềm - Xây dựng hệ thống quản lý tài liệu trực tuyến

Nội dung text: Bài tập lớn Kiểm tra phần mềm - Xây dựng hệ thống quản lý tài liệu trực tuyến

1. 4 2. INTRODUCTION [Topics introduction] “BUILDING ONLINE DOCUMENT MANAGEMENT SYSTEM” Manager Vietnamese Documents Allow user searching documents by semantic , by word key and by combination System is based on JSP and Struts Framework 1.3.10 technology Run on Internet Explorer or Mozilla FireFox. System must ensure search speeds less than 10 seconds System can distribute documents access to users. [Give an overview of the plan: • The summary of the requirements. • List what needs to be achieved (test objectives) • Detail why testing needed.] The summary of the features will be tested : General Functions: ➢ View company documents (TC: 4 man-days, Test: 2 man-days) ➢ View department documents (TC: 2 man-days, Test: 1.5 man-days) ➢ Grant privilege (TC: 1 man-days, Test: 0.5 man-days) ➢ Manager personal documents (TC: 2 man-days, Test: 1 man-days) Common Functions: ➢ View individual profile (TC: 0.5 man-days, Test: 0.5 man-days) ➢ Change password (TC: 0.5 man-days, Test: 0.5 man-days) ➢ Share documents (TC: 5 man-days, Test: 3 man-days) ➢ Upload one or many documents (TC: 2 man-days, Test: 1 man-days) ➢ Search documents (TC: 2 man-days, Test: 1 man-days) [Testing purpose] List what needs to be achieved and details why testing needed : Test all of auxiliary tasks. Estimate project performance.
2. 6 4. SOFTWARE RISK ISSUES [List all software Risks. These risks are related to the testing process, other risks will be mentioned in section 5.Features to be tested. Below are some common risks: • Lack of personnel resources when testing is to begin. • Lack of availability of required hardware, software, data or tools. • Late delivery of the software, hardware or tools. • Delays in training on the application and/or tools. • Changes to the original requirements or designs. • Complexities involved in testing the applications] Lack of personnel resources: We have 2 persons while the system has about 9 tasks must be tested. Lack of availability of required hardware, software, data or tools : ➢ Hardware: We have about 2 PCs. ➢ Software: OS : Unix , Windows Xp , Windows 7 run in VMware workstation Web browsers: Internet Explored 6 ,7,8 and Mozilla FireFox. ➢ Data: OK. ➢ Tools: We have no some tools for doing performance test , usability test and security test.
3. 8 5. FEATURES TO BE TESTED [List all features will be tested under this test plan • Identify risks for each feature by their likelihood and impact and then determine the extent of testing. • Identify testing efforts for each type of test] Technical Business Risk Extent of Estimated Risk Risk Priority Testing Testing Feature No Feature Description Time (hours) View company 1 documents View department 2 documents 3 Grant privilege Manager personal 4 documents View individual 5 profile 6 Change password 7 Share documents Upload one or many 8 documents 9 Search documents Total Estimated Testing Time
4. 12 Technique: Execute each use case, use case flow, or function, using valid and invalid data, to verify the following: • The expected results occur when valid data is used. • The appropriate error / warning messages are displayed when invalid data is used. • Each business rule is properly applied. Completion Criteria: • All planned tests have been executed. • All identified defects have been addressed. Special Considerations: [Identify / describe those items or issues (internal or external) that impact the implementation and execution of function test] 7.2 Performance Testing [Performance profiling is a performance test in which response times, transaction rates, and other time sensitive requirements are measured and evaluated. The goal of Performance Profiling is to verify performance requirements have been achieved. Performance profiling is implemented and executed to profile and tune a target-of-test's performance behaviors as a function of conditions such as workload or hardware configurations. NOTE: Transactions below refer to “logical business transactions.” These transactions are defined as specific use cases that an actor of the system is expected to perform using the target-of-test, such as add or modify a given contract.] Test Objective: Ensure search speed less than 10 seconds Technique: Use Test Procedures developed for Function Cycle Testing. Modify data files (to increase the number of transactions) or the scripts to increase the number of iterations each transaction occurs. Many users access at the same time. Completion Criteria: Single Transaction / single user: Successful completion of the test scripts without any failures and within the expected / required time allocation (per transaction) Multiple transactions / multiple users: Successful completion of the test scripts without any failures and within acceptable time allocation. Special Considerations: In assignment requirements hasn’t performance test.
5. 14 9. ENVIRONMENTAL NEEDS [List all testing environments needed] System Resources Resource Name / Type Windown XP Operating system Firefox (all of version) Browsers IE 7