Network Information V1.2, NIDB modifications - Unit Test plan


$Id: nidb12testing.html,v 1.3.2.1 2000/07/25 00:47:58 marcd Exp $
$Author: danp $
$Date: 2000/08/04 22:50:53 $

1. Introduction

The current document describes the test plans and results for the NIDB modifications that were required for the NI V1.2 release as described in the Network Information V1.2, NIDB modifications - Specs and Design document.
 

2. NIDB support for latitude/longitude

The NIDBTOOL has been modified to make a validation of the region string for 2 specific commands:


2.1 ENTITY UPDATE COMMAND TESTING

Assuming that 'host1' exists, run "nidbtool" from the command line and execute the following test cases:

TEST 01 - Try to update region with a string that is not 17 nor 15 caracters long.
COMMAND - entity update host host1 region CA11
EXPECTED RESULT - An error message: "Error: 'CA11' is not 17 nor 15 characters long, so the user format is not appropriate."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 02 - Try to update region with a string which does not have the correct separator caracters.
COMMAND - entity update host host1 region CA10-7548N-12034W
EXPECTED RESULT - An error message: "Error: 'CA10-7548N-12034W' is not in the correct user format. Character 5 is not ':' or character 11 is not '/'."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 03 - Try to update region with a latitude direction that is not 'N', 'n', 'S' nor 's'.
COMMAND - entity update host host1 region CA10:7548E/12034W
EXPECTED RESULT - An error message: "Error: The latitude direction (caracter 10 of 'CA10:7548E/12034W') is not appropriate, must be either 'N', 'n', 'S' or 's'."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 04 - Try to update region with a longitude direction that is not 'E' nor 'W'.
COMMAND - entity update host host1 region CA10:7548N/12034S
EXPECTED RESULT - An error message: "Error: The longitude direction (caracter 17 of 'CA10:7548N/12034S') is not appropriate, must be either 'E', 'e', 'W' or 'w'."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 05 - Try to update region with a latitude degree value that is over 90 degrees.
COMMAND - entity update host host1 region CA10:9548N/12034W
EXPECTED RESULT - An error message: "Error: The value of latitude degrees '95' extracted from 'CA10:9548N/12034W' is out of range, must be between 0 and 90."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 06 - Try to update region with a latitude minute value that is over 59 minutes.
COMMAND - entity update host host1 region CA10:7568N/12034W
EXPECTED RESULT - An error message: "Error: The value of latitude minutes '68' extracted from 'CA10:7568N/12034W' is out of range, must be between 0 and 59."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 07 - Try to update region with a non null latitude minute value while the latitude degree value is already 90 degrees.
COMMAND - entity update host host1 region CA10:9048N/12034W
EXPECTED RESULT - An error message: "Error: The value of latitude minutes '48' extracted from 'CA10:9048N/12034W' is out of range for a latitude of 90 degrees."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 08 - Try to update region with a longitude degree value that is over 180 degrees.
COMMAND - entity update host host1 region CA10:7548N/19034W
EXPECTED RESULT - An error message: "Error: The value of longitude degrees '190' extracted from 'CA10:7548N/19034W' is out of range, must be between 0 and 180."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 09 - Try to update region with a longitude minute value that is over 59 minutes.
COMMAND - entity update host host1 region CA10:7548N/12064W
EXPECTED RESULT - An error message: "Error: The value of longitude minutes '64' extracted from 'CA10:7548N/12064W' is out of range, must be between 0 and 59."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 10 - Try to update region with a non null longitude minute value while the longitude degree value is already 180 degrees.
COMMAND - entity update host host1 region CA10:7548N/18034W
EXPECTED RESULT - An error message: "Error: The value of longitude minutes '34' extracted from 'CA10:7548N/18034W' is out of range for a longitude of 180 degrees."
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 11 - Make a successful update
COMMAND - entity update host host1 region CA10:7548N/12034W
EXPECTED RESULT -
"Command: update host host1 region CA107548N12034W"
"servoperator [Zero-Knowledge Systems [100]]"
" new region will be [CA107548N12034W]"
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

