Company NameTest PlanRevision CFor

Company Name
Test Plan

Revision C

For more Testing/QA Templates please visit http://www.softwaretestinghelp.com

Revision History

DATE REV AUTHOR DESCRIPTION
5/14/07 A First Draft
5/21/07 B Second Draft
5/25/07 C Added FTBT

Table of Contents

1. Introduction 4
1.1. Test Plan Objectives 4
2. Scope 4
2.1. Data Entry 4
2.2. ReportsFile Transfer 4
2.3. File Transfer 4
2.4. Security 4
3. Test Strategy 5
3.1. System Test 5
3.2. Performance Test 5
3.3. Security Test 5
3.4. Automated Test 5
3.5. Stress and Volume Test 5
3.6. Recovery Test 5
3.7. Documentation Test 5
3.8. Beta Test 5
3.9. User Acceptance Test 5
4. Environment Requirements 6
4.1. Data Entry workstations 6
4.2 MainFrame 6
5. Test Schedule 6
6. Control Procedures 6
6.1 Reviews 6
6.2 Bug Review meetings 6
6.3 Change Request 6
6.4 Defect Reporting 6
7. Functions To Be Tested 7
8. Resources and Responsibilities 7
8.1. Resources 7
8.2. Responsibilities 7
9. Deliverables 8
10. Suspension / Exit Criteria 9
11. Resumption Criteria 9
12. Dependencies 9
12.1 Personnel Dependencies 9
12.2 Software Dependencies 9
12.3 Hardware Dependancies 9
12.3 Test Data & Database 9
13. Risks 9
13.1. Schedule 9
13.2. Technical 9
13.3. Management 9
13.4. Personnel 10
13.5 Requirements 10
14. Tools 10
15. Documentation 10
16. Approvals 11

1. Introduction

The company has outgrown its current payroll system & is developing a new system that will allow for further growth and provide additional features. The software test department has been tasked with testing the new system.

The new system will do the following:
 Provide the users with menus, directions & error messages to direct him/her on the various options.
 Handle the update/addition of employee information.
 Print various reports.
 Create a payroll file and transfer the file to the mainframe.
 Run on the Banyan Vines Network using IBM compatible PCs as data entry terminals
1.1. Test Plan Objectives
This Test Plan for the new Payroll System supports the following objectives:
 Define the activities required to prepare for and conduct System, Beta and User Acceptance testing.
 Communicate to all responsible parties the System Test strategy.
 Define deliverables and responsible parties.
 Communicate to all responsible parties the various Dependencies and Risks

2. Scope
2.1. Data Entry
The new payroll system should allow the payroll clerks to enter employee information from IBM compatible PC workstations running DOS 3.3 or higher. The system will be menu driven and will provide error messages to help direct the clerks through various options.
2.2. Reports
The system will allow the payroll clerks to print 3 types of reports. These reports are:
 A pay period transaction report
 A pay period exception report
 A three month history report
2.3. File Transfer
Once the employee information is entered into the LAN database, the payroll system will allow the clerk to create a payroll file. This file can then be transferred, over the network, to the mainframe.
2.4. Security
Each payroll clerk will need a userid and password to login to the system. The system will require the clerks to change the password every 30 days.

3. Test Strategy
The test strategy consists of a series of different tests that will fully exercise the payroll system. The primary purpose of these tests is to uncover the systems limitations and measure its full capabilities. A list of the various planned tests and a brief explanation follows below.
3.1. System Test
The System tests will focus on the behavior of the payroll system. User scenarios will be executed against the system as well as screen mapping 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 payroll system’s response times 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. Security Test
Security tests will determine how secure the new payroll system is. The tests will verify that unauthorized user access to confidential data is prevented.
3.4. Automated Test
A suite of automated tests will be developed to test the basic functionality of the payroll system and perform regression testing on areas of the systems that previously had critical/major defects. The tool will also assist us by executing user scenarios thereby emulating several users.

