Hardware and Software Testing
OneWorld Helpdesk™ Provides Computer Hardware and SoftwareTesting Services
OneWorld Helpdesk™ has provided testing and technical support on high-end defense systems for over 17 years. About 10 years ago we decided to use our engineering, tech support, and testing expertise to expand our services into computer hardware and software testing.
We work closely with the customer and use our deep engineering and technical support expertise to develop a detailed Statement of Work (SOW) that explains:
The contact process between OneWorld Helpdesk™ and our customer
What hardware, software, and documentation we require from the customer
What work we will perform such as:Write a test plan and procedures
Submit test plan and procedures to customer for approval and/or modification
Perform the testing
Write a detailed Final Test Report
Test pricing
After receipt of the contract, hardware, software, and documentation from the customer we begin the process of writing a test plan that explains the overall testing process. The plan generally covers:
Writing the detailed test procedures is the next step we take in the testing process. A test procedure first lists the equipment and/or software being tested. Next the procedure includes the Tester, Quality Assurance (QA) Inspector, and start and end testing dates.Documentation
Installation
Operating special features
Operating standard capabilities
Software compatibility
Different hardware and/or software configurations
What hardware and software we will use to perform the testing
The actual step-by-step Test Procedure is then written. Each step in the procedure has a place for the Tester’s and QA Inspector’s initials and the date the testing step was performed. These are very detailed steps that cover:
The Test Plan and Test Procedures are next submitted to the customer for approval and/or modification. Once the Test Plan and Procedures are approved we begin performing the testing.Product installation
Ease of use and ergonomics
Automated testing of the product
Operational testing of the product
Uninstalling the product
The testing is not cast in concrete. During testing we often find problems with a product. We notify the customer immediately about the problem, workarounds we found, and possible solutions. Sometime the problem is defective customer equipment, at other times it’s an operational misconception, and sometimes there are compatibility issues. Test Procedures that need changing are redlined to incorporate the appropriate modifications by the QA Inspector and/or Test Engineer. The Tester does not make modifications to a Test Procedure but they provide valuable feedback information to the Test Engineer. QA Inspectors make readability redlines that do not effect the technical testing of the product.
After the testing is completed the Test Engineer writes the Final Test Report that usually includes:
The Final Test Report, the original test procedures and data, product hardware, software, and documentation are then returned to the customer.Title Page
Table of Contents
List of Figures
List of Tables
Introduction
Overview of the Test Plan and Procedures
Details on problems found, workarounds, and possible solutions
Testing Conclusion