kiểm tra phần mềm nguyễn văn hiệp test plan xây dựng hệ thống quản lý tài liệu truc tuyen sinhvienzone com

1 ASSIGNMENT SOFTWARE-TESTING Test Plan Table of content Vi en Zo ne C om References Introduction Test Items Software Risk Issues Features to be tested Features not to be tested Test Strategies Item Pass/Fail Criteria Environmental Needs 10 Test Deliverables nh Group members: Tran Hoang Duy 50601095 Truong Quang Khai 50600939 Bui Phi Hung 50601490 Nguyễn Trường Minh Si 50600357 SinhVienZone.com https://fb.com/sinhvienzonevn 10 11 12 Si nh Vi en Zo ne C om SinhVienZone.com https://fb.com/sinhvienzonevn REFERENCES No NAME Location AVAILABLE Test plan template www.google.com.vn Slide Si nh Vi en Zo ne C om http://www.cse.hcmut.edu.vn/~minhnnn SinhVienZone.com https://fb.com/sinhvienzonevn INTRODUCTION [Topics introduction] “BUILDING ONLINE DOCUMENT MANAGEMENT SYSTEM” [Give an overview of the plan: Zo ne The summary of the requirements List what needs to be achieved (test objectives) Detail why testing needed.] C om 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 en The summary of the features will be tested : Si nh Vi General Functions:  View company documents (TC: man-days, Test: man-days)  View department documents (TC: man-days, Test: 1.5 man-days)  Grant privilege (TC: man-days, Test: 0.5 man-days)  Manager personal documents (TC: man-days, Test: 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: man-days, Test: man-days)  Upload one or many documents (TC: man-days, Test: man-days)  Search documents (TC: man-days, Test: man-days) [Testing purpose] List what needs to be achieved and details why testing needed : Test all of auxiliary tasks Estimate project performance SinhVienZone.com https://fb.com/sinhvienzonevn TEST ITEMS [List of Software Items to be tested, their versions and how they are handed over for testing] Si nh Vi en Zo ne C om A build of Project Version 1.0 Teacher send to my group Project and installations as Testing Software Assignment SinhVienZone.com https://fb.com/sinhvienzonevn 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: om 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] C Lack of personnel resources: We have persons while the system has about tasks must be tested ne Lack of availability of required hardware, software, data or tools : Zo  Hardware:  Software: en We have about PCs Vi OS : Unix , Windows Xp , Windows run in VMware workstation Web browsers: Internet Explored ,7,8 and Mozilla FireFox nh  Data: OK Si  Tools: We have no some tools for doing performance test , usability test and security test SinhVienZone.com https://fb.com/sinhvienzonevn Si nh Vi en Zo ne C om SinhVienZone.com https://fb.com/sinhvienzonevn 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] View department documents Grant privilege Manager personal documents View profile om nh individual Si ne Zo View company documents Extent of Testing Vi Risk Priority C Feature Description Business Risk en Feature No Technical Risk Change password Share documents Upload one or many documents Search documents Total Estimated Testing Time SinhVienZone.com https://fb.com/sinhvienzonevn Estimated Testing Time (hours) FEATURES NOT TO BE TESTED [List all features will not be tested under this test plan] Feature No Feature Description Technical Risk Business Risk Risk Priority Extent of Testing Estimated Testing Time (hours) Performance Usability Security Si nh Vi en Zo ne C om SinhVienZone.com https://fb.com/sinhvienzonevn Si nh Vi en Zo ne C om 10 SinhVienZone.com https://fb.com/sinhvienzonevn 11 TEST STRATEGIES om [The Test Strategy presents the recommended approach to the testing the target-of-test The previous section, feature to be tested, described what will be tested, this section describes how the target-of-test will be tested For each type of test, provide a description of the test and why it is being implemented and executed If a type of test will not be implemented and executed, indicate in a sentence stating the test will not be implemented / executed and stating the justification, such as “This test will not be implemented / executed This test is not appropriate …” The main considerations for the test strategy are the techniques to be used and the criterion for knowing when the testing is completed In addition to the considerations provided for each test below, testing should only be executed using known, controlled databases, in secured environments In addition, you need to describe: nh Vi en Zo ne C Testing Tools/Aids Constrains to testing Support Required – Environment & Staffing What metrics will be collected? Which level is each metric to be collected at? How is Configuration Management to be handled? How many different configurations will be tested? Hardware Software Combinations of HW, SW and other vendor packages What levels of regression testing will be done and how much at each test level? Will regression testing be based on severity of defects detected? How will elements in the requirements and design that not make sense or are untestable be processed?] Si 7.1 Function Testing [Function testing of the target-of-test should focus on any requirements for test that can be traced directly to use cases (or business functions), and business rules The goals of these tests are to verify proper data acceptance, processing, and retrieval, and the appropriate implementation of the business rules This type of testing is based upon black box techniques, that is, verifying the application (and its internal processes) by interacting with the application via the GUI and analyzing the output (results) Identified below is an outline of the testing recommended for each application:] Test Objective: Ensure proper target-of-test functionality, including navigation, data entry, processing Security , performance and retrieval will not tested SinhVienZone.com https://fb.com/sinhvienzonevn 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 [Identify / describe those items or issues (internal or external) that impact the implementation and execution of function test] om Special Considerations: C 7.2 Performance Testing en Zo ne [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.] nh Si Technique: Ensure search speed less than 10 seconds Vi Test Objective: Completion Criteria: 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 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: SinhVienZone.com In assignment requirements hasn’t performance test https://fb.com/sinhvienzonevn 13 ITEM PASS/FAIL CRITERIA C om [This section of the test plan describes the pass/fail criteria for each of the items described in Section Test Items Typically, pass/fail criteria are expressed in terms of test cases passed and failed; number, type, severity and location of bugs; usability, reliability, and/or stability Examples of pass/fail criteria include: % of test cases passed number, severity, and distribution of defects test case coverage successful conclusion of user test completion of documentation performance criteria.] Si nh Vi en Zo ne TestCase Result SinhVienZone.com https://fb.com/sinhvienzonevn 14 ENVIRONMENTAL NEEDS [List all testing environments needed] System Resources Resource Name / Type Windown XP Operating system Firefox (all of version) Browsers Si nh Vi en Zo ne C om IE SinhVienZone.com https://fb.com/sinhvienzonevn 15 10 TEST DELIVERABLES [List all documents can be delivered such as: Test Plan, Test cases, Test Reports etc] [List all test scripts can be delivered] No Document Type Assigned To Tran Hoang Duy (50600357) Nguyen Phi Hung (50600939) Test Plan om Nguyen Truong Minh (50601490) C Truong Quang Khai (50601095) Design : Tran Hoang Duy (50600357) TestCase Excute : Truong Quang Khai (50601095) Si nh Vi en Zo Installation ne Tran Hoang Duy (50600357) SinhVienZone.com https://fb.com/sinhvienzonevn ... performance test , usability test and security test SinhVienZone. com https://fb .com/ sinhvienzonevn Si nh Vi en Zo ne C om SinhVienZone. com https://fb .com/ sinhvienzonevn FEATURES TO BE TESTED [List... Estimated Testing Time SinhVienZone. com https://fb .com/ sinhvienzonevn Estimated Testing Time (hours) FEATURES NOT TO BE TESTED [List all features will not be tested under this test plan] Feature... SinhVienZone. com https://fb .com/ sinhvienzonevn 11 TEST STRATEGIES om [The Test Strategy presents the recommended approach to the testing the target-of -test The previous section, feature to be tested, described