3.5. Stress and Volume Test
We will subject the payroll system to high input conditions and a high volume of data during the peak times. The System will be stress tested using twice (20 users) the number of expected users.
3.6. 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 payroll data is recovered after a system failure & no corruption of the data occurred.
3.7. Documentation Test
Tests will be conducted to check the accuracy of the user documentation. These tests will ensure that no features are missing, and the contents can be easily understood.
3.8. Beta Test
The Payroll department will beta tests the new payroll system and will report any defects they find. This will subject the system to tests that could not be performed in our test environment.
3.9. User Acceptance Test
Once the payroll system is ready for implementation, the Payroll department will perform User Acceptance Testing. The purpose of these tests is to confirm that the system is developed according to the specified user requirements and is ready for operational use.

4. Environment Requirements
4.1. Data Entry workstations
 20 IBM compatible PCs (10 will be used by the automation tool to emulate payroll clerks).
 286 processor (minimum)
 4mb RAM
 100 mb Hard Drive
 DOS 3.3 or higher
 Attached to Banyan Vines network
 A Network attached printer
 20 user ids and passwords (10 will be used by the automation tool to emulate payroll clerks).

4.2 MainFrame
 Attached to the Banyan Vines network
 Access to a test database (to store payroll information transferred from LAN payroll system)

5. Test Schedule
 Ramp up / System familiarization 6/01/07 - 6/15/07
 System Test 6/16/07 - 8/26/07
 Beta Test 7/28/07 - 8/18/07
 User Acceptance Test 8/29/07 - 9/03/07

6. Control Procedures
6.1 Reviews
The project team will perform reviews for each Phase. (i.e. Requirements Review, Design Review, Code Review, Test Plan Review, Test Case Review and Final Test Summary Review). A meeting notice, with related documents, will be emailed to each participant.
6.2 Bug Review meetings
Regular weekly meeting will be held to discuss reported defects. The development department will provide status/updates on all defects reported and the test department will provide addition defect information if needed. All member of the project team will participate.
6.3 Change Request
Once testing begins, changes to the payroll system are discouraged. If functional changes are required, these proposed changes will be discussed with the Change Control Board (CCB). The CCB will determine the impact of the change and if/when it should be implemented.
6.4 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.

7. Functions To Be Tested
The following is a list of functions that will be tested:

 Add/update employee information
 Search / Lookup employee information
 Escape to return to Main Menu
 Security features
 Scaling to 700 employee records
 Error messages
 Report Printing
 Creation of payroll file
 Transfer of payroll file to the mainframe
 Screen mappings (GUI flow). Includes default settings
 FICA Calculation
 State Tax Calculation
 Federal Tax Calculation
 Gross pay Calculation
 Net pay Calculation
 Sick Leave Balance Calculation
 Annual Leave Balance Calculation

A Requirements Validation Matrix will “map” the test cases back to the requirements. See Deliverables.
8. Resources and Responsibilities
The Test Lead and Project Manager will determine when system test will start and end. The Test lead will also be responsible for coordinating schedules, equipment, & tools for the testers as well as writing/updating the Test Plan, Weekly Test Status reports and Final Test Summary report. The testers will be responsible for writing the test cases and executing the tests. With the help of the Test Lead, the Payroll Department Manager and Payroll clerks will be responsible for the Beta and User Acceptance tests.
8.1. Resources
The test team will consist of:
 A Project Manager
 A Test Lead
 5 Testers
 The Payroll Department Manager
 5 Payroll Clerks

8.2. Responsibilities
Project Manager Responsible for Project schedules and the overall success of the project. Participate on CCB.

Lead Developer Serve as a primary contact/liaison between the development department and the project team.
Participate on CCB.

Test Lead Ensures the overall success of the test cycles. He/she will coordinate weekly meetings and will communicate the testing status to the project team.
Participate on CCB.