TEST 12 - Make a successful update using a lower case for the value of the latitude direction
COMMAND - entity update host host1 region CA10:7534n/12034W
EXPECTED RESULT -
"Command: update host host1 region CA107548N12034W"
"servoperator [Zero-Knowledge Systems [100]]"
" new region will be [CA107534N12034W]"
ACTUAL RESULT (PASSED/FAILED): PASSED (04/08/2000, by danp on danielf.dev.freedom/net)

Note: You may also do the 12 last test using a 2-caracter region string as well! This has been done on 04/08/2000, by danp on danielf.dev.freedom/net. Results: PASSED.
 
 

2.2 ENTITY ADD COMMAND TESTING

Assuming that 'host7' does NOT exist, run "nidbtool" from the command line and execute the following test cases:

TEST 01 - Try to add a new host with a region string that is not 17 caracters long.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA11 "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: 'CA11' is not 17 caracters long, so the user format is not appropriate."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 02 - Try to add a new host with a region string that does not have the correct separator caracters.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10-7548N-12034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: 'CA10-7548N-12034W' is not in the correct user format. 5th caracter is not ':' and/or 11th caracter is not '/'."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 03 - Try to add a new host with a latitude direction that is not 'N' nor 'S'.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548E/12034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The latitude direction (10th caracter of 'CA10:7548E/12034W') is not appropriate, must be either 'N', 'n', 'S' or 's'."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 04 - Try to add a new host with a longitude direction that is not 'E' nor 'W'.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548N/12034S "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The longitude direction (17th caracter of 'CA10:7548N/12034S') is not appropriate, must be either 'E', 'e', 'W' or 'w'."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 05 - Try to add a new host with a latitude degree value that is over 90 degrees.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:9548N/12034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The value of latitude degrees '95' extracted from 'CA10:9548N/12034W' is out of range, must be between 0 and 90."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 06 - Try to add a new host with a latitude minute value that is over 59 minutes.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7568N/12034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The value of latitude minutes '68' extracted from 'CA10:7568N/12034W' is out of range, must be between 0 and 59."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 07 - Try to add a new host with a non null latitude minute value while the latitude degree value is already 90 degrees.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:9048N/12034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The value of latitude minutes '48' extracted from 'CA10:9048N/12034W' is out of range for a latitude of 90 degrees."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 08 - Try to add a new host with a longitude degree value that is over 180 degrees.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548N/19034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The value of longitude degrees '190' extracted from 'CA10:7548N/19034W' is out of range, must be between 0 and 180."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 09 - Try to add a new host with a longitude minute value that is over 59 minutes.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548N/12064W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The value of longitude minutes '64' extracted from 'CA10:7548N/12064W' is out of range, must be between 0 and 59."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 10 - Try to add a new host with a non null longitude minute value while the longitude degree value is already 180 degrees.
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548N/18034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT - An error message: "Error: The value of longitude minutes '34' extracted from 'CA10:7548N/18034W' is out of range for a longitude of 180 degrees."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 11 - Make a successful add
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548N/12034W "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT -
""
"[Zero-Knowledge Systems [100]]"
"Entity stored."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)

TEST 12 - Make a successful add using a lower case for the value of the longitude direction
COMMAND - entity add host host7 thierry.dev.freedom.net 10.16.128.136 CA10:7548N/12034w "Zero-Knowledge Systems [100]" 1
EXPECTED RESULT -
""
"[Zero-Knowledge Systems [100]]"
"Entity stored."
ACTUAL RESULT (PASSED/FAILED): PASSED (29/06/2000, by danp on thierry.dev.freedom/net)
NOTE - You should run the host deletion command before running TEST 12 because of TEST 11.
     - Deletion command 'entity delete host host7'
 

3. NIDB support for new messaging entity types

