Validation Template by sNDd0a3

VIEWS: 67 PAGES: 11

									    Software Testing Plan

          Version 1.0

        April 22, 2004

   Web Publishing System

       Joan Teamleader
          Paul Adams
         Bobbie Baker
        Charles Charlie


Submitted in partial fulfillment
    Of the requirements of
CS 310 Software Engineering I
                                                            Table of Contents
Table of Contents ........................................................................................................................................... 1
1.0. Introduction ............................................................................................................................................. 2
  1.1. Purpose ................................................................................................................................................ 2
  1.2. Scope of Testing .................................................................................................................................. 2
  1.3. Glossary ............................................................................................................................................... 2
  1.4. References ........................................................................................................................................... 2
  1.5. Overview of Document ....................................................................................................................... 3
2.0. Verification Testing ............................................................................................................................ 4
  2.1      Unit Relationships .......................................................................................................................... 4
  2.2      Unit Testing .................................................................................................................................... 5
      Test Unit: AuthorSearch ......................................................................................................................... 5
  2.3      Integrative Testing .......................................................................................................................... 5
      Test Unit: On-Line Journal (JournalHomePage) .................................................................................... 5
3.0. System (In-House Validation) Testing ............................................................................................... 7
  3.1      Use Case: Search Article ................................................................................................................ 7
  3.2      Use Case: ........................................................................................................................................ 8
4.0. Stakeholder Testing ...........................................................................................................................10
  4.1      Acceptance Testing........................................................................................................................10
  4.2      Beta Testing ...................................................................................................................................10




Software Testing Plan                                                          1                                                           April 22, 2004
1.0. Introduction
1.1. Purpose

        This document is part of the Software Verification and Validation Plan.

        Its primary audiences are the development team, the in-house quality assurance

team, and the stakeholders. An important secondary audience is the maintenance team

who will need to correct, modify, and enhance this product.


1.2. Scope of Testing

        This document will be used by the development team to conduct verification and

validation tests for the product. It also details the Acceptance Testing that will be done

and the Beta Testing procedures. This document contains only two sample verification

tests and two sample use case validation tests in accordance with the class assignment.


1.3. Glossary

         Term                                           Definition
Acceptance Testing             Testing done in the stakeholder environment. It may be
                               done by the stakeholder, the development team, or an
                               outside team as agreed to by the stakeholder.
Beta Testing                   The preliminary usage of the system by the stakeholder.
Validation Testing             Testing done to assure that the product satisfies all of the
                               needs of the stakeholder and the requirements listed in the
                               Software Requirements Specification.
Verification testing           Testing done to assure that the modules of the project
                               perform as required by the Software design Description.



1.4. References

Teamleader, Joan, Paul Adams, Bobbie Baker, and Charles Charlie. Web Publishing

        System: Software Design Description. Jacksonville State University, 2004.




Software Testing Plan                         2                                 April 22, 2004
Teamleader, Joan, Paul Adams, Bobbie Baker, and Charles Charlie. Web Publishing

         System: Software Requirements Specification. Jacksonville State University,

         2004.


1.5. Overview of Document

         In the next section, the verification tests for two of the major design entities are

given.

         In the following section, sample validation tests for some of the major use cases

as required by a previous assignment are given.

         The final chapter outlines the installation and acceptance testing procedure and

gives the conditions for beta testing the software.




Software Testing Plan                           3                                  April 22, 2004
2.0.    Verification Testing
2.1     Unit Relationships

Relationships other than on tables:
Unit Name                                 Depends on
User (interface)                          On-Line Journal (Journal Home Page)
Journal Home Page                         AuthorSearch
Journal Home Page                         CategorySearch
Journal Home Page                         KeywordSearch
Editor (interface)                        Article Manager
Article Manager                           PeopleManager
PeopleManager                             HS Database (interface)
Article Manager                           ArtMgr
Article Manager                           Publishetr

Table dependencies are as follows:
Unit Name                                 Depends on Table
AuthorSearch                              Author
AuthorSearch                              Article
CategorySearch                            Article
CategorySearch                            Category
KeywordSearch                             Article
PeopleManager                             Reviewer
PeopleManager                             Reviewer-Relationship
PeopleManager                             Author
PeopleManager                             Author-Relationship
ArtMgr                                    Reviewer
ArtMgr                                    Author
ArtMgr                                    Author-Relationship
ArtMgr                                    Reviewer-Relationship
ArtMgr                                    Category-Relationship
ArtMgr                                    Active Article
Publisher                                 Active Article
Publisher                                 Article (Journal Database)




Software Testing Plan                 4                                April 22, 2004
2.2     Unit Testing

Test Unit: AuthorSearch
Cross-Reference: SDD 3.1.2 Code:

Driver: None needed.

At least five articles must be in the database. The following will suffice.

Authors             Title             Categories         Abstract             Body
Dean, James         Ways to Avoid     Humor,             This article         <insert block of
Nash, Ogden         Testing           Satire             involves             random text
Paddle, Wheel                                            ridiculous           here>
                                                         ideas about
                                                         mud.
