V1.1 NETINFO CLIENT INIT SEQUENCE TEST PLAN

Team : MI5

Release : V1.1

Component : frNetInfo/NIQS

Version : $id$

Louis Beaumier
Zero-Knowledge Systems Inc
Internal Documentation


Description

This test plan is designed to validate the new API function of the frnetinfo library, which is used by the Freedom client at startup.

The expression 'full update' and 'partial update' both refer to the same operation, which is a request for information on a list of entities. In a 'full update' the list will contains every entities in the systems. while in a 'partial update', it will contain only those modified since the provided time stamp (the 'since' parameter).

(We could also say that a 'full update' is a special case of a 'partial update' with since = 0.)

Pre-Requisites and Installation

You must know how to edit the content of NIDB using nidbtool.

You will need to use fr_client_init, a test program that performs the same operation that the client does at startup (regarding its interaction with NIQS).

Some of the command line options for that program are:

--niqs.hostname <host> : the host on which niqs runs --load <cache file> : the local cache file to load --save <cache file> : the local cache file to save --life <in seconds> : the lifetime of the local cache file in seconds before it expires --long : display the retrieved entities information in a more detailed format

Test Cases

Name of Tester:
TCO Item Test Cases Est. Time Actual Time Pass/Fail Comments
No local cache file Calling fr_client_init without loading a cache file should trigger a 'full update'

./fr_client_init --niqs.hostname <niqs_host> --life 1000
< 10 minutes
Calling fr_client_init with loading a cache file should NOT trigger a 'full update'

./fr_client_init --niqs.hostname <niqs_host> --save <cache>
./fr_client_init --niqs.hostname <niqs_host> --load <cache> --life 1000
< 10 minutes
Expiry of local cache file Calling fr_client_init with an expired cache file should trigger a 'partial update'

./fr_client_init --niqs.hostname <niqs_host> --save <cache>
./fr_client_init --niqs.hostname <niqs_host> --load <cache> --life 30
(repeat last call over a period of more than 30 seconds)
< 10 minutes
Calling fr_client_init with a non-expired cache file should NOT trigger a 'partial update'

./fr_client_init --niqs.hostname <niqs_host> --save <cache>
./fr_client_init --niqs.hostname <niqs_host> --load <cache> --life 1000
< 10 minutes
Out of sync local cache file Calling fr_client_init with an out of sync cache file should trigger a 'full update'

./fr_client_init --niqs.hostname <niqs_host> --save <cache>

On the NIQS host, edit the /freedom/etc/freedom-nidb.conf file and increase the
value of cacheDataVersion

./fr_client_init --niqs.hostname <niqs_host> --load <cache> --life 1000
< 10 minutes
NIDB with varying number of entities Add entities to NIDB after saving the cache file. Subsequent startup -- with an expired
cache -- will do a partial update.

./fr_client_init --niqs.hostname <niqs_host> --save <cache>

On the NIQS host, start nidbtool
entity add host ......
entity add aip ....

./fr_client_init --niqs.hostname <niqs_host> --load <cache> --life 0
< 10 minutes
Remove entities from NIDB after saving the cache file. Subsequent startup -- with an
expired cache -- will do a partial update and cull some
entities.

./fr_client_init --niqs.hostname <niqs_host> --save <cache>

On the NIQS host, start nidbtool
entity delete host ......
entity delete aip ....

./fr_client_init --niqs.hostname <niqs_host> --load <cache> --life 0
< 10 minutes

Link to TCO

A TCO was not written for this component.


This document was generated on May, 12 2000 using texi2html 1.57.