The NIDBTOOL should be tested with the 3 new entity types for the following commands:

The niqs_test tool will be used to test the NIQS (Network Information Query Server). The following commands will be tested:


3.1 NIDBTOOL

Assuming that the NIDB does not yet contain any POP, IMEP or NMTA entity, run the following commands:

TEST 1 - Add a new POP entity on host1 (port 12345)
COMMAND - entity add pop POP host1 12345
EXPECTED RESULT - A confirmation message: "Entity stored."
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 2 - Add a new IMEP entity on host1 (port 67890)
COMMAND - entity add imep IMEP host1 67890
EXPECTED RESULT - A confirmation message: "Entity stored."
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 3 - Add a new NMTA entity on host1 (port 13579)
COMMAND - entity add nmta NMTA host1 13579
EXPECTED RESULT - A confirmation message: "Entity stored."
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 4 - List all entities
COMMAND - entity list
EXPECTED RESULT - A list of all entities that are in the NIDB, including the 3 new entities that were just added.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 5 - Get the description of the new POP entity
COMMAND - entity desc <entity_id_that_is_given_by_the_list_command>
EXPECTED RESULT - A complete description of the given entity:
 enttype<...> entname=<...>
 eid=<...> type=<...> ip=<...>
 status=<...> rating=<...>
 region=<...> operator=<...>
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 6 - Get the description of the new IMEP entity
COMMAND - entity desc <entity_id_that_is_given_by_the_list_command>
EXPECTED RESULT - A complete description of the given entity.
 enttype<...> entname=<...>
 eid=<...> type=<...> ip=<...>
 status=<...> rating=<...>
 region=<...> operator=<...>
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 7 - Get the description of the new NMTA entity
COMMAND - entity desc <entity_id_that_is_given_by_the_list_command>
EXPECTED RESULT - A complete description of the given entity.
 enttype<...> entname=<...>
 eid=<...> type=<...> ip=<...>
 status=<...> rating=<...>
 region=<...> operator=<...>
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 8 - Retrieve the data of the POP entity
COMMAND - entity show pop POP
EXPECTED RESULT - Data of the POP entity (name, id, port, ...)
 Data retrieved for [POP]
 entity pop POP <entity_id> 1 12345
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 9 - Retrieve the data of the IMEP entity
COMMAND - entity show imep IMEP
EXPECTED RESULT - Data of the IMEP entity (name, id, port, ...)
 Data retrieved for [IMEP]
 entity imep IMEP <entity_id> 1 67890
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 10 - Retrieve the data of the NMTA entity
COMMAND - entity show nmta NMTA
EXPECTED RESULT - Data of the NMTA entity (name, id, port, ...)
 Data retrieved for [NMTA]
 entity nmta NMTA <entity_id>1 13579
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 11 - Delete the POP entity from the NIDB
COMMAND - entity delete pop POP
EXPECTED RESULT - A deletion confirmation message.
 Found entity id for pop POP = <entity_id>
 Node [POP/pop] deleted
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 12 - Delete the IMEP entity from the NIDB
COMMAND - entity delete imep IMEP
EXPECTED RESULT - A deletion confirmation message.
 Found entity id for imep IMEP = <entity_id>
 Node [IMEP/imep] deleted
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 13 - Delete the NMTA entity from the NIDB
COMMAND - entity delete nmta NMTA
EXPECTED RESULT - A deletion confirmation message.
 Found entity id for nmta NMTA = <entity_id>
 Node [NMTA/nmta] deleted
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 14 - List all entities to make sure the 3 entities were deleted.
COMMAND - entity list
EXPECTED RESULT - A list of all entities that are in the NIDB without the 3 new entities.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)
 

3.2 NIQS_TEST

Assuming that the NIDB does not yet contain any POP, IMEP or NMTA entity, run the 3 first tests in section 3.1 (to add the new entities to the NIDB), and run the niqs_test tool. Then, run "connect <host_running_an_niqs>, and the following test cases:

