Test plans are used to confirm functionality of a system/network or several integrated systems/networks.
We encourage customers to execute a test plan before and after every major change to confirm the change was successful. The purpose of running through the test plan before the change is to confirm the test plan is good and easily followed, and also to confirm the functionality you expect is present before the change occurs. If a test plan isn't run before a change, any resulting lack of functionality may not be due to the change, but something else entirely.
NOTE: The more specific the test plan is, the easier it will be to follow. EX: Open CRM application > edit customer TEST123 > save changes > print report.
Example:
Below are some ideas and examples of steps you could include in your test plan.
- Reboot a PC (wired) and confirm Internet connectivity after reboot
- Can be done for each VLAN
- Reboot a PC (wireless) and confirm Internet connectivity after reboot
- Can be done for each wireless SSID
- Confirm expected communication between networks (EG: clients to servers, servers to clients)
- Confirm expected communication between locations (EG: HQ to data center, data center to HQ)
- Confirm internal applications (especially business critical) are working as expected
- ERP, CRM, Time Clock?
- Confirm external applications (especially business critical) are working as expected
- Bank website, salesforce, company website?
- Confirm access to internal file shares
- Confirm access to internal print services
- Confirm access to email services
- Check Outlook
- Check OWA
- Check mobile access
- Send outbound email
- Send inbound email
- Send internal email
- Reboot a phone and confirm it registers as expected
- Make an outbound call and confirm two-way audio
- Make an inbound call and confirm two-way audio
- Make an internal call and confirm two-way audio
- Make an inbound call to the main number and confirm auto-attendant answers
- Send outbound fax
- Send inbound fax
SAMPLE Check List