Docstoc

test

Document Sample
test Powered By Docstoc
					TEST PLAN DOCUMENT                         Date: _____8 Nov 2005__________

Overview
         Individual programmers will be responsible for white box component testing of their
particular components. This testing will be done by custom test programs written by each
programmer to test the components that they write. They will be testing the functionality of
their particular component. They will go through certain methods by hand to determine the
cohesion level of each method then determine if their component finds the correct cohesion level
for each method. Following this hands on testing, the class tests listed later in this document will
be used to test the functionality of the individual classes. In regards to system testing, we will
be taking a top down approach for integration testing. Once we have completed integration
testing, we will move on to functionality testing using the use cases. There will be a test that tests
each of the system requirements in the Requirements Document. We will also run a series of
final stress tests to determine the maximum limits of the system. This will be done by running
the system on the FSU CS server Program and setting the memory usage size lower and lower
until the program fails. Also, the program will be tested on very large code segments to test for
speed performance. After any faults are found these will be addressed and then regression
testing will be done to make sure that these errors have been corrected.


Use Case Testing
        The user sits at the computer and opens the user interface. The user then selects the
option to browse to select a file. The user selects a file that consists of program code from C,
C++, or Java. The system then takes that file as input to the program.

        The user sits at the computer and opens the user interface. The user then selects the
option to browse to select a file. The user selects a file that does not contain program code
written in C, C++, or Java. The system produces an error message indicating an inappropriate
file was selected.


       An appropriate file is input to the system. The system analyzes the code data in the file
and produces a report indicating an acceptable level of cohesion in each of the methods
contained within the program.

       An appropriate file is input to the system. The system analyzes the code data in the file
and produces a report indicating an unacceptable level of cohesion in each of the methods
contained within the program.


Class Testing
        Class Testing will be accomplished prior to integration testing using the testing scenarios
listed below. Included is a table of classes in the system and their respective purposes.

 CodeTranslator                    Class                       Parses target program to list it's methods
 CohesionAnalysis                  SuperClass                  Analyses the cohesion of the target program methods
 CohesionRater                     Class                       Rates the cohesion of the target program methods
 FileSystem                        Class                      I/O class methods
 Interpreter                       Class                      Interprets the parse string
 Results                           Class                      Creates the Cohesion Report



Class:
         CodeTranslator
Test Scenario:
       Send CodeTranslator a snippet of code that’s unreadable.
Return Value Expected:
       Text string explaining a program error has occurred.

Test Scenario:
       Send CodeTranslator a snippet of code in Java with methods
Return Value Expected:
       Code ready to be translated

Test Scenario:
       Send CodeTranslator a snippet of code in C with methods
Return Value Expected:
       Code ready to be translated

Test Scenario:
       Send CodeTranslator a snippet of code in C++ with methods
Return Value Expected:
       Code ready to be translated

Test Scenario:
       Send CodeTranslator a snippet of code in Java with no methods
Return Value Expected:
       Code ready to be translated

Test Scenario:
       Send CodeTranslator a snippet of code in C with no methods
Return Value Expected:
       Code ready to be translated

Test Scenario:
       Send CodeTranslator a snippet of code in C++ with no methods
Return Value Expected:
       Code ready to be translated

Class:
       CohesionAnalysis
Test Scenario:
       Send source code written in language with BNF grammar to object.
Return Value Expected:
         Data delineating cohesion information for each method.

Test Scenario:
       Send source code written in language without BNF grammar to object.
Return Value Expected:
       Program exception string data

Class:
       CohesionRater
Test Scenario:
       Send data delineating cohesion information for each method
Return Value Expected:
       Data with cohesion ratings for each method

Test Scenario:
       Send anything but data delineating cohesion information for each method
Return Value Expected:
       Program exception string data

Class:
       FileSystem
Test Scenario:
       Load File (regardless of file type or actual file information)
Return Value Expected:
       Loads file to string variable

Test Scenario:
       Save Results
Return Value Expected:
       Saves cohesion rater results to text file

Class:
       Interpreter
Test Scenario:
       Send valid program data to interpreter with methods
Return Value Expected:
       Program data to be rated with the CohesionRater

Test Scenario:
       Send valid program data to interpreter with no methods
Return Value Expected:
       Exception string value

Test Scenario:
       Send interpreter Exception string value
Return Value Expected:
         Exception string value

Class:
       Results
Test Scenario:
       Send Results cohesion information to be assembled for a report
Return Value Expected:
       Cohesion report string value

Test Scenario:
       Send Results exception string information
Return Value Expected:
       Exception string value

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:21
posted:7/23/2011
language:English
pages:4