After the deployment of the school WiFi network billing system, acceptance is the last level before the official transfer.——Account can create, charge to account and authenticate——But some of the key scenes are not seen in the basic tests, they are left out and become a problem on-line, bursting at the most inappropriate. The pre-enumeration of these easily overlooked test sites is the first step towards acceptance.
High-sum authentication pressure test is not to be omitted
The basic function test usually has only a few test accounts online, which is very different from the real operating environment.
Pressure testing should simulate peaks and set scenes: a 1.5-fold normal usage certification request is launched at short notice to observe the success rate and response time. The success rate of less than 99% or the response time of more than three seconds needs to be optimized. This test does not require real user participation, it can be modelled using RADIFUS test tools, but it must be implemented before acceptance and cannot be postponed until it is online.
Complete link testing for fee-for-net breakout and self-help recovery
The only tests that are usually done are fee-for-net breakouts."Clear the balance and confirm the break.", but the whole chain goes beyond that. Could Portal pop up normally after a break? Can you still access the charge account? How long will it be back online after the charge has been successful?
Each step needs to be tested, not just the end result. Especially when the charge is time-sensitive, which is the most direct indicator of the user’s experience. If it is found that recovery takes a few minutes, this data should be clearly identified before acceptance and informed in the operating file that the user would not complain immediately after the user had avoided charging."Not yet."。
Cross-border testing of multi-equipment switching and capping
Students usually have more equipment than they can use to bind up. When receiving and inspection, the upper limit border scene is tested: what happens when you tie up the maximum number of equipment before trying to add new equipment?
There is also a common gap: how to handle the binding records of used equipment after replacement of equipment? If there is no automatic release mechanism in the system, students are given access to the quota for tying with old equipment, new equipment cannot be tied and need to contact managers for manual processing.
Log integrity and compliance traceability tests
The acceptance should be conducted in a specific way to test the integrity of the log: is the authentication and flow records of an account complete at a certain time? Does the log contain the fields (account, IP, time, access targets) needed to complete the trace? If a test account is specified for posting on the web site at a given time, can all activity records of that account be accurately found from the log?
Log query interfaces also need to be tested: do the search results return within a reasonable time after entering the account number and time range? If the data are large, is the query acceptable? These details directly affect the efficiency of handling user complaints later and cooperating with compliance checks. If it becomes difficult to get online before you find that log queries are slow, then the cost of optimization is greater.
Validation of the correct execution of cross-regional strategies
If the system is configured with different billing strategies for accommodation and teaching areas, each must be verified separately at the time of receipt: Are the charges to be applied according to the suite rules for boarding accommodation? Are the fees to be paid in the classroom to be implemented according to a free or speed-limit strategy for access to education areas? Is the policy switch correct when switching between two regions?
These tests need to be moved into different areas in a real network environment, using real devices instead of simulations at the laboratory. If there is an error in regional strategy, there will be problems with boarding-room students not being charged or school-area students being accidentally billed.
Certification of system abnormal recovery capability
The school WiFi network billing system is highly available and usually only done"Is main ready to switch normal", but a more detailed scenario is often not measured: after the main server has been restarted, does the authentic user session remain? After the short interruption of database services, is the billing data missing? Does the user that is charging the value at the time of the switch?
The resilience of these anomalies determines how much the system’s user experience is lost in case of failure. If there are minutes of certification interruptions during the main preset switch, this should be clearly documented in the acceptance report and assessed whether it is acceptable. Leave the details blank, problems on line are unclear, and accountability is blurred.
The acceptance test must be documented.
Finally, the process and results of acceptance tests must be documented.——It should be recorded in the acceptance report. If a scene fails, it must be repaired on site or left for follow-up.
The record is an important basis for determining the attribution of responsibility when there are problems that arise. Only complete records can assess whether the system continues to meet standards in annual wi-fi inspections or has begun to deteriorate performance.