Testers Responsible for performing the actual system testing.

Payroll Department Manager Serves as Liaison between Payroll department and project team. He/she will help coordinate the Beta and

Company Name
Test Plan

Revision C

For more Testing/QA Templates please visit http://www.softwaretestinghelp.com

Revision History

DATE REV AUTHOR DESCRIPTION
5/14/07 A First Draft
5/21/07 B Second Draft
5/25/07 C Added FTBT

Table of Contents

1. Introduction 4
1.1. Test Plan Objectives 4
2. Scope 4
2.1. Data Entry 4
2.2. ReportsFile Transfer 4
2.3. File Transfer 4
2.4. Security 4
3. Test Strategy 5
3.1. System Test 5
3.2. Performance Test 5
3.3. Security Test 5
3.4. Automated Test 5
3.5. Stress and Volume Test 5
3.6. Recovery Test 5
3.7. Documentation Test 5
3.8. Beta Test 5
3.9. User Acceptance Test 5
4. Environment Requirements 6
4.1. Data Entry workstations 6
4.2 MainFrame 6
5. Test Schedule 6
6. Control Procedures 6
6.1 Reviews 6
6.2 Bug Review meetings 6
6.3 Change Request 6
6.4 Defect Reporting 6
7. Functions To Be Tested 7
8. Resources and Responsibilities 7
8.1. Resources 7
8.2. Responsibilities 7
9. Deliverables 8
10.  Suspension / Exit Criteria 9
11. Resumption Criteria 9
12. Dependencies 9
12.1 Personnel Dependencies 9
12.2 Software Dependencies 9
12.3 Hardware Dependancies 9
12.3 Test Data & Database 9
13. Risks 9
13.1. Schedule 9
13.2. Technical 9
13.3. Management 9
13.4. Personnel 10
13.5 Requirements 10
14. Tools 10
15. Documentation 10
16. Approvals 11

1. Introduction

The company has outgrown its current payroll system & is developing a new system that will allow for further growth and provide additional features. The software test department has been tasked with testing the new system.

The new system will do the following:
 Provide the users with menus, directions & error messages to direct him/her on the various options.
 Handle the update/addition of employee information.
 Print various reports.
 Create a payroll file and transfer the file to the mainframe.
 Run on the Banyan Vines Network using IBM compatible PCs as data entry terminals
1.1. Test Plan Objectives
This Test Plan for the new Payroll System supports the following objectives:
 Define the activities required to prepare for and conduct System, Beta and User Acceptance testing.
 Communicate to all responsible parties the System Test strategy.
 Define deliverables and responsible parties.
 Communicate to all responsible parties the various Dependencies and Risks

2. Scope
2.1. Data Entry
The new payroll system should allow the payroll clerks to enter employee information from IBM compatible PC workstations running DOS 3.3 or higher. The system will be menu driven and will provide error messages to help direct the clerks through various options.
2.2. Reports
The system will allow the payroll clerks to print 3 types of reports. These reports are:
 A pay period transaction report
 A pay period exception report
 A three month history report
2.3. File Transfer
Once the employee information is entered into the LAN database, the payroll system will allow the clerk to create a payroll file. This file can then be transferred, over the network, to the mainframe.
2.4. Security
Each payroll clerk will need a userid and password to login to the system. The system will require the clerks to change the password every 30 days.

3. Test Strategy
The test strategy consists of a series of different tests that will fully exercise the payroll system. The primary purpose of these tests is to uncover the systems limitations and measure its full capabilities. A list of the various planned tests and a brief explanation follows below.
3.1. System Test
The System tests will focus on the behavior of the payroll system. User scenarios will be executed against the system as well as screen mapping 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 payroll system’s response times 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. Security Test
Security tests will determine how secure the new payroll system is. The tests will verify that unauthorized user access to confidential data is prevented.
3.4. Automated Test
A suite of automated tests will be developed to test the basic functionality of the payroll system and perform regression testing on areas of the systems that previously had critical/major defects. The tool will also assist us by executing user scenarios thereby emulating several users.

