The certification system is complete. The supplier says"All right, we're ready for acceptance."Many hotel IT directors have signed the contract by connecting WiFi, receiving a code for mobile phones, and calling for confirmation. But such acceptances only confirm one piece of equipment, one operation, one scene, leaving out a lot of questions about possible future explosions.
Basic Authentication
The most basic authentication items are: full process of SMS certification (sMS messaging, security code entry, authentication success, normal access to the extranet), frequency limits for SMS (only once in a short time, preventing brushing), expired processing of the SMS (a certificate code that is not available for more than five minutes), correct recording of logs (cell number, time, MAC address, intranet IP) after authentication has been successful, and whether accounts expire correctly. These are core functions of the authentication system, and any failure to meet a standard is an unwireable issue.
Multi-equipment multi terminal testing
The test must cover the main equipment type: iPhone (the latest version of iOS), Android flag ship (one each for Hua, Mi, OPPO), Android portal (compatibility to cover low end devices), Windows notebook (one for Chrome and Edge browsers) and Mac notebook (one for Safari and Chrame). For each device, verify: Captive tests normal trigger Portal page pop-ups, Portal page layouts normal (no error or button not clickable), authentication process properly completed and network smooth after certification has been successful. The iOS device Captive window is to be tested separately and cannot be replaced by Safari because of the differences in behaviour between the two.
Multi-certification test
If the system supports multiple authentication methods (text message, micromail, room number, etc.), each of these is tested completely. Microletter authentication is measured in different network environments (wiFi-based and 4G-based feedbacks are normal); room number certification is required to measure boundary conditions (if the wrong room number is correctly rejected and the returned room number is not valid); if there are multiple authentication methods that exist, test whether the switch between modes flows and interfaces are residual.
MultiSSID policy validation
In the case of multiple SSIDs, each SSID certification strategy is independently validated: the physical name authentication process for the guest room WiFi, the password validation of the employee in-network (acknowledged that Portal will not be triggered), the free or temporary password authentication of the meeting room (recognizing that the strategy is correct and isolated from other SSIDs).
And stress tests.
Single user tests are not equal to high and no problems are suggested. Simulation of peak-level scenarios in the testing environment is recommended: a request for authentication was launched with 20-30 devices, observing whether there had been a significant increase in the time required for certification (target: a single certified response time of less than three seconds followed by a single one-time release, with a success rate of no less than 95%). If the test conditions do not allow real equipment to be sent together, the verification interface can be simulated and requested using pressure tools to verify that the server is stable at a high load. Many projects have jumped and will not be found to last until holiday holidays, and the cost of remediation is high.
Failed site validation
The acceptance is done by actively detecting the failure scenario rather than simply measuring normal processes: manually stopping the authentication service process, observing whether the online user has broken off the network, whether new users can access it (depending on the configuration of the malfunction release mode), whether process dæmonies automatically restart; breaking up connections between the authentication server and network equipment and observing processing behaviour after RADIUS timeouts; clearing SMS switch balances (which can be tested for account simulation) and observing if there are correct alarm output. These failures occur early in real operations, being validated at the receiving and inspection stage to ensure that each failure is processed with a desired result, much less than it would be prudent to check the reasons for re-exiting after going online.
Log Compliance Validation
After completing authentication with several devices, the back-office log is opened to check that: the log field is complete (cell number, authentication time, MAC address, intranet IP, authentication mode); all authentication records of the user are available via cell phone numbers; a time range is used to screen the log; and whether log export (CSV or Excel format) is supported. If you have a real name reporting requirement, simulate a data upload, confirm that the reported interface works properly, and the file format is in conformity.
Manage back-office functional validation
The management backstage is the main tool for future dimensions and is also fully tested at receiving and inspection: whether manual creation/deletion of accounts is normal; whether the operation to compel a device to be offline is effective (whether the device can continue to access without being recertified should not be possible after downlink); whether the Portal page configuration changes are in effect in real time; whether system parameters (duration period, equipment number limit) have been correctly applied to new authentication requests. The administration backboard operator ' s operating privileges are also checked if different permission roles (superpipes, general administrator) are properly segregated.
Value of acceptance reports
After the acceptance test has been completed, it is recommended that a supplier be required to provide a written acceptance report recording the results and status of each test item. The unpassed project must specify the duration and re-examination requirements and cannot sign the acceptance if there are no pass items.
The acceptance of the WiFi certification system at the hotel is not a formality, but a final closure to the quality of delivery for the entire project.