iwd.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: James Prestwood <prestwoj@gmail.com>
To: iwd@lists.linux.dev
Cc: James Prestwood <prestwoj@gmail.com>
Subject: [PATCH v2 3/6] auto-t: add test for scanning in AP mode
Date: Fri,  4 Nov 2022 09:37:57 -0700	[thread overview]
Message-ID: <20221104163800.451867-3-prestwoj@gmail.com> (raw)
In-Reply-To: <20221104163800.451867-1-prestwoj@gmail.com>

---
 autotests/testAP/scan_test.py | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
 create mode 100644 autotests/testAP/scan_test.py

diff --git a/autotests/testAP/scan_test.py b/autotests/testAP/scan_test.py
new file mode 100644
index 00000000..0935912c
--- /dev/null
+++ b/autotests/testAP/scan_test.py
@@ -0,0 +1,20 @@
+#! /usr/bin/python3
+
+import unittest
+
+from iwd import IWD
+
+class Test(unittest.TestCase):
+    def test_ap_scan(self):
+        wd = IWD(True)
+
+        dev = wd.list_devices(1)[0]
+
+        dev.start_ap('TestAP2', 'Password2')
+
+        dev.scan()
+
+        networks = dev.get_ordered_networks()
+
+        self.assertTrue(len(networks) == 1)
+        self.assertTrue(networks[0]['Name'] == 'TestAP1')
-- 
2.34.3


  parent reply	other threads:[~2022-11-04 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-04 16:37 [PATCH v2 1/6] ap: update Scanning property when AP starts James Prestwood
2022-11-04 16:37 ` [PATCH v2 2/6] auto-t: iwd.py: allow certain APIs to be used in AP mode James Prestwood
2022-11-04 16:37 ` James Prestwood [this message]
2022-11-04 16:37 ` [PATCH v2 4/6] ap: change PairwiseCiphers to string array James Prestwood
2022-11-04 16:37 ` [PATCH v2 5/6] auto-t: update test to work with PairwiseCiphers array James Prestwood
2022-11-04 16:38 ` [PATCH v2 6/6] doc: document AP properties PairwiseCiphers/GroupCipher James Prestwood
2022-11-04 17:54 ` [PATCH v2 1/6] ap: update Scanning property when AP starts Denis Kenzior

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221104163800.451867-3-prestwoj@gmail.com \
    --to=prestwoj@gmail.com \
    --cc=iwd@lists.linux.dev \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).