UAT stands for User Acceptance Test, somewhere we also called it as ATP ( Acceptance test Plan).
As we are already discussed about ICT Project Implementation processes and stages and this section is final stage of ICT implementation.
Once we done with Installation, Configuration, implementation based on proposed Solution and RFP. Now we need to test the solution in real world to test all services and tools.
Process follows to test all these services called UAT- User Acceptance test or ATP (Acceptance Test Plan).
Let’s understand how UAT executed and what all document and process required.
UAT (User Acceptance Test Plan)
Before start testing, need to share a testing plan with customer and get a signoff on the same. Below are the best practices during preparing Testing Plan:
- Customer Name
- SI, Vendor, OEM or Agency name
- Project Details
- Document Name, Ref & number
- Date & Revision number
- Complete Hardware or Tools details
- Licensee details
- Test Scenario
- Expected Result
- Actual Result with Pass/Fail
- Any Remarks
- Approved by Customer
How to Prepare UAT Document
To start or Perform UAT, we should have a format where we can share our observation and findings. Below are some mandatory information which should be part of UAT document
- Customer Name : This document should have complete Customer details and representative who will be Available during testing and approve the test.
- SI, Vendor, OEM or Agency name : Who will be perform these test from SI. Vendor or OEM end. It will be recommended that the team who implemented the solution should perform the test.
- Project Details: Document should have clear information about project name, Location, logo and contact details.
- Document Name, Ref & number : Test document should have a reference name and number that for which testing it is. Document name should be self explainetry about the test. Also capture if any RFP ref, document ref need to mentioned.
- Date & Revision number : Document should have testing date and revision number. Rev number will give us idea that how many times we have performed this test.
- Complete Hardware or Tools details : Test document should have completed hardware information for which test is planned like ( Hardware name. Model. Software version, Serial number, complete inventory, booting output, License details etc)
- Test Scenario : This is very critical and important section of the test document. All test and their scenarios should be agreed with customer. Also, we should try to cover at least one test scenario from each services, hardware or Tools. Some time all test parameters are already mentioned in RFP, so SI need to perform all those test and verify and make ensure that required/mentioned test cases should be pass and compliance.
- Expected Result : This document should have expected result from that test, so Customer can check and verify whether test is pass or Fail.
How to prepare Test scenarios : This part of the document is actually deliver the motive of the test. As we already discuss that some time test cases are already mentioned in RFP which we need to comply.
Case study-1 : Hardware Feature Compliance Test
Suppose Customer already explained some specific feature, firmware, technology, RAM, Flash then we need to show them via some Command, GUI or other ways. Let me take one template for Network Switch for your understanding.
This is only for example.
Case study-2 : How network Switch Avoid the Loop Test
Suppose we need to show that How network switch Avoid the Loop. Then below should be the test scenario
- Switch details on which we are going to perform this test ( Device name, Model, ver, Serial Number)
- Ports details on which test will be performed
- Sample Topology on which command will run
- Sample Config and what all Command needs to run
- Technology details which is using for this test like STP in this case.
- What will expected Output and result which prove that STP is working and Avoiding the Loop
Case Study-3 : End User Network Access Level Test
One of the most important test that User level test, that User will access that particular Service. Support we need to show how User will access Internet. Below are some basic information and results we need to show to customer to prove that how traffic is flow or is this taking right path or not.
- Need to present a Topology from ISP Link, Internet Router, FW, Core RTR, Core SW, Dist, SW, Access SW and then end Use connected with Access Switch.
Need to explain that how LAN user will access Internet and what will be the path. What will be expected result like:
- Will user will get IP from DHCP or Static
- From which IP subnet user will get IP, Subnet mask and Gateway.
- If User try to open Google, then how query will resolve, means how DNS will resolve and all
- How Traffic will flow.
- Need to share “trace-route” output where all Access, Dist, Core, RTR and othe IP will show that will indicate that user is connected with correct network and getting internet access in correct and Secure way.
- How much delay, ping response and other output.
Case Study-4 : Wi-Fi User Testing
If you need to do UAT for Wireless network, then need to take care of below test:
- Explain how Wi-Fi network Setup and Built
- Explain about all SSID (Corporate and Guest)
- Prepare a test on Corporate SSID like,
- How SSID configure
- How and where user will found this SSID (SSID Name)
- How to connect
- How user will IP Address ( DHCP)
- Which username password user need to use
- How AAA process will work for Corporate user Authentication’
- Then finally how they get access (Pass or Fail)
- Same for Guest User
- How WEB-Auth will work
- How Guest will access of internet not corporate
Case Study-5 : Tools or server access testing
All management and Monitoring tools needs to be access by all operation team, so they can do day-to-day operational task. To verify whether it is
working fine or not, we can plan some below tests:
- Tools Installed server location
- Licenses
- URL or IP to access the tool
- How to access, username/password
- How to find network details, Dashboard, network Topology, Health Status
- Some troubleshooting steps
Case Study-6 : Hardware HA or load balancing test
This is very important test to run a operation and services smoothly and without any downtime. Always plan a good redundancy at each level based on your DC tier level. Some of the HA test are includes:
- Hardware level – All critical devices should be implement and configure in redundant mode.
Rack Level- All critical devices should not be installed in same rack- Devices should have redundant Power supply and UPS power
- Devices should have link level redundancy.
- Plan to remove one Link / Power/ shutdown device and your network should run without any interruption from secondary or redundant devices.
- Also verify how much Failover took
- Verify fallback test
Perform Test Activity :
Once your all testing plans will accepted and approved by customer then you can plan for actual testing activities.
- Actual Result with Pass/Fail : Need to perform actual test based on the planned document with same command and scenarios and with same Result as expected. Customer can cross validate the output with expected result and if he is not found the same result or any gap between expected vs Actual then its upto client then he can fail the test.
- Need to capture Actual result and outputs and need to paste in UAT document.
- Until all test scenarios will not Pass and accepted by customer need to performed again and again with improvement.
- Any Remarks: Customer needs to validate all test and give his remarks or deviation if any.
- Approved by Customer: Finally UAT should be approved by Customer with UAT sign-off.
Conclusion
Basically UAT is an official document which prove that you have implemented the solution as expected in Solution and RFP and now solution or network is ready to use.
FAQ
Q: What is UAT means or stand for?
A: UAT stands for User Acceptance Testing.
Q: What is User Acceptance Testing (UAT)?
A: User Acceptance Testing (UAT) is the final stage of solution testing, where end-users or clients test the proposed vs implemented solution to ensure that it meets their requirements and performs as expected in real-world scenarios.
Q: What is the purpose of UAT?
A: The purpose of UAT is to validate the proposed, agreed solution with fulfill all business requirement and end use access. Its includes end to end solution testing with different real world scenarios.
Q: Who performs UAT?
A: UAT is typically performed between Client / end user and MSI/ SME. Sometime its includes OEM/Vendors as well. SME (Subject Matter Expert) will perform the test as per Client/end user requirement and end user will validate and accepted whether test is Pass or Fail.
Read More : https://techblog.kbrosistechnologies.com/
Visit to our site : https://www.kbrosistechnologies.com/
Watch more Video https://www.youtube.com/channel/UCpcd6IshE1caAbf9EdJd3gw
