You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 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

  1. In-Range UT - these are the test cases which cover normal operations.
  2. Out-of-Range UT - these are the test cases which cover out of range scenarios: 
    1. border cases
    2. race conditions
    3. unexpected events
      1. EX: Tearing down an active Network Interface
  3. Error UT
    1. Error parameters
    2. Error Conditions
      1. network goes down unexpectedly
      2. Wire gets disconnected, etc

Performance Testing cases will be a separate section in this document.

Unit Test Plan

Configuration tests should be done through the DLC direct interface, as well as the YAML interface.

Local Network Configuration

In-Range UT

Primary Requirement ID

Secondary Requirement IDUnit Test IDUnit Test Description
cfg-020cfg-005, cfg-010, cfg-015,cfg-045, cfg-055, cfg-060, cfg-065UT-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-025cfg-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-035cfg-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
   
  • Configure 1st NID on tcp*/o2ib* in the following form:
    • tcp(<eth intf>)[<cpt>] <pattern>
  • Show NIDs to ensure that the interface has been added to the correct CPTs
   
  • Configure 1st NID on tcp*/o2ib* in the following form:
    • tcp(<eth intf>, <eth intf>, ...)[<cpt>] <pattern>
  • Show NIDs to ensure that the interface has been added to the correct CPTs
   
  • Configure 1st NID on tcp*/o2ib* in the following form:
    • tcp(<eth intf>[<ctp>], <eth intf>[<ctp>], ...) <pattern>
  • Show NIDs to ensure that the interface has been added to the correct CPTs
cfg-060cfg-065 

Go through the following lnetctl commands and excercise their parameters:

  • net
  • set num_range

 

Out-of-Range UT

Primary Requirement IDSecondary Requirement IDUnit Test IDUnit Test Description
cfg-020cfg-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
cfg-060cfg-065 

Go through the following lnetctl commands and excercise their parameters, by providing out of range values:

  • net
  • set num_range
   
  • Don't configure any LNet modprobe.
  • Load LNet where there exists only one commissioned IB interface with IPoIB configured
  • a TCP network should be created with that IB interface
  • Configure an o2ib network with the same IB interface
  • Now you should have two interfaces with exactly the same IB
    
    

 

Error UT

Primary Requirement IDSecondary Requirement IDUnit Test IDUnit 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
   

Go through the following lnetctl commands and excercise their parameters, by providing error values:

  • net
  • set num_range
   Delete a non-existent network
   Delete a non existent NID on tcp/o2ib

 

Remote Peer Configuration

In-Range UT

Primary Requirement IDSecondary Requirement IDUnit Test IDUnit Test Description
   
  • add a new peer with only git
    
    

 

Policy Configuration

General Configuration

Functional Requirements

Interface Selection and Message Sending Requirements

Dynamic NID Discovery

Debugging Requirements

Network interface Health

Backwards Compatibility Requirements

 

  • No labels