Installation Testing
[Installation testing has two purposes. The first is to insure that the software can be installed under different conditions¾such as a new installation, an upgrade, and a complete or custom installation¾under normal and abnormal conditions. Abnormal conditions include insufficient disk space, lack of privilege to create directories, and so on. The second purpose is to verify that, once installed, the software operates correctly. This usually means running a number of the tests that were developed for Function Testing.]
| Test Objective: | Verify that the target-of-test properly installs onto each required hardware configuration under the following conditions: · new installation, a new machine, never installed previously with <Project Name> · update, machine previously installed <Project Name>, same version · update, machine previously installed <Project Name>, older version |
| Technique: | · [Manually or develop automated scripts, to validate the condition of the target machine¾ new - <Project Name> never installed; <Project Name> same version or older version already installed). · Launch or perform installation. · Using a predetermined sub-set of function test scripts, run the transactions.] |
| Completion Criteria: | <Project Name> transactions execute successfully without failure. |
| Special Considerations: | [What <Project Name> transactions should be selected to comprise a confidence test that <Project Name> application has been successfully installed and no major software components are missing?] |
Tools
The following tools will be employed for this project:
[Note: Delete or add items as appropriate.]
| Tool | Vendor/In-house | Version | |
| Test Management | |||
| Defect Tracking | |||
| ASQ Tool for functional testing | |||
| ASQ Tool for performance testing | |||
| Test Coverage Monitor or Profiler | |||
| Project Management | |||
| DBMS tools |
Resources
[This section presents the recommended resources for the <Project Name> project, their main responsibilities, and their knowledge or skill set.]
Roles
This table shows the staffing assumptions for the project.
[NOTE: Delete or add items as appropriate.]
|
|
|
| Human Resources | ||
| Worker | Minimum Resources Recommended (number of full-time roles allocated) | Specific Responsibilities or Comments |
| Test Manager, Test Project Manager | Provides management oversight. Responsibilities: · provide technical direction · acquire appropriate resources · provide management reporting | |
| Test Designer | Identifies, prioritizes, and implements test cases. Responsibilities: · generate test plan · generate test model · evaluate effectiveness of test effort | |
| Tester | Executes the tests. Responsibilities: · execute tests · log results · recover from errors · document change requests | |
| Test System Administrator | Ensures test environment and assets are managed and maintained. Responsibilities: · administer test management system · install and manage access to test systems | |
| Database Administrator, Database Manager | Ensures test data (database) environment and assets are managed and maintained. Responsibilities: · administer test data (database) | |
| Designer | Identifies and defines the operations, attributes, and associations of the test classes. Responsibilities: · identifies and defines the test classes · identifies and defines the test packages | |
| Implementer | Implements and unit tests the test classes and test packages. Responsibilities: · creates the test classes and packages implemented in the test model |
System
The following table sets forth the system resources for the testing project.
[The specific elements of the test system are not fully known at this time. It is recommended that the system simulate the production environment, scaling down the accesses and database sizes if and where appropriate.]
[Note: Delete or add items as appropriate.]
| System Resources | |
| Resource | Name / Type |
| Database Server | |
| —Network or Subnet | TBD |
| —Server Name | TBD |
| —Database Name | TBD |
| Client Test PC's | |
| —Include special configuration requirements | TBD |
| Test Repository | |
| —Network or Subnet | TBD |
| —Server Name | TBD |
| Test Development PC's | TBD |
Project Milestones
|
|
|
[Testing of <Project Name> should incorporate test activities for each of the test efforts identified in the previous sections. Separate project milestones should be identified to communicate project status accomplishments.]
| Milestone Task | Effort | Start Date | End Date |
| Plan Test | |||
| Design Test | |||
| Implement Test | |||
| Execute Test | |||
| Evaluate Test |
Deliverables
[In this section, list the various documents, tools, and reports that will be created, by whom, delivered to who, and when delivered.]
Test Model
[This section identifies the reports that will be created and distributed from the test model. These artifacts in the test model need to be created or referenced in the ASQ tools.]
Test Logs
[Describe the method and tools used to record and report on the test results and testing status.]
Defect Reports
[In this section, identify the method and tools used to record, track, and report on test incidents and their status.]
Дата добавления: 2015-12-17; просмотров: 12; Мы поможем в написании вашей работы! |
Мы поможем в написании ваших работ!