You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 2
Next »
Overview
The Unit Test Plan (UTP) will follow the same section breakdown as the Requirements in the Scope & Requirement Document.
Each Section will include the following types of tests
- In-Range UT - these are the test cases which cover normal operations.
- Out-of-Range UT - these are the test cases which cover out of range scenarios:
- border cases
- race conditions
- unexpected events
- EX: Tearing down an active Network Interface
- Error UT
- Error parameters
- Error Conditions
- network goes down unexpectedly
- Wire gets disconnected, etc
Performance Testing cases will be a separate section in this document.
Unit Test Plan
Local Network Configuration
In-Range UT
Configuration tests should be done through the DLC direct interface, as well as the YAML interface.
Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
| cfg-020 | cfg-005, cfg-010, cfg-015,cfg-045, cfg-055, cfg-060, cfg-065 | UT-000005 | - Configure 3 NIDs on the same TCP network.
- Show the NIDs
|
| | | UT-000010 | - Configure 3 NIDs on the same IB network
- Show the NIDs
|
| | | UT-000015 | - Configure 3 NIDs on the same TCP/IB Network
- Show the NIDs
- Delete 1 NID from the TCP/IB Network
- Show the NIDs
|
| | | | - Configure 2 NIDs on tcp0/o2ib0
- Configure 2 NIDs on tcp1/o2ib1
- Show the NIDs
- Delete 1st NID from tcp0
- Delete 2nd NID from tcp0
- Show NIDs
- No more tcp 0 should exist
- o2ib0 should be unaffected
|
| cfg-025 | cfg-005, cfg-010, cfg-015,cfg-045, cfg-055, cfg-060, cfg-065 | | - Configure the system to have 4 CPTs
- options libcfs cpu_npartitions=4 cpu_pattern="0[0] 1[1] 2[2] 3[3]"
- Configure 2 NIDs on tcp0
- NID 1 should be on CPTs 0, 3
- NID 2 should be on CPTs 1, 2
- Show NIDs
- proper CPT association should be displayed
|
| cfg-035 | cfg-040, cfg-045, cfg-055, cfg-060, cfg-065 | | - Configure the system to have 4 CPTs
- options libcfs cpu_npartitions=4 cpu_pattern="0[0] 1[1] 2[2] 3[3]"
- Configure 3 NIDs on tcp0
- NID 1 should be on CPTs 0, 3
- NID 2 should be on CPTs 1, 2
- NID 3 should be on all CPTs
- Show NIDs
- proper CPT association should be displayed
- NID 3 should exist on all CPTs
|
| | | | - Configure 1st NID on tcp0 using the legacy ip2nets parameter from DLC
- Show NIDs
|
| | | | |
Out-of-Range UT
| Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
| cfg-020 | cfg-005, cfg-010, cfg-015 | | - Configure 32 NIDs on the same TCP/IB Network
- Show the NIDs
|
| | | | - Configure 32 NIDs on the same TCP/IB Network
- Show the NIDs.
- Delete 32 NIDs on the same TCP/IB Network
|
| | | | - Configure NID A, B and C on tcp0/o2ib0 Network
- Configure NID A and B on tcp1/o2ib1 Network
- Show the NIDs
- Configuration should succeed. NIs can exist on different networks
|
| | | | |
| | | | |
| | | | |
| | | | |
Error UT
| Primary Requirement ID | Secondary Requirement ID | Unit Test ID | Unit Test Description |
|---|
| | | | - Configure 128 NIDs on the same TCP/IB Network
- Only the maximum NIDs will be configured
|
| | | | - Configure a non-existent NID on tcp0
- Configuration should fail with INVALID PARAMETER
|
| | | | - Configure the system to have 4 CPTs
- options libcfs cpu_npartitions=4 cpu_pattern="0[0] 1[1] 2[2] 3[3]"
- Configure 3 NIDs on tcp0
- NID 1 should be on CPTs 0, 4
- NID 2 should be on CPTs 1, 2
- NID 3 should be on all CPTs
- Show NIDs
- NID 1 should fail since no CPT 4
|
| | | | |
| | | | |
Remote Peer Configuration
Policy Configuration
General Configuration
Functional Requirements
Interface Selection and Message Sending Requirements
Dynamic NID Discovery
Debugging Requirements
Network interface Health
Backwards Compatibility Requirements