3.5. Stress and Volume Test 
We will subject the payroll system to high input conditions and a high volume of data during the peak times. The System will be stress tested using twice (20 users) the number of expected users.
3.6. 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 payroll data is recovered after a system failure & no corruption of the data occurred. 
3.7. Documentation Test 
Tests will be conducted to check the accuracy of the user documentation. These tests will ensure that no features are missing, and the contents can be easily understood. 
3.8. Beta Test
The Payroll department will beta tests the new payroll system and will report any defects they find. This will subject the system to tests that could not be performed in our test environment. 
3.9. User Acceptance Test
Once the payroll system is ready for implementation, the Payroll department will perform User Acceptance Testing. The purpose of these tests is to confirm that the system is developed according to the specified user requirements and is ready for operational use.

4. Environment Requirements
4.1. Data Entry workstations
 20 IBM compatible PCs (10 will be used by the automation tool to emulate payroll clerks).
 286 processor (minimum)
 4mb RAM
 100 mb Hard Drive
 DOS 3.3 or higher
 Attached to Banyan Vines network
 A Network attached printer
 20 user ids and passwords (10 will be used by the automation tool to emulate payroll clerks).

4.2 MainFrame
 Attached to the Banyan Vines network
 Access to a test database (to store payroll information transferred from LAN payroll system)

5. Test Schedule
 Ramp up / System familiarization  6/01/07 - 6/15/07
 System Test 6/16/07 - 8/26/07
 Beta Test 7/28/07 - 8/18/07 
 User Acceptance Test 8/29/07 - 9/03/07

6. Control Procedures
6.1 Reviews
The project team will perform reviews for each Phase. (i.e. Requirements Review, Design Review, Code Review, Test Plan Review, Test Case Review and Final Test Summary Review). A meeting notice, with related documents, will be emailed to each participant.
6.2 Bug Review meetings
Regular weekly meeting will be held to discuss reported defects. The development department will provide status/updates on all defects reported and the test department will provide addition defect information if needed. All member of the project team will participate.
6.3 Change Request
Once testing begins, changes to the payroll system are discouraged. If functional changes are required, these proposed changes will be discussed with the Change Control Board (CCB). The CCB will determine the impact of the change and if/when it should be implemented.
6.4 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.

7. Functions To Be Tested
The following is a list of functions that will be tested:

 Add/update employee information
 Search / Lookup employee information
 Escape to return to Main Menu
 Security features
 Scaling to 700 employee records
 Error messages
 Report Printing
 Creation of payroll file
 Transfer of payroll file to the mainframe
 Screen mappings (GUI flow). Includes default settings
 FICA Calculation
 State Tax Calculation
 Federal Tax Calculation
 Gross pay Calculation
 Net pay Calculation
 Sick Leave Balance Calculation
 Annual Leave Balance Calculation

A Requirements Validation Matrix will “map” the test cases back to the requirements. See Deliverables.
8. Resources and Responsibilities
The Test Lead and Project Manager will determine when system test will start and end. The Test lead will also be responsible for coordinating schedules, equipment, & tools for the testers as well as writing/updating the Test Plan, Weekly Test Status reports and Final Test Summary report. The testers will be responsible for writing the test cases and executing the tests. With the help of the Test Lead, the Payroll Department Manager and Payroll clerks will be responsible for the Beta and User Acceptance tests.
8.1. Resources
The test team will consist of:
 A Project Manager
 A Test Lead 
 5 Testers
 The Payroll Department Manager
 5 Payroll Clerks

8.2. Responsibilities
 Project Manager Responsible for Project schedules and the overall success of the project. Participate on CCB.
 
 Lead Developer Serve as a primary contact/liaison between the development department and the project team.
