Kernel/iwd
3
0
Fork 0
mirror of https://git.kernel.org/pub/scm/network/wireless/iwd.git synced 2024-11-09 05:29:23 +01:00
Code Releases Activity
5567caf64a
iwd/autotests/testEAP-TTLS-MSCHAPv2/connection_test.py

82 lines
2.1 KiB
Python
Raw Normal View History

auto-t: Test Tunneled-MSCHAPv2 over TTLS
2019-01-10 23:34:29 +01:00
#!/usr/bin/python3
import unittest
import sys
sys.path.append('../util')
import iwd
import testutil
from iwd import IWD
from iwd import PSKAgent
from iwd import NetworkType
from hostapd import HostapdCLI
class Test(unittest.TestCase):
auto-t: TTLS-MSCHAPv2 - remove iwd instance on failure
2019-03-15 23:02:48 +01:00
def validate_connection(self, wd):
auto-t: let testEAP-TTLS-MSCHAPv2 use HostapdCLI easier This test made it past the initial refactor to use HostapdCLI with the 'config' parameter. This avoids the need to iterate the hostapd map in the actual test.
2019-11-14 20:58:06 +01:00
hostapd = HostapdCLI(config='ssidEAP-TTLS-MSCHAPv2.conf')
auto-t: Test Tunneled-MSCHAPv2 over TTLS
2019-01-10 23:34:29 +01:00
self.assertIsNotNone(hostapd)
psk_agent = PSKAgent('abc', ('domain\\user', 'testpasswd'))
wd.register_psk_agent(psk_agent)
device = wd.list_devices(1)[0];
condition = 'not obj.scanning'
wd.wait_for_object_condition(device, condition)
device.scan()
condition = 'not obj.scanning'
wd.wait_for_object_condition(device, condition)
ordered_networks = device.get_ordered_networks()
ordered_network = ordered_networks[0]
self.assertEqual(ordered_network.name, "ssidEAP-TTLS-MSCHAPv2")
self.assertEqual(ordered_network.type, NetworkType.eap)
condition = 'not obj.connected'
wd.wait_for_object_condition(ordered_network.network_object, condition)
ordered_network.network_object.connect()
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
auto-t: Test Tunneled-MSCHAPv2 over TTLS
2019-01-10 23:34:29 +01:00
hostapd.eapol_reauth(device.address)
auto-t: remove busy wait for eapol reauth Many tests force a reauth after the initial connection. When the tests were written there was no way of ensuring the reauth completed except waiting (IWD.wait()). Now we can wait for hostapd events in the tests, which is faster and more reliable than busy waiting.
2020-07-08 19:48:01 +02:00
hostapd.wait_for_event('CTRL-EVENT-EAP-STARTED')
hostapd.wait_for_event('CTRL-EVENT-EAP-SUCCESS')
auto-t: Test Tunneled-MSCHAPv2 over TTLS
2019-01-10 23:34:29 +01:00
auto-t: replace waiting for network with device Many tests waited on the network object 'connected' property after issuing a Connect command. This is not correct as 'connected' is set quite early in the connection process. The correct way of doing this is waiting for the device state to change to connected. This common code was replaced, hopefully putting to rest any random failures that happen occasionally.
2020-09-14 23:02:33 +02:00
condition = 'obj.state == DeviceState.connected'
wd.wait_for_object_condition(device, condition)
auto-t: Test Tunneled-MSCHAPv2 over TTLS
2019-01-10 23:34:29 +01:00
testutil.test_iface_operstate()
testutil.test_ifaces_connected()
device.disconnect()
condition = 'not obj.connected'
wd.wait_for_object_condition(ordered_network.network_object, condition)
wd.unregister_psk_agent(psk_agent)
auto-t: TTLS-MSCHAPv2 - remove iwd instance on failure
2019-03-15 23:02:48 +01:00
def test_connection_success(self):
wd = IWD(True)
autotests: Remove del wd at the end function pattern Don't use del wd to dereference the IWD instance at the end of the function where it has been defined in the first place as at this point wd is about to have its reference count decreased anyway (the variable's scope is ending) so it's pointless (but didn't hurt). Relying on the __del__ destructor to kill the IWD process in those tests it has been started in the constructor is a bit of a hack in the first place, because the destructor is called on garbage collection and even through CPython does this on the refcount reaching 0, this is not documented and there's no guideline on when it should happen or if it should happen at all. So it could be argued that we should keep the del wd statemenets to be able to easily replace all of them with a call to a new method. But most of them are not placed so that they're guaranteed to happen on test success or failure. It would probably be easier to do this and other housekeeping in a base class and make the tests its subclasses. Also some of these tests don't really need to launch iwd themselves, since IWD now tracks changes in the known network files I think IWD only really needs to be killed between tests when main.conf changes.
2019-04-20 22:29:05 +02:00
self.validate_connection(wd)
auto-t: Test Tunneled-MSCHAPv2 over TTLS
2019-01-10 23:34:29 +01:00
@classmethod
def setUpClass(cls):
IWD.copy_to_storage('ssidEAP-TTLS-MSCHAPv2.8021x')
@classmethod
def tearDownClass(cls):
IWD.clear_storage()
if __name__ == '__main__':
unittest.main(exit=True)
Copy Permalink