Dean, James         Testing is Fun    Satire             Ridiculous is        < insert different
                                                         a manner of          block of random
                                                         speaking.            text here>
Dean James          Nonsense I        Romance            No keyword           < insert different
Double, Mint        Have Known                           in common.           block of random
                                                                              text here>
Paul, Peter         Apostles of       Software           Speaking of          < insert different
                    Testing           Engineering        mud and mud.         block of random
                                                                              text here>
Double, Mint        Software is Fun   Software           Ridiculous           < insert different
Nash, Ogden         to Create         Engineering        mud ideas.           block of random
                                      Romance                                 text here>



Method: Use interactive input.

Each author must be tested for each article by that author. Continue each until the article

is downloaded. (There are nine tests to be performed.)

The test is successful when the correct article is downloaded each time.


2.3     Integrative Testing

Test Unit: On-Line Journal (JournalHomePage)
Cross-Reference: SDD 3.1.1 Code:

Driver: None needed.


Software Testing Plan                          5                                   April 22, 2004
Method: This unit is partly tested by testing the Use Case Search Article (see 3.1
below).

In addition, we must test the email capability. Select to send email then send a message

to the editor of the journal attaching a text file.

The test is successful if the text file can be successfully downloaded by the editor.




Software Testing Plan                           6                               April 22, 2004
3.0.    System (In-House Validation) Testing
3.1     Use Case: Search Article

Reference: SRS, Section 3.2.1.

Environment: Access the database from a computer on the Internet other than the one on

which the database resides.

Since this use case uses the Online Journal database exclusively, we will create a copy of

that database by entering data directly into tables. The following is a minimum of the data

that must be available for testing:

At least five articles must be in the database. The following provides a variety of options

to be tested.

Authors             Title             Categories        Abstract          Body
Dean, James         Ways to Avoid     Humor,            This article      <insert block of
Nash, Ogden         Testing           Satire            involves          random text
Paddle, Wheel                                           ridiculous        here>
                                                        ideas about
                                                        mud.
Dean, James         Testing is Fun    Satire            Ridiculous is     < insert different
                                                        a manner of       block of random
                                                        speaking.         text here>
Dean James          Nonsense I        Romance           No keyword        < insert different
Double, Mint        Have Known                          in common.        block of random
                                                                          text here>
Paul, Peter         Apostles of       Software          Speaking of       < insert different
                    Testing           Engineering       mud and mud.      block of random
                                                                          text here>
Double, Mint        Software is Fun   Software          Ridiculous        < insert different
Nash, Ogden         to Create         Engineering       mud ideas.        block of random
                                      Romance                             text here>




Software Testing Plan                          7                               April 22, 2004
Method: Use interactive input.

There are three functions to be tested, lookup by author, category and keyword. These are

to be tested in random order.

Each author must be tested. Continue each until the article is downloaded.

Each category must be tested. Continue each until the article is downloaded.

Each noun in the Abstract column is to be tested as a keyword. Continue each until the

article is downloaded. Try words not contained in the abstract. Make sure that duplicate

words do not produce duplicate responses. Make sure case is not significant.

Periodically, abandon a search in the middle and restart.

Results Expected: The test is successful if no problems are encountered.


3.2     Use Case:

Reference: SRS, Section 3.2.6.

Environment: This test will be performed on the Article Manager Database. The use

case Enter Communication must be implemented prior to validation testing of this use

case.

At leas t five articles must be in the database at various status levels. The data listed in

Section 2.1 can be used with the addition of status values.



Method: Use interactive input.

There are five functions to be tested, add (or remove) categories, correct typographical

errors, remove a reviewer, enter an updated article, and enter a review. After each action

is performed, inspect the database to see if the action has occurred.

Add a new category for an article.


Software Testing Plan                          8                                  April 22, 2004
Add two new categories for an article.

Delete a category for an article.

Attempt to delete the last category for an article. This should not be allowed.

Modify an author’s name.

Modify a title.

Modify an abstract.

Remove a reviewer. If all the other reviews are entered, this should change the article’s

status accordingly.

Attempt to remove the last reviewer. This should not be allowed.

Enter an updated article.

Enter a review for an article. This should change the reviewer’s status accordingly and if

that is the last outstanding review, change the article’s status accordingly.

Results Expected: The test is successful if no problems are encountered.




Software Testing Plan                         9                                   April 22, 2004
4.0.    Stakeholder Testing
4.1     Acceptance Testing

        The development team will preload the system with at least five articles in various

stages of approval based on information provided by the stakeholder. The system will

then be installed on the stakeholder’s computer. The stakeholder will enter new

information and update the preloaded information to test the system. This includes

publishing accepted articles to the Online Journal and accessing these from a remote

location by multiple simultaneous users.

        Any discrepancies between the behavior described in the SRS and the actual

system will be corrected and the system will be retested.


4.2     Beta Testing

        Any problems detected by the stakeholder within six months of installation will

be reported to the development team. After correction, a further six month period for beta

testing will ensue under the same regulations. All costs for this work are covered by the

original contract.




Software Testing Plan                       10                                 April 22, 2004

								
To top