Participate on CCB.
 
 
 Test Lead Ensures the overall success of the test cycles. He/she will coordinate weekly meetings and will communicate the testing status to the project team.
Participate on CCB.
 
 Testers Responsible for performing the actual system testing.
 
 Payroll Department Manager Serves as Liaison between Payroll department and project team. He/she will help coordinate the Beta and

0/5000

Từ: -

Sang: -

Kết quả (Việt) 1: [Sao chép]

Sao chép!

Tên doanh nghiệpThử nghiệm kế hoạchPhiên bản CĐể thêm mẫu thử nghiệm/bảo đảm chất lượng, hãy truy cập http://www.softwaretestinghelp.comLịch sử sửa đổiNGÀY REV TÁC GIẢ MÔ TẢ5/14/07 bản dự thảo đầu tiên5/21/07 B thứ hai dự thảo5/25/07 C bổ sung FTBT Bảng nội dung1. giới thiệu 41.1. kiểm tra các mục tiêu kế hoạch 42. phạm vi 42.1. nhập dữ liệu 42.2. ReportsFile chuyển 42.3. tập tin chuyển 42.4. an ninh 43. kiểm tra chiến lược 53.1. Hệ thống thử nghiệm 53.2. hiệu suất thử nghiệm 53.3. an ninh kiểm tra 53.4. tự động thử nghiệm 53.5. căng thẳng và kiểm tra khối lượng 53.6. phục hồi thử nghiệm 53.7. tài liệu thử nghiệm 53.8. thử nghiệm Beta 53.9. người dùng chấp nhận thử nghiệm 54. môi trường yêu cầu 64.1. các máy trạm làm việc cho các mục nhập dữ liệu 64.2 máy tính lớn 65. kiểm tra lịch trình 66. kiểm soát quy trình 66.1 đánh giá 66.2 cuộc họp lỗi đánh giá 66.3 thay đổi yêu cầu 66.4 lỗi báo cáo 67. chức năng để thử nghiệm 78. tài nguyên và trách nhiệm 78.1. nguồn lực 78.2. trách nhiệm 79. phân phôi 810. tạm dừng / thoát khỏi tiêu chuẩn 911. vòng tiêu chí 912. phụ thuộc 912,1 nhân sự phụ thuộc 912.2 phần mềm phụ thuộc 912.3 phần cứng Dependancies 912.3 kiểm tra dữ liệu & cơ sở dữ liệu 913. rủi ro 913.1. lịch trình 913.2. 9 kỹ thuật13,3. quản lý 913.4. nhân viên 1013,5 yêu cầu 1014. công cụ 1015. tài liệu hướng dẫn 1016. chấp thuận 11 1. giới thiệuCông ty đã outgrown hệ thống biên chế hiện tại của nó và đang phát triển một hệ thống mới sẽ cho phép cho biết thêm sự phát triển và cung cấp các tính năng bổ sung. Bộ phận kiểm tra phần mềm đã được giao nhiệm vụ với các thử nghiệm hệ thống mới.Hệ thống mới sẽ thực hiện như sau: cung cấp cho người dùng với thực đơn, hướng dẫn & lỗi thông điệp trực tiếp anh/cô ấy vào các tùy chọn khác nhau. xử lý bổ sung/Cập nhật các thông tin nhân viên. In báo cáo khác nhau. Tạo một tập tin biên chế và chuyển các tập tin vào máy tính lớn. Chạy trên Banyan Vines mạng bằng cách sử dụng máy tính tương thích IBM là thiết bị đầu cuối mục nhập dữ liệu1.1. kiểm tra các mục tiêu kế hoạchThử nghiệm này kế hoạch cho các hệ thống mới hỗ trợ các mục tiêu sau đây: xác định các hoạt động cần thiết để chuẩn bị cho và tiến hành hệ thống, phiên bản Beta và người dùng chấp nhận thử nghiệm. truyền đạt cho tất cả các bên chịu trách nhiệm các chiến lược thử nghiệm hệ thống. xác định phân phôi và bên chịu trách nhiệm. giao tiếp với tất cả các bên chịu trách nhiệm khác nhau phụ thuộc và rủi ro2. phạm vi2.1. dữ liệu nhậpHệ thống biên chế mới nên cho phép nhân viên biên chế để nhập thông tin nhân viên từ máy trạm máy tính tương thích IBM chạy DOS 3.3 hoặc cao hơn. Hệ thống sẽ là menu hướng và sẽ cung cấp thông báo lỗi để giúp chỉ đạo các nhân viên thông qua các tùy chọn khác nhau.2.2. báo cáoHệ thống sẽ cho phép nhân viên biên chế in 3 loại báo cáo. Các báo cáo này là: A trả báo cáo thời gian giao dịch A pay period exception report A three month history report2.3. File TransferOnce the employee information is entered into the LAN database, the payroll system will allow the clerk to create a payroll file. This file can then be transferred, over the network, to the mainframe.2.4. SecurityEach payroll clerk will need a userid and password to login to the system. The system will require the clerks to change the password every 30 days. 3. Test StrategyThe test strategy consists of a series of different tests that will fully exercise the payroll system. The primary purpose of these tests is to uncover the systems limitations and measure its full capabilities. A list of the various planned tests and a brief explanation follows below.3.1. System TestThe System tests will focus on the behavior of the payroll system. User scenarios will be executed against the system as well as screen mapping 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 TestPerformance test will be conducted to ensure that the payroll system’s response times 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. Security TestSecurity tests will determine how secure the new payroll system is. The tests will verify that unauthorized user access to confidential data is prevented.3.4. Automated TestA suite of automated tests will be developed to test the basic functionality of the payroll system and perform regression testing on areas of the systems that previously had critical/major defects. The tool will also assist us by executing user scenarios thereby emulating several users.3.5. Stress and Volume Test We will subject the payroll system to high input conditions and a high volume of data during the peak times. The System will be stress tested using twice (20 users) the number of expected users.3.6. 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 payroll data is recovered after a system failure & no corruption of the data occurred. 3.7. Documentation Test Tests will be conducted to check the accuracy of the user documentation. These tests will ensure that no features are missing, and the contents can be easily understood. 3.8. Beta TestThe Payroll department will beta tests the new payroll system and will report any defects they find. This will subject the system to tests that could not be performed in our test environment. 3.9. User Acceptance TestOnce the payroll system is ready for implementation, the Payroll department will perform User Acceptance Testing. The purpose of these tests is to confirm that the system is developed according to the specified user requirements and is ready for operational use.4. Environment Requirements4.1. Data Entry workstations 20 IBM compatible PCs (10 will be used by the automation tool to emulate payroll clerks). 286 processor (minimum) 4mb RAM 100 mb Hard Drive DOS 3.3 or higher Attached to Banyan Vines network A Network attached printer 20 user ids and passwords (10 will be used by the automation tool to emulate payroll clerks).4.2 MainFrame Attached to the Banyan Vines network Access to a test database (to store payroll information transferred from LAN payroll system)5. Test Schedule Ramp up / System familiarization 6/01/07 - 6/15/07 System Test 6/16/07 - 8/26/07 Beta Test 7/28/07 - 8/18/07  User Acceptance Test 8/29/07 - 9/03/076. Control Procedures6.1 ReviewsThe project team will perform reviews for each Phase. (i.e. Requirements Review, Design Review, Code Review, Test Plan Review, Test Case Review and Final Test Summary Review). A meeting notice, with related documents, will be emailed to each participant.6.2 Bug Review meetingsRegular weekly meeting will be held to discuss reported defects. The development department will provide status/updates on all defects reported and the test department will provide addition defect information if needed. All member of the project team will participate.6.3 Change RequestOnce testing begins, changes to the payroll system are discouraged. If functional changes are required, these proposed changes will be discussed with the Change Control Board (CCB). The CCB will determine the impact of the change and if/when it should be implemented.6.4 Defect ReportingWhen 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. 7. Functions To Be TestedThe following is a list of functions that will be tested: Add/update employee information Search / Lookup employee information Escape to return to Main Menu Security features Scaling to 700 employee records Error messages Report Printing Creation of payroll file Transfer of payroll file to the mainframe Screen mappings (GUI flow). Includes default settings FICA Calculation State Tax Calculation Federal Tax Calculation Gross pay Calculation Net pay Calculation Sick Leave Balance Calculation Annual Leave Balance CalculationA Requirements Validation Matrix will “map” the test cases back to the requirements. See Deliverables.8. Resources and Responsibilities
The Test Lead and Project Manager will determine when system test will start and end. The Test lead will also be responsible for coordinating schedules, equipment, & tools for the testers as well as writing/updating the Test Plan, Weekly Test Status reports and Final Test Summary report. The testers will be responsible for writing the test cases and executing the tests. With the help of the Test Lead, the Payroll Department Manager and Payroll clerks will be responsible for the Beta and User Acceptance tests.
8.1. Resources
The test team will consist of:
 A Project Manager
 A Test Lead
 5 Testers
 The Payroll Department Manager
 5 Payroll Clerks

