Releases

All tests listed here should be run in addition to 'make distcheck' before a release.

Branch merges

In addition to 'make distcheck', the following test categories should be run:

• Basic

• Basic WiFi (can be ignored if no wifi or supplicant code was changed)

• VLAN
• Bridge
• Bond

If the merged code contains changes to the Bluetooth or PPP-related code, those tests should be run as well. Changes that touch wpa_supplicant code should run Advanced WiFi and Advanced Wired tests.

Basic

• Ensure that a DHCPv4 based wired connection works
• Ensure that a static IP wired connection works
• Ensure that the following work for an "automatic" wired IPv6-only connection:
  • where the RA does not include M or O options, NM obtains a global IPv6 address and a default route
  • same as above plus RDNSS (and DNSSL if you have kernel 3.5 or later)
  • where the RA includes the O (otherconf) option, NM runs DHCPv6 and correctly handles the returned options
  • where the RA includes the M (managed) option, NM runs DHCPv6 and correctly handles the returned options
• Ensure that when no network connections are defined, the wired interface receives a default "Wired connection 1" connection that successfully activates with DHCP
• Ensure that wired connection takeover/assumption works by activating a DHCPv4 wired connection and restarting NM. The wired device should not "bounce", but upon restart the device should move from UNMANAGED to UNAVAILALBE to IP_CONFIG states, but not enter the DISCONNECTED, PREPARE, or CONFIG states
• Ensure that wired connection takeover/assumption works with static IPv4 addressing
• Ensure that at least one VPN plugin can successfully connect to the VPN server

Basic WiFi

• Ensure connection to the following types of WiFi access points using a common wifi driver (like ath9k or iwlwifi)

  • open
  • WEP
  • WPA-PSK
  • WPA-Enterprise with PEAP/MSCHAPv2 authentication
• Ensure that an "always ask" WPA Enterprise connection asks for the password each time

VLAN

• Ensure a VLAN connection for a physical interface which is set autoconnect=yes is created when NM starts
• Ensure a VLAN connection which is set autoconnect=yes is started when it's physical interface has a carrier
• Ensure that disconnecting a VLAN interface does not affect the parent physical interface

Bridge

• Ensure that a bridge port with autoconnect=yes also starts its bridge master at NM startup
• Ensure that manually activating a bridge master using DHCP waits for a bridge port before starting DHCP
• Ensure that manually activating a bridge port starts its bridge master and successfully acquires a DHCP lease
• Ensure that a bridge master with static addressing does not wait for bridge ports before completing activation
• Ensure that deactivating the last bridge port does not deactivate the bridge master
• Ensure that a bridge master created outside of NM (with eg brctl addbr foo0) is ignored by NM

Bonding

• Ensure that a bond slave with autoconnect=yes also starts its bond master at NM startup
• Ensure that manually activating a bond master using DHCP waits for a bond slave before starting DHCP
• Ensure that manually activating a bond slave starts its bond master and successfully acquires a DHCP lease
• Ensure that a bond master with static addressing does not wait for bond slave before completing activation
• Ensure that deactivating the last bond slave does not deactivate the bond master

PPP

Any changes that relate to PPP code, mobile broadband, or PPPoE should test the following.

• Ensure that a PPP-based mobile broadband modem successfully connects and passes traffic
• Ensure that a DHCP/static mobile broadband modem successfully connects and passes traffic
• Ensure that a Bluetooth DUN connection works correctly
• Ensure that killing pppd with a SIGTERM causes the NM device to enter the FAILED state

Advanced WiFi

• Ensure WPA-Enterprise connections survive multiple roaming attempts between APs in the same SSID
• Test WEP, WPA, and open connections on a variety of drivers (ath5k, ath9k, iwlagn, rt2800, b43, bcma, orinoco, p54)
• Ensure that connecting to a new "hidden" SSID network works correctly when using the "Connect to hidden network..." applet option
• Test other 802.1x authentication methods like TLS, TTLS, PAP, CHAP, GTC, etc
• Ensure that if no CA certificate path is given that the security warning dialog shows and warns about missing CA certificate

Advanced Wired

• Ensure a wired 802.1x connection works correctly using the MD5
• Ensure connection fallback from a DHCP connection to a different static IP connection works when the network does not support DHCP

Bluetooth

• Ensure that pairing a DUN capable phone works and creates a new NM connection
• Ensure that pairing a PAN capable phone works and creates a new NM connection
• Ensure that the new DUN connection connects and passes traffic
• Ensure that the new PAN connection connects and passes traffic
• Ensure that moving the phone out of range causes the NM device to enter the FAILED state for both DUN and PAN

• Ensure that deleting a paired device from the bluetooth applet removes the phone's connection from NetworkManager too