TEST 1 - Query the status of all POP entities in the NIDB
COMMAND - status pop
EXPECTED RESULT - A table containing the status (and other information) of the existing pop entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 2 - Query the status of all IMEP entities in the NIDB
COMMAND - status imep
EXPECTED RESULT - A table containing the status (and other information) of the existing imep entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 3 - Query the status of all NMTA entities in the NIDB
COMMAND - status nmta
EXPECTED RESULT - A table containing the status (and other information) of the existing nmta entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 4 - List all the pop entities
COMMAND - list pop
EXPECTED RESULT - The entity id, entity type and entity name of the pop entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 5 - List all the imep entities
COMMAND - list imep
EXPECTED RESULT - The entity id, entity type and entity name of the imep entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 6 - List all the nmta entities
COMMAND - list nmta
EXPECTED RESULT - The entity id, entity type and entity name of the nmta entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 7 - Query the description of the pop entity
COMMAND - query description pop POP
EXPECTED RESULT - The full description of the entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 8 - Query the description of the imep entity
COMMAND - query description imep IMEP
EXPECTED RESULT - The full description of the entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 9 - Query the description of the nmta entity
COMMAND - query description nmta NMTA
EXPECTED RESULT - The full description of the entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 10 - Query the status of the pop entity
COMMAND - query status pop POP
EXPECTED RESULT - The current status of the entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 11 - Query the status of the imep entity
COMMAND - query status imep IMEP
EXPECTED RESULT - The current status of the entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)

TEST 12 - Query the status of the nmta entity
COMMAND - query status nmta NMTA
EXPECTED RESULT - The current status of the entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (10/07/2000, by danp on thierry.dev.freedom/net)
 

4 NIDB support for CORE AIPS

The NIDBTOOL should be tested using the following commands:

The niqs_test tool will be used to test the NIQS. This section will also check the "SET command of the NIDBTOOL". The following commands will be tested: The NIQS patch that allows the NIQS to return all AIP neighbours as AIPs (conversion COREAIP to AIP) will also be tested.
 

4.1 NIDBTOOL

Assuming that the NIDB does not yet contain any COREAIP, run the following commands:

TEST 1 - Add a new COREAIP entity on host1
        (aip port:12345, dh port: 67890, name COREAIP1, dh timeout 30, dh neg 3600)
COMMAND - entity add coreaip COREAIP1 host1 12345 67890 30 3600 1
EXPECTED RESULT - A confirmation message: "Entity stored".
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 2 - Add a new link between COREAIP1 and AIP1 (named host1)
         (tsdelay 5000, ts packets 2, ct flag off)
COMMAND - entity add link host1 coreaip/COREAIP1 5000 2 off
EXPECTED RESULT - A confirmation message: "Entity stored".
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 3 - Add a new link between COREAIP1 and AIP2 (named host2)
         (tsdelay 5000, ts packets 2, ct flag off)
COMMAND - entity add link host2 coreaip/COREAIP1 5000 2 off
EXPECTED RESULT - A confirmation message: "Entity stored".
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 4 - List all entities
COMMAND - entity list
EXPECTED RESULT - See all entities including the COREAIP (the link entities are NOT shown).
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 5 - Get the description of COREAIP1
COMMAND - entity desc <entity_id_of_COREAIP1>
EXPECTED RESULT - It should show all caracteristics of COREAIP1, including the neighbours:
enttype=<...> entname=<...>
entid=<entity_id_of_COREAIP1> type=<...> ip=<...> s/r=<...> neigh=2
region=<...> code=<...> operator=<...>
  neighbour 0:<entity_id_of_host1>
  neighbour 1:<entity_id_of_host2>
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 6 - Run the "entity show" command
COMMAND - entity show coreaip COREAIP1
EXPECTED RESULT - All data of COREAIP1 should be shown.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 7 - Delete the link AIP1-COREAIP1 from the NIDB
COMMAND - entity delete link host1 COREAIP1
EXPECTED RESULT - A deletion confirmation message.
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 8 - Get the description of COREAIP1 again
COMMAND - entity desc <entity_id_of_COREAIP1>
EXPECTED RESULT - Make sure the coreaip only has 1 neighbour left.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 9 - Delete the link AIP2-COREAIP1 from the NIDB
COMMAND - entity delete link host2 COREAIP1
EXPECTED RESULT - A deletion confirmation message.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 10 - Delete the COREAIP from the NIDB
COMMAND - entity delete coreaip COREAIP1
EXPECTED RESULT - A deletion confirmation message.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 11 - List all entities again
COMMAND - entity list
EXPECTED RESULT - The COREAIP is no longer part of this list.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)
 

