Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Strategy for Testing Distributed File Service

IP.com Disclosure Number: IPCOM000116936D
Original Publication Date: 1995-Nov-01
Included in the Prior Art Database: 2005-Mar-31
Document File: 2 page(s) / 81K

Publishing Venue

IBM

Related People

Abbattista, A: AUTHOR [+5]

Abstract

A strategy for test the Distributed File Service is disclosed. The strategy involved first verifying basic product functionality, then executing the same scenario repetitively for extended periods of time.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Strategy for Testing Distributed File Service

      A strategy for test the Distributed File Service is disclosed.
The strategy involved first verifying basic product functionality,
then
executing the same scenario repetitively for extended periods of
time.

      The problem involved the lack of a detailed strategy for
adequately performing a Product Assessment (PA) test on the
Distributed Computing Environment (DCE) Distributed File Service
(DFS) to insure quality released products.  PA testing, a post
Functional Verification Test (FVT), consists of scenarios focusing on
product functionality, stability, reliability, stress, and
interoperability (software and hardware) using large system
configurations representative of customer environments.  The
Distributed Computing Environment provides services which allows a
distributed application to interact with multiple types of computers,
operating systems, and networks as if they were a single system.
Distributed File Service is a distributed application that manages
information in the form of a file system.

      The solution involved architecting a series of testing methods
and configurations used to identify defects in the DFS product that
may impact a customer's business operations.  The team developed a
detailed strategy that gradually built and enlarged the DCE cell
configuration over time while increasing the complexity of the test
cases.  Initially, the test strategy demonstrated basic product
functionality by executing simple test cases.  Next, the test
strategy demonstrated overall product stability by executing more
complex test scenarios.  Finally, the test strategy demonstrated
overall product reliability by executing complex test scenarios for
extended periods of time.

      The test strategy utilized different machine configurations,
starting with 3 machine cells and moving up to 15 machine cells
(constrained by hardware limitations).  The DCE cell configurations
included non-distributed servers, distributed servers, replicated
servers, intercell access using DNS and X500, and single and multiple
LANS.  Additionally, the test configured the DFS component...