The test plan is for that how we are going to conduct that system is working.
Test Plan
Purpose
The purpose of this document is to project the test plan to allow the project team to adequately test the solution versus the business requirements. This document is merely a guide. Specific projects may warrant a different approach to testing. However, it is important that the test plan is detailed enough to validate that each business requirement has been adequately tested.
Business Requirements
This is to test a Network Design for 3 Separate Centres namely Albury, Waga Waga and Griffith with their departments namely Sales, IT, Procurement and Training & Facilitation is properly functioning having DHCP facilities, VoIP soft phone to registered Users, Proper Security Mechanism and the ADDS structure for deployment purpose.
The 3 centers will be connected to the cloud having VPN facilities and VoIP facilities, VPN to enable secure access to remote users.
For ensuring that our project is being developed correctly and appropriately, we have used various Verification and validation mechanisms. Testing at different levels is performed to ensure that the product is developed right and various validation testings are performed. Testing activities we performed includes both static and dynamic testing along with hazardous testing. To ensure the quality of the product extensive testing with appropriate number of test cases is performed along with the ISO 9001:2005 guidelines are followed to ensure the quality of the product.
Some of the verification activities we have implicated in our project are:
White box and black box testing activities are performed at different levels of testing. The levels of testing are:
Unit testing- Testing each and every line of code.
Integration testing – Testing the code combined.
Module Testing- Ensuring that each module is error free individually
Integration testing- testing the entire modules to ensure there exist no integration errors.
System testing- testing the entire application at the application level in a test environment.
Alpha Testing- Ensuring the functionality of the system at client’s environment without any errors.
Beta testing- Performing testing activity even after the product is delivered and implemented at the client.
Validation activities:
Various validation testing activities are:
Fault Injection: A Technique of Validation Testing.
Hardware fault inoculation: inoculation of bugs into the system.
Root Causes and Possible Countermeasures Hazard Analysis, Hazard Analysis by Identifying the Possible Consequences of Each Hazard and Their Probability of Occurrence Risk Analysis are the techniques of Validation Testing.
Testing Mechanisms
System Testing
System testing is developer testing of the solution against the Functional Design Specification or the Business Requirements Document. The focus of this testing is to directly validate the code.
Unit Testing
This testing is typically defined as developer testing of a specific module against functional design specifications.
Integration Testing
This testing is typically defined as testing by the development team as a single entity to ensure developed interactions are functioning properly.
Stability Testing (software / hardware)
Stability testing is a suite of tests meant to ensure that the system and hardware being utilized for this solution meet the specifications dictated by the business requirements. This testing is typically performed through a joint effort of the functional and technical testers. The testing can be divided into some or all of the following sub-phases:
Performance Testing
This testing is meant to monitor system performance during normal to high usage and compares to expected benchmarks detailed in the requirements.
Load Testing
This testing is meant to exercise the solution using a predefined load level, usually the highest load that the system can accept while still functioning properly.
Stress Testing
This testing is meant to allow testers to observe how the system reacts to failure. Stress testing tries to break the system under test by overwhelming its resources or by taking resources away from it.
Stability Entrance Criteria
All required hardware/system components within the test environment have been initialized.
All required network connectivity between devices has been completed.
Stability test cases have been documented, reviewed and validated.
Stability benchmarks are clearly agreed upon based on the Business Requirements Document.
All required data entry, database population, and system configuration have been completed.
Test facilities are available.