Test Plan

Functional Testing

Our general approach to functional testing involves continuously testing operation of the system, using laptop emulation environments and Raspberry Pi deployments.

• Verify usability of network connection once it has been established
• Verify service comes up cleanly when power to the access point is temporarily lost
• Test connection in both AP and device mode
• Verify connection is displayed in Active Sessions
• Test that code expires, and is culled from the AP database and the client's memorized networks
• Test re-connection

Exploratory Testing

The core of our approach to exploratory testing is dogfooding. By continually using our own product and seeing where it breaks, we can simulate real-world usage with a fair degree of accuracy.

Specifically, we want to:

• Test various timeouts
• Test a variety of traffic scenarios: simple browsing, e-mail, streaming video, etc.

Unit Testing

Service

• Verify that the service revokes access when the access code has expired
• Verify the client is disassociated from the wireless access point when a code expires
• Verify the service regenerates access codes where appropriate
• Verify all revoked access codes are culled
• Aim for 100% code coverage

Admin UI

To unit test the admin UI, we plan to simulate HTTP requests to the admin interface and compare the response to previous responses that are known to be correct.

Performance and Load Testing

There is very little we can do to load test our system without significant hardware investment. However, we can do the following:

• Verify that many connections are properly disconnected/culled
• Simulate multiple hostapd_cli calls