Manual Test Cases

1. Wifi Device Support
For each type of Wifi NIC, verify that NWAM is able to connect to various kinds of WLANs, as well as detect when security parameters are incorrect. Items to check:

• Connect to Unsecured WLAN
• Connect to WEP WLAN
• Connect to WPA WLAN
• Connect to Unsecured WLAN that isn't broadcasting SSID.
• Connect to WEP WLAN that isn't broadcasting SSID.
• Detection of bad key for WEP
• Detection of bad key for WPA

2. Suspend and Resume
Verify that in wired and wireless environments, NWAM does the right thing after a suspend resume cycle. NWAM should properly detect if it is still connected to the old network environment, and if not, reconfigure the system for the new environment. This test is done using the Automatic NCP.

• Wired same environment
• Wired new environment (different DHCP network)
• Wireless old AP available
• Wireless old AP absent, new AP available

3. AP Selection
NWAM should choose the correct AP based on configured WLAN priority, regardless of whether that AP is broadcasting its WLAN ID.

• 2 APs, connect to highest priority
• Connect to highest priority WLAN, which is not broadcasting SSID, when a lower priority WLAN is broadcasting.

4. Wired Link Cable Plug/Unplug
Verify NWAM does the right thing when an interface is plugged. Test these cases with the Automatic NCP enabled.

• Wired interface cable plug-in (to a network with a DHCP server available) causes NWAM to configure that interface and stop using wireless.
• Wired interface cable unplug causes that NCU to go offline, and resumption of wireless usage.

5. Hotplug
Verify NWAM takes the correct action when a supported USB wireless NIC is plugged in:

• Automatic NCP - the new NIC is brought up and can connect to available wifi access points with no further configuration.
• User NCP - nothing happens.

6. DR
Verify that NWAM doesn the right thing when DR operations are performed on a wired NIC.

• Device is DRed out
• Replacement device is DRed in

7. Shared-Stack Zone

• Verify that attempting to enable the NWAM service in zone with ip-type=shared fails gracefully.

8. Non-Interference
Verify that NWAM doesn't attempt to configure various kinds of network devices that are created for use inside of zones or guest OSes.

• NICs, VNICs, VLAN links, and aggregations assigned to exclusive stack zones
• NICs, VNICs, VLAN links, and aggregations assigned to Xen Guests
• Logical interfaces belonging to shared-stack zones
• VBox interfaces
• LDOM interfaces

9. Duplicate Address Detection
Verify that NWAM marks an interface offline that fails to come up due to a duplicate address being configured.

• Static IPv4
• Static IPv6
• ??? How does the GUI report duplicates ???

10. BFU
Verify that NWAM 1.0 works well with BFU.

• NWAM 1.0 works after BFUing from a pre-NWAM 1.0 Nevada build with NWAM enabled.
• BFU runs correctly on a system running NWAM 1.0 bits with NWAM enabled.

11. OpenSolaris Upgrade
Verify that upgrading to NWAM 1.0 using IPS results in a working system.

• Upgrade a 2009.06 to NWAM 1.0 bits using IPS from a project private repo. Ensure that NWAM 1.0 works correctly when the upgraded image boots.
• Same as the previous test item, except customize the NWAM .5 configuration on the base system before upgrading.

12. Punchin
Verify that punchin works with the latest NWAM bits. This will require getting the very latest punchin packages that support NWAM 1.0.

• Punchin succeeds.
• A punchin location is created and made active when punchin starts.
• NIS and DNS configurations work.
• The punchin location is made inactive and destroyed when punchin is stopped.

13. Xen Guest
Verify that NWAM correctly brings up a network configuration in a Xen guest.

14. Ldoms
Verify that NWAM correctly brings up a network configuration in logical domain.

15. Vbox Guest
Verify that NWAM correctly brings up a network configuration in a Virtual Box Solaris Guest.

16. Initialization Tasks
Verify that NWAM properly creates persistent VNICs, Etherstubs and Flows at service start time.

• Make sure NWAM is enabled and will remain enabled on reboot.
• Create a persistent VNIC, flow, and Etherstub.
• Reboot the system and ensure that the VNIC, flow and Etherstub are all created, but not configured, during boot.