mirror of
https://github.com/Telecominfraproject/wlan-testing.git
synced 2025-11-01 03:17:54 +00:00
2d277bfeb7
* Country code with channel division: 2Ghz,20Mhz, US and channel 1 * change in testcase execution * created country_code-US, with channel_width-20Mhz, channel_no-1 for 2G band * missed git_configuration param * checking from setup_params_general 'rf' to set radio config * added country_code_channel_division funtion * added radio config using radio_config * corrected allure report * changed function name * check allure report * Added comment * allure report corrected * Created testcase for channel 2 in 2G band * checking allure report * added channel mode VHT in AP configuration which is common for both wifi-5 and wifi-6 AP, without channel-mode always getting channel mode HE * checking allure report * corrected json_get url * testcase for channel-2 in 20Mhz, US, 2G * corrected channel overwritten on second testcase * testcases for channels from 3 to 13 with US, 20Mhz, 2G * US have 2G channels from 1 to 11 * added print statement to verify IP and channel no * Checking again if client not assigned with IP * Testcases: US, 40Mhz, 2G, channels 1-11 * Testcases: US, 40Mhz, 5G, channels (36,44,52,60,100,108,132,140) * removed wrong testcases * Testcases: IN, (20Mhz, 40Mhz), 2G, channels 1-11 * Testcases: IN, 40Mhz, 5G, channels (36,44,52,60,100,108,132,140) * Testcases: CA, 20Mhz,40Mhz, 2G,5G, channels (1-11) (36,44,52,60,100,108,132,140) * Testcases: CA, 40Mhz, 5G, channels (36,44,52,60,100,108,132,140) * Testcases: CA, 5G, 80Mhz, channel (36, 52, 100, 132) * Testcases: IN, 5G, 80Mhz, channel (36, 52, 100, 132) * Testcases: US, 5G, 80Mhz, channel (36, 52, 100, 132) * Testcases: CA, 20Mhz, 5G, channel (36,40,44,48,52,56,60, 64, 100, 104, 108, 112, 116,132, 136, 140, 144) * Testcases: IN, 20Mhz, 5G, channel (36,40,44,48,52,56,60, 64, 100, 104, 108, 112, 116,132, 136, 140, 144) * Testcases: US, 20Mhz, 5G, channel (36,40,44,48,52,56,60, 64, 100, 104, 108, 112, 116,132, 136, 140, 144) * Added rf config improvements Signed-off-by: shivam <shivam.thakur@candelatech.com> * Testcases: JP, 20Mhz, 40Mhz (2G+5G), 80Mhz (5G) * Testcases: JP, 20Mhz, 40Mhz (2G+5G), 80Mhz (5G) * Called json_post to change country of lanforge-radio * Edited print message * corrected cli command * Testcases:GB(united kingdom) 20Mhz, 40Mhz, 80Mhz * added cleanup to clear station before creating next station * corrected radio-bands * Added US country code to change lanforge-radio country * Added IN country code to change lanforge-radio country * corrected radio-bands * Added US country code to change lanforge-radio country Co-authored-by: shivam <shivam.thakur@candelatech.com> Co-authored-by: Shivam Thakur <70829776+shivamcandela@users.noreply.github.com>
Test Case Execution Suite
Run on 1.X SDK
pytest -m sanity and not interop -s -vvv --testbed=basic-01 -o build=<firmware URL> --1.x
pytest -m sanity and interop -s -vvv --testbed=basic-01 -o build=<firmware URL> --1.x
pytest -m sanity_55 -s -vvv --testbed=basic-01 -o build=<firmware URL> --1.x
pytest -m performance -s -vvv --testbed=basic-01 -o build=<firmware URL> --1.x
pytest -m firmware -s -vvv --testbed=basic-01 -o build=<firmware URL> --1.x
Run on 2.X SDK
pytest -m uc_sanity -s -vvv --testbed=basic-03 -o build=<firmware URL>
pytest -m "performance and dataplane_throughput_test" -s -vvv --testbed=basic-03 -o build=<firmware URL>
You can customize the markets with and/or/not logical options
wlan-testing framework Information
pytest uses setup > test > tear_down
Fixtures : Code that needs to be part of more than 1 test cases, Setup and teardown is Implemented in Fixtures
Test cases are structured across different directories
├── wlan-testing
├── tests /* Root directory for tests */
We have 3 main resource types:
- Controller
- Access Points
- Traffic Generator
Controller is meant to Provision the Access-Point
├── tests /* Pytest cases Directory */
├── controller_tests /* controller has the REST API*/
├── conftest.py /* Fixtures to be used by controller tests */
├── test_api_login.py
├── test_api_customer.py
├── test_api_location.py
├── test_api_equipment.py
├── test_api_equipment_gateway.py
├── test_api_profile.py
├── test_api_firmware_management.py
Access-Point is meant to be connected to controller, as well as should be able to provide wired and wireless connectivity to Both real and virtual Clients
├── tests /* Pytest cases Directory */
├── access_point_tests
├── conftest.py /* Fixtures to be used by access point tests */
├── test_connectivity.py
├── test_radio.py
├── test_featureA.py To be added
├── test_featureB.py
e2e (End to End) test cases are further structured into test case physical environment
Each Environment differs in testbed setup
Controller AP Traffic Generator PDU Attenuator
basic : 1 1 1 LANforge 1 0 Atten
advanced : 1 1 1 LANforge 1 1 Atten
interOp : 1 - 8 Perfecto 0 1 Atten
MDU : 1 - - LANforge 0
Scale : 1 - - LANforge 0
├── tests /* Pytest cases Directory */
├── conftest.py /* Global Fixtures for tests */
├── tests - /* Pytest cases Directory */
├── e2e
├── advanced
├── conftest.py /* Fixtures specific to advanced LAB Environment */
├── basic
├── conftest.py /* Fixtures specific to basic LAB Environment */
├── interOp
├── conftest.py /* Fixtures specific to interOp LAB Environment */
├── mdu
├── conftest.py /* Fixtures specific to mdu LAB Environment */
|── mesh
├── conftest.py /* Fixtures specific to mesh LAB Environment */
|── scale
├── conftest.py /* Fixtures specific to scale LAB Environment */
Read the README.md in each e2e directory to get sample test case.
For any Clarifications, regarding Framework,
Email : shivam.thakur@candelatech.com