Bài tập lớn Kiểm tra phần mềm - Website quản lý trung tâm tin học

Nội dung text: Bài tập lớn Kiểm tra phần mềm - Website quản lý trung tâm tin học

1. Table of Contents 1. Introduction 3 1.1 Purpose 3 1.3 Intended Audience 3 1.4 Document Terminology and Acronyms 3 1.5 References 3 2. Evaluation Mission and Test Motivation 4 2.1 Background 4 2.2 Evaluation Mission 4 2.2 Test Motivators 4 3. Target Test Items 4 5. Test Approach 4 5.1 Function Testing 5 5.2 User Interface Testing 5 6. Entry and Exit Criteria 5 6.1 Test Plan Entry Criteria 5 6.2 Test Plan Exit Criteria 5 7. Deliverables 5 8. Testing Workflow 5 9. Environmental Needs 6 9.1 Base System Hardware 6 9.2 Base Software Elements in the Test Environment 6 9.3 Productivity and Support Tools 6 9.4 Test Environment Configurations 7 10. Responsibilities, Staffing, and Training Needs 7 10.1 People and Roles 7 10.2 Staffing and Training Needs 9 12. Risks, Dependencies, Assumptions, and Constraints 9 12.1 Risks 9 12.1.1 Schedule 9 12.1.2. Management 9 12.1.3. Personnel 9 12.1.4 Requirements 9 12.2 Dependencies 9 12.2.1 Personnel Dependencies 9 12.2.2 Software Dependencies 9 12.2.3 Test Data & Database 9 13. Management Process and Procedures 10 13.1 Reviews 10 13.2 Bug Review meetings 10 13.3 Defect Reporting 10 14 Documentation 10 15 Approvals 10
2. - certify to a standard - verify a specification (requirements, design or claims) - advise about product quality, satisfy stakeholders - advise about testing - fulfill process mandates 2.2 Test Motivators Q&A team members will be motivated by some key factors - Quality risks - Technical risks - Five use cases those must be tested - Functional requirements - Non-functional requirements - Design elements - Suspected failures or faults 3. Target Test Items The listing below identifies those test items; software, hardware, and supporting product elements that have been identified as targets for testing. This list represents what items will be tested. - Build a test project which include Plan Test, Design Test Cases, Execute Test, Report Test - Realize a test plan, realize all components in test plan completely, in addition o Define features to be tested and features not to be test in tested plan clearly o Define functions those to be tested and not to be tested ( just test only five use cases) - Just only write the necessary test cases for five use cases - Inspect by the way relying on written test cases, record bugs in bug tracking system - Give the report 4. Features to Be Tested 4.1 Student management - Search information - Update data - Insert data - Delete data - GUI to report in test report file 4.2 Long-term education management - Search information - Update data - Insert data - Delete data - GUI to report in test report file 4.3 Short-term education management - Search information - Update data - GUI to report in test report file 4.4 Desire management - Search information
3. 8. Testing Workflow - Verify the result from implementation by testing each build - Plan the tests in each iteration - Design and implement tests by creating - Perform the tests and systematically handle the test results - Test model artifacts ✓ Test cases ✓ Test procedures ✓ Test components ✓ Test subsystem packages for complex test models’ - Other artifacts ✓ Test Plan ✓ Defects ✓ Test Evaluation 9. Environmental Needs 9.1 Base System Hardware System resources that need for the test effort presented in this Test Plan are: - Database server - CPUs core 2dual 2.0; Ram 2GB 9.2 Base Software Elements in the Test Environment The following base software elements are required in the test environment for this Test Plan. Software Element Name Version Type and Other Notes Windows XP 2;3 Operating System Windows Vista Operating System Window 7 Operating System MS SQL Server database J2EE Platform java Network Associates McAfee Virus Checker Virus Detection and Recovery Software 9.3 Productivity and Support Tools The following tools will be employed to support the test process for this Test Plan. Tool Category or Type Tool Brand Name Vendor or In-house Version Test Management Defect Tracking ASQ Tool for functional testing ASQ Tool for performance testing Test Coverage Monitor or Profiler Project Management
4. Test Designer Defines the technical approach to the implementation of the test effort. Responsibilities include: define test approach define test automation architecture verify test techniques define testability elements structure test implementation Tester Implements and executes the tests. Responsibilities include: implement tests and test suites execute test suites log results analyze and recover from test failures document incidents Test System Administrator Ensures test environment and assets are managed and maintained. Responsibilities include: administer test management system install and support access to, and recovery of, test environment configurations and test labs Database Administrator, Ensures test data (database) environment and Database Manager assets are managed and maintained. Responsibilities include: support the administration of test data and test beds (database). Designer Identifies and defines the operations, attributes, and associations of the test classes. Responsibilities include: defines the test classes required to support testability requirements as defined by the test team Implementer Implements and unit tests the test classes and test packages. Responsibilities include: creates the test components required to support testability requirements as defined by the designer 10.2 Staffing and Training Needs
5. 13.3 Defect Reporting When defects are found, the testers will complete a defect report on the defect tracking system. The defect tracking systems is accessible by testers, developers & all members of the project team. When a defect has been fixed or more information is needed, the developer will change the status of the defect to indicate the current state. Once a defect is verified as FIXED by the testers, the testers will close the defect report. 14 Documentation The following documentation will be available at the end of the test phase: • Test Plan • Test Cases • Test Case review • Defect reports • Final Test Summary Report 15 Approvals Name (Print) Signature Date