ter;" CLASS="Normal">BLACK BOX TEST SUITE

INTRODUCTION

Purpose

This set of test cases is composed to test the functionality of the
SMAK NT tool with respect to the functionality specified in the System
Requirement Specification (SRS).  These tests are created and implemented
without specific knowledge of the implemented source code of the program. 
The test cases are arranged by module according to the Specific Functional
& Performance Requirements (SRS 4.0) of the System Requirement Specification. 
Each test case will include the following information:

Test ID#
Description
Conditions
Inputs
Expected
Outputs
Result Log
Entry #



References and Controlling Documents

System Requirements Specification (SRS)

Testing Plan (TP)

Definitions, Abbreviations, and Acronyms

See Glossary (in Data Dictionary document).

ENVIRONMENT AND INTERFACE REQUIREMENTS

Operational System Hardware Requirements



Intel-based system
16MB of RAM
30MB HD space



Operational Support Software Requirements



Operating System: Windows 95/NT



PROGRAM TEST MODULES


Objecti</span><span class="Body-0020Text-00202--Char" style=" font-family: 'Arial';
font-size: 14pt;">ve Measurement Module (SRS 4.1)

BBTest01.01

Description:

Testing the ability of the Objective
Measurement Module to open C source code and successfully send it to
the secondary metrics tool for evaluation.

Conditions:

See Interface/Environment Conditions
(BBTS2.0)

Inputs:

** For this test case testfile.c is a valid,
compileable C source code file.

Open file testfile.c from some directory on the local hard drive
by navigating through the directory structure to the directory containing testfile.c.  Then double-clicking on its name
and/or icon.
Open file testfile.c from some directory on the local hard drive
by navigating through the directory structure to the directory containing testfile.c.  Then single-click its
name and/or icon and press the Open butt</span><span class="Body-0020Text-00202--Char" style=" font-family: 'Arial';
font-size: 12pt; font-weight: normal;">on.
Open file testfile.c from some directory on the local hard drive
by navigating through the directory structure to the directory containing testfile.c.  Then type testfile.c into the Filename text box
and press the Open button.
Open file testfile.c from some directory on the local
hard drive by typing the path from the root directory to testfile.c and then pressing the Open
button.
Open file testfile.c from some directory on the local hard drive
by typing the path from the current directory to testfile.c and then pressing the Open button

Expected Outputs:

For both above cases, the file testfile.c should
be sent to the secondary metrics tool.  Once sent to the secondary
metrics tool, the files ________, ________, and ________ should be created
as the files for extracting the metrics data.

Result Log Entry #:

BBTest01.02

Description:

Testing for return errors from
sending missing and/or unreadable files to the secondary metrics tool
from SMAK NT.

Conditions: See Interface/Environment
Conditions (BBTS2.0)

Inputs:

Open a file that does not exist
in the current directory.
Open a file that has it</span><span
class="Body-0020Text-00202--Char" style=" font-family: 'Arial'; font-size: 12pt;
font-weight: normal;"></span><span class="Body-0020Text-00202--Char" style=" font-family: 'Arial';
font-size: 12pt; font-weight: normal;">s read/write permissions disabled.
Open a file that is not a C
source file.

Expected Outputs:

A dialog box with a message, Error: File not found. Should be displayed with an
OK button on it.  When the OK button is pressed the Open file box
should reappear and allow the user another chanc</span><span class="Body-0020