8.2. Responsibilities
Project Manager Responsible for Project schedules and the overall success of the project. Participate on CCB.

Lead Developer Serve as a primary contact/liaison between the development department and the project team.
Participate on CCB.

Test Lead Ensures the overall success of the test cycles. He/she will coordinate weekly meetings and will communicate the testing status to the project team.
Participate on CCB.

Testers Responsible for performing the actual system testing.

Payroll Department Manager Serves as Liaison between Payroll department and project team. He/she will help coordinate the Beta and

đang được dịch, vui lòng đợi..

Kết quả (Việt) 2:[Sao chép]

Sao chép!

đang được dịch, vui lòng đợi..

Kết quả (Việt) 3:[Sao chép]

Sao chép!

đang được dịch, vui lòng đợi..

Các ngôn ngữ khác

Hỗ trợ công cụ dịch thuật: Albania, Amharic, Anh, Armenia, Azerbaijan, Ba Lan, Ba Tư, Bantu, Basque, Belarus, Bengal, Bosnia, Bulgaria, Bồ Đào Nha, Catalan, Cebuano, Chichewa, Corsi, Creole (Haiti), Croatia, Do Thái, Estonia, Filipino, Frisia, Gael Scotland, Galicia, George, Gujarat, Hausa, Hawaii, Hindi, Hmong, Hungary, Hy Lạp, Hà Lan, Hà Lan (Nam Phi), Hàn, Iceland, Igbo, Ireland, Java, Kannada, Kazakh, Khmer, Kinyarwanda, Klingon, Kurd, Kyrgyz, Latinh, Latvia, Litva, Luxembourg, Lào, Macedonia, Malagasy, Malayalam, Malta, Maori, Marathi, Myanmar, Mã Lai, Mông Cổ, Na Uy, Nepal, Nga, Nhật, Odia (Oriya), Pashto, Pháp, Phát hiện ngôn ngữ, Phần Lan, Punjab, Quốc tế ngữ, Rumani, Samoa, Serbia, Sesotho, Shona, Sindhi, Sinhala, Slovak, Slovenia, Somali, Sunda, Swahili, Séc, Tajik, Tamil, Tatar, Telugu, Thái, Thổ Nhĩ Kỳ, Thụy Điển, Tiếng Indonesia, Tiếng Ý, Trung, Trung (Phồn thể), Turkmen, Tây Ban Nha, Ukraina, Urdu, Uyghur, Uzbek, Việt, Xứ Wales, Yiddish, Yoruba, Zulu, Đan Mạch, Đức, Ả Rập, dịch ngôn ngữ.