4.2 NIQS_TEST

Assuming that the NIDB does not yet contain any COREAIP entity, run the 3 first tests in section 4.1 (to add the new COREAIP and links to the NIDB), and run the niqs_test tool. Then, run "connect <host_running_an_niqs>, and the following test cases:

TEST 1 - Query the status of all COREAIP entities in the NIDB (there is only 1 coreaip)
COMMAND - status coreaip
EXPECTED RESULT - A table containing the status (and other information) of the existing coreaip entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 2 - Get all available coreaips
COMMAND - available coreaip
EXPECTED RESULT - List of all COREAIP entity ids.
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 3 - List all coreaips
COMMAND - list coreaip
EXPECTED RESULT - List all COREAIPs.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 4 - Query the status of the specific coreaip
COMMAND - query status coreaip COREAIP1
EXPECTED RESULT - A table containing the status (and other information) of the existing coreaip entity.
ACTUAL RESULT (PASSED/FAILED): PASSED (14/07/2000, by danp on flint.dev.freedom/net)

TEST 5 - Query the description of the coreaip
COMMAND - query description coreaip COREAIP1
EXPECTED RESULT - Should return all information about this COREAIP, including the neighbours.
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 6 - Query the topology of the coreaip
COMMAND - query topology coreaip COREAIP1
EXPECTED RESULT - Should show all information of COREAIP1 and of its current neighbours.
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 7 - Run the nidbtool to remove the link between host1 (AIP1) and COREAIP1
COMMAND - entity delete link host1 COREAIP1
EXPECTED RESULT - A confirmation message.
ACTUAL RESULT (PASSED/FAILED):  PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 8 - Query the topology of the coreaip again
COMMAND - query topology coreaip COREAIP1
EXPECTED RESULT - The AIP1 (host1) should no longer be part of the neighbour list.
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 9 - Run the nidbtool and set the coreaip to "NOT available"
COMMAND - entity set coreaip COREAIP1 unavailable
EXPECTED RESULT - No message.
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 10 - Run the NIDBTOOL with the "entity state" command to make sure the coreaip is unavailable.
COMMAND - entity state coreaip COREAIP1
EXPECTED RESULT - Information about COREAIP1 showing it as "Unavailable"
ACTUAL RESULT (PASSED/FAILED): PASSED (17/07/2000, by danp on flint.dev.freedom/net)

TEST 11 - Get all available coreaips
COMMAND - available coreaip
EXPECTED RESULT - No coreaip should be available at this time.
ACTUAL RESULT (PASSED/FAILED): FAILED (17/07/2000, by danp on flint.dev.freedom/net)
 

4.3 NIQS Patch

Assuming that COREAIP1 is a neighbour of AIP "host1", run the following commands using the niqs_test:

TEST 1 - query the topology of aip "host1"
COMMAND - query topology aip host1
EXPECTED RESULT - COREAIP1 should be shown as an AIP.
ACTUAL RESULT (PASSED/FAILED): FAILED (17/07/2000, by danp on flint.dev.freedom/net)
 

5. Acronyms

All acronyms in the Network Information V1.2, NIDB modifications - Specs and Design document apply.