Software Testing Plan

Document Sample
Software Testing Plan Powered By Docstoc
					CON.fusion                                                                          Software Testing Plan


Table of contents
1. Introduction ......................................................................................... 3
  1.1    Document Purpose ......................................................................... 3
  1.2    Document Scope............................................................................ 3
  1.2    System Overview ........................................................................... 4
  1.4    Document Overview ....................................................................... 4

2. Software Test Plan ............................................................................... 4
  2.1   The Testing Process ....................................................................... 4
  2.2   Client Acceptance Test Plan ............................................................. 5
  2.3   Functional Test Plan ....................................................................... 6

3. Detailed Client Acceptance Test Plan .................................................... 7
  3.1     Test Case Design for all Clients “Provide Dynamic Page” ..................... 7
  3.2     Test Case Design for all Clients “Checking that links work” .................. 8
  3.3     Test Case Design for CIT “Reading the correct file extension” .............. 8
  3.4     Test Case Design for CIT “Document Passwords” ............................... 9
  3.5     Test Case Design for CIT “Functionality” ........................................... 9
  3.6     Test Case Design for CTD “Script Plugs into WebCT” ........................ 10
  3.7     Test Case Design for Solution 2 Distance Learning “Servlet to Select
  Correct Student Information” .................................................................. 11
  3.8     Case Specification for Solution 2 Distance Learning
  “Students ability to sort information” ........................................................ 11
  3.9     Test Case Design for Solution 3 Distance Learning “Scripts ability to
  select the correct file”............................................................................. 12
  3.10      Test Case Design for Solution 3 Distance Learning “Scripts ability to
  imbed information into the correct database” ............................................ 12
  3.11      Test Case Design for Solution 3 Distance Learning “Scripts ability a
  activate by it self at a specific time” ......................................................... 12

4. Detailed Functional Test Plan ............................................................. 13
  4.1    Test Case Design for All Clients “Provide Dynamic Page” ................... 13
  4.2    Test Case Design for All clients “Checking that links work” ................ 13
  4.3    Test Case Design for All Clients “Reading the correct file extension” ... 14

Computer Information Technology CIT .................................................. 15
  4.4  Test Case Design for CIT “Document Passwords” ............................. 15
  4.5  Test Case Specification for CIT “MySQL Database not Present ” ......... 15
  4.6  Test Case Design for CIT “Functionality” ......................................... 16

Customised Training and Development .................................................. 17
  4.7  Test Case Design for CTD “Plug into webCT” ................................... 17

Swinburne Distance Learning ................................................................. 17
  4.9     Test Case Design for Solution 2 Distance Learning “Servlet selects
  relevant student information” .................................................................. 17
  4.10      Test Case Design for Solution 2 Distance Learning “Students ability to
  sort information” ................................................................................... 18
  4.11      Test Case Design for Solution 2 Distance Learning “Servlet has access
  to Students database” ............................................................................ 18
  4.12      Test Case Design for Solution 2 Distance Learning “No connecting to
  students database” ................................................................................ 18
  4.13      Test Case Design for Solution 3 Distance Learning “Scripts ability to
  select the correct file”............................................................................. 19
  4.14      Test Case Design for Solution 3 Distance Learning “Scripts ability to
  imbed information into the correct database” ............................................ 19
  4.15      Test Case Design for Solution 3 Distance Learning “Scripts ability
  activate by it self at a specific time” ......................................................... 20


                                                                                              Page 1 of 23
CON.fusion                                                                         Software Testing Plan




Requirements Traceability ..................................................................... 20
  5.2   Requirements Traceability for CIT. ................................................. 20
  5.3   Requirements Traceability for Customised Training and Development. 20
  5.4   Requirements Traceability for Swinburne Distance Learning. ............. 20
Appendix A:     Definitions and Abbreviations .............................................. 21
Appendix B:     Review of Test Plan ............................................................ 21
Appendix C: Errors Check List ..................................................................... 23

Appendix C:         Errors check list ................................................................. 23




                                                                                            Page 2 of 23
CON.fusion                                                        Software Testing Plan


Software Testing Plan

1.        Introduction

1.1       Document Purpose

The purpose of this document is to provide the clients of CIT, Customised
Training and Development, Distance Learning along with the development team
CON.fusion a detailed outline of the testing procedures to be undertake for each
department‟s development project. The document will specify –

         Functional test plan
         User acceptance test plan
         Testing approach (black box and white box testing)
         Tools and techniques
         Constraints
         Environmental

1.2       Document Scope

The development team has three different clients all coming under the one
company. This report will be written in sections relating to that departments
project requirements.

CIT - As this will be a JAVA based script which will produce a dynamic web page,
the testing department will look at a number of different areas and functions
relating to the project.

         Can the page be implemented on to the server?
         Does the script produce a page based on the HTML code provided?
         Does the script pick up and imbed the correct files as specified?
         Do links work as intended?
         Do secure document prompt the user for the password?
         Does the site still maintain it functionally?
         Does the file system and producing of the web page remain the same?
         Does the page sill maintain the same look as before?

Customised Training and Development WebCT- As this is a similar project to
that of CIT department, the problems being tested will be very similar.
This department is after automated page to make up system plus some
embedded perl script so that the present application can recognize the new script.

         Does the embedded perl script run the new code?
         Does the script produce a page based on the HTML code provided?
         Does the script pick up and imbed the correct files as specified?
         Do links work as intended?
         Does the file system and producing of the web age remain the same?

Swinburne Distance Learning – This project has three parts to it, the first will
be to imbed the automated page make up script on to there system so that the
department can have a promotional web page that is automatically generated.
The second step in the process will be to test a JAVA servlet site which will be
used by the student body to view mark relating the exams and assignments. The
third part will be to create an Automated File Transfer script. The development
team will be looking for the following.

         Does the script produce a page based on the HTML code provided?
         Does the script pick up and imbed the correct files as specified?
         Do links work as intended?
                                                                          Page 3 of 23
CON.fusion                                                          Software Testing Plan


         Does the site still maintain it functionally?
         Does the file system and producing of the web age remain the same?
         Does the page sill maintain the same look as before?
         Does the Servlet connect to the database?
         Does the Servlet format the page as required?
         Does the Servlet validate uses logging in and out?
         What happens when invalided inputs are entered in the text files?
         Does the Script Select the right files?
         Does the script activate at the correct time?
         Does the script send the data to the correct spot?
         When the data has been selected it format correctly be for it is sent to the
          database?

1.2       System Overview

As mentioned before the development team has three different clients all coming
under the one company.

The first section of the development project all three clients will be receiving, this
will be a JAVA based Automated Page Make up Servlet, which will scan a file tree
and generate a web page based on what‟s in side a specific file.

Another client will be receiving a Servlet based front end, which will allow
students to log in and check there results, this will be connected to an MSSQL
database.

Lastly a perl or windows scripting language will be used to create a file transfer so
that file stored in one database can be formatted so that the can be stored in an
MSSQL database this will put an end to the current manual process. For more
information please refer to scope section 1.0 feasibility document section 2.2.

1.4       Document Overview

This document, the Software Test Document (STD), identifies the software test
plan and the details of the testing to be carried out for the following projects.

         CIT – Computer Information Technology.
         Customised Training and Development.
         Swinburne Distance Learning.

2.        Software Test Plan

This section describes the testing plans for testing the Java servlet Automatic web
generation tool, Student servlet database access and the file transfer script. In
general, this includes the client acceptance test and the functional testing for all
products being developed.


2.1       The Testing Process

The testing will be conducted at different stages of the Rapid Application
Development Project (RAD). As there are a number of different products being
developed the way in which some applications are tested will vary some will be
conducted for individual units, which then will be integrated to be a complete
system finally and other will be tested as the project develops

The testing will be done using black box as well as white box techniques. The
testing leader for all three products is Bradley Clift.

                                                                            Page 4 of 23
CON.fusion                                                                      Software Testing Plan


For the system testing to occur on schedule the client must have purchased and
set up a suitable hardware and software platform (See SRS). Suitable networked
workstations, printing facilities and access to the software to be tested must be
made available to testers. For regression testing to be performed satisfactorily
during the maintenance phase a member for the three departments represented
in this document must be actively involved in using the system. The client must
assist in beta testing at their site and ensure their availability to conduct client
acceptance testing.

The deliverables are templates to be used for testing, test plan, actual tests
conducted and their results recorded in defect logs supported by manual or
automated testing scripts. The testing report should be produced at the end to
provide summary. The client must approve and sign all of the relevant testing
documents.

2.2      Client Acceptance Test Plan

This section documents a high level view of the client acceptance test plan and
traces the functionalities under test against the SRS of the software. In
particular, the client acceptance test plan addresses the client acceptance
criteriain the SRS.

Table 1 General Client Acceptance Test Plan for All Clients

Functionality    Requirements        Description/Main             Feature to be         Test Spec.
                    In SRS           Responsibilities                tested             And Design
  Provide                       Script has to create page      Scripts ability to
  Dynamic         SRS 3.1.1,    base of files in file tree     read and create             4.1.1
   page                                                        page

Clicking Links                  When a user clicks a link on   Links send the user
                  SRS 3.1.2     the site it should send them   to the correct page.        4.2.1
                                to the correct page
Reading the                     Site has to know what files    Scripts ability to
correct file      SRS 3.1.3     it is allowed to accept.       recognize files.            4.3.1
extinction

Table 2 Client acceptance test plan for CIT

Functionality    Requirements        Description/Main             Feature to be         Test Spec.
                    In SRS           Responsibilities                tested             And Design
Password and                    Once user is on web site       Script must prompt
logon for         SRS 3.2.1     and selects a confidential     user for password if        4.4.1
confidential                    document it will prompt the    it meets
documents                       user for password              requirements
Functionality                   Site still has to have the     Scripts ability to
                  SRS 3.2.2     same look and feel as old      keep it functionality       4.6.1
                                site


Table 3 Client acceptance test plan for Customised Training and Development

Functionality    Requirements        Description/Main             Feature to be         Test Spec.
                    In SRS           Responsibilities                tested             And Design
  Plug in to                    Script has to interface with    Does the software
   webCT          SRS 3.3.1               webCT                  plug into webCT           4.7.1




                                                                                        Page 5 of 23
CON.fusion                                                                            Software Testing Plan


Table 4 Client acceptance test plan for Swinburne Distance Learning

Functionality     Requirements        Description/Main               Feature to be            Test Spec.
                     In SRS           Responsibilities                  tested                And Design
Servlet can                      Once student has logged in,      That relevant
pull up and                      the servlet will gather all      student information            4.9.1
format the         SRS 3.4.1     the information relevant to      is displayed to the
correct                          that student.                    authored logged on
student                                                           user.
information
Students                         A button will support this
ability to sort    SRS 3.4.2     function and when pressed                                      4.10.1
information                      the marks will be sorted
                                 base of selection
Automatic                        Script has to be able to         Is script able to read
File Transfer      SRS 3.4.3     access and read data in site     data inside file.             4.13.1
selects                          a file.
correct files
Automatic                        Once script has read file is     Is script able to
File Transfer      SRS 3.4.4     it able to format and            implant data.                 4.14.1
is able to                       implant data into a new
format and                       database.
Can script                       Script will have a config fill   Script ability to
start up by        SRS 3.4.5     where it will get all it         activate at a specific        4.15.1
its self at a                    instructions from, one           time.
specific time.                   function will be to active at
                                 a specific time.


2.3       Functional Test Plan
This section documents traces the functionalities under test against the SRS
developed for CON.fusion clients.
Table 1 General Functional Test Plan for All Clients

Functionality     Requirements        Description/Main               Feature to be            Test Spec.
                     In SRS           Responsibilities                  tested                And Design
  Provide                        Script has to create page        Scripts ability to
  Dynamic          SRS 3.1.1     base of files in file tree       read and create                4.1.1
   page                                                           page

Clicking Links                   When a user clicks a link on     Links send the user
                   SRS 3.1.2     the site it should send them     to the correct page.           4.2.1
                                 to the correct page
Reading the                      Site has to know what files      Scripts ability to
correct file       SRS 3.1.3     it is allowed to accept.         recognize files.               4.3.1
extinction




Table 2 functional test plans for CIT

Functionality     Requirements        Description/Main               Feature to be            Test Spec.
                     In SRS           Responsibilities                  tested                And Design
Password and                     Once user is on web site         Script must prompt
logon for          SRS 3.2.1     and selects a confidential       user for password if           4.4.1
confidential                     document it will prompt the      it meets
documents                        user for password.               requirements.
MySQL                            The database will house          What will happen if
Database not          NA         user name and password           database is not                4.5.1
Present                          for accessing secure             present.
                                 documents.
Functionality                    Site still has to have the       Scripts ability to
                   SRS 3.2.2     same look and feel as old        keep it functionality.         4.6.1
                                 site.




                                                                                              Page 6 of 23
CON.fusion                                                                           Software Testing Plan


Table 3 functional test plan for Customised Training and Development

Functionality    Requirements        Description/Main               Feature to be            Test Spec.
                    In SRS           Responsibilities                  tested                And Design
Plug in to                      Script has to interface with     Does the software              4.7.1
webCT             SRS 3.3.1     webCT.                           plug into webCT


Table 4 functional test plan for Swinburne Distance Learning

Functionality    Requirements        Description/Main               Feature to be            Test Spec.
                    In SRS           Responsibilities                  tested                And Design
Servlet                         This function will require       Scripps ability to
selects                         the servlet to select the        selects the correct            4.9.1
relevant          SRS 3.4.1     relevant student                 student information.
student                         information based on there
information                     password and logon and
                                display the results to the
                                screen.
Students                        A button on the web site         The servlets ability
have there        SRS 3.4.2     will have the responsibility     to sort marks.                4.10.1
sort                            of sorting student marks
functionality                   and results
Servlet has                     Student access Servlet has       Servlet has a
access to            NA         to have access the MS            connection.                   4.11.1
Students                        SQL SERVER 7 to access
database                        relevant student
                                information.
Automatic                       Script has to be able to         Is script able to read
File Transfer     SRS 3.4.3     access and read data in site     data inside file?             4.13.1
selects                         a file.
correct files
Automatic                       Once script has read file is     Is script able to
File Transfer     SRS 3.4.4     it able to format and            implant data?                 4.14.1
is able to                      implant data into a new
format and                      database.
implant data
Can script                      Script will have a config fill   Script ability to
start up by       SRS 3.4.5     where it will get all it         activate at a specific        4.15.1
its self at a                   instructions from, one           time.
specific time.                  function will be to active at
                                a specific time.


3.       Detailed Client Acceptance Test Plan
This section describes the details for the Client Acceptance Test. The
development team will demonstrate the functionalities to all projects to the
respective clients using the following test specifications listed bellow.


General Client Acceptance Test Plan for All Clients

3.1      Test Case Design for all Clients “Provide Dynamic Page”

This section describes the specifications of the test case for testing how well the
software handles a users request to the script.

3.1.1 Test Case Specification for all Clients “Provide Dynamic Page”

Features to be tested: The feature to be tested will be the scripts ability to
generate a web page a specified in the SRS

Requirements: Internet Connection, also see SRS 4.2.1.

Expected Behavior: User should make URL request this should activate the
script and a web site should be generated as requirements specify.

Test Case Design: Same as test case 4.1.1 of this document.

                                                                                             Page 7 of 23
CON.fusion                                                           Software Testing Plan


3.2    Test Case Design for all Clients “Checking that links work”

This section describes the specifications of the test case for testing how well the
links on the site work, do the links go to the correct places.

3.2.1 Test Case Specification for all clients “Checking that links work”

Features to be tested: Testing for the scripts ability to generate links, links
should then take the user to the respective page.

Requirements: Internet Connection, also see SRS 4.3.1. (.2)

Expected Behavior: The user will be required to select a number of links, once
selected the links should take the user to the corresponding page or download the
correct document.

Test Case Design: Same as test case 4.2.1 of this document.


3.3    Test Case Design for CIT “Reading the correct file extension”

This section describes the specifications of the test case for testing if the script
able to recognize the correct file extinction from a config script.

3.3.1 Test Case Specification for CIT “Reading the correct file extension”

Features to be tested: The feature to be tested will be the scripts ability to
recognize the correct file extinction from a config script.

Requirements: Internet Connection, also see SRS 4.2.1.

Expected Behavior: The site should be able to handle file extensions specified in
the config script.

Test Case Design: Same as test case 4.3.1 of this document.




                                                                             Page 8 of 23
CON.fusion                                                           Software Testing Plan


Computer Information Technology CIT

3.4    Test Case Design for CIT “Document Passwords”

This section describes the specifications of the test case for testing if the script
can place a password of document based on the folder it has been placed in.

3.4.1 Test Case Specification for CIT “Document Passwords”

Features to be tested: The feature to be tested will be the scripts ability to
prompt for a password based on a specific document; if password is accepted, the
user in this case the teacher should get access.

Requirements: Internet Connection, also see SRS 4.2.1. (.2)

Expected Behavior: User should place a document in the specific folder, the link
should then be posted to the web and when clicked should prompt for a
password.

Test Case Design: Same as test case 4.4.1 of this document.

3.5    Test Case Design for CIT “Functionality”

This section describes the specifications of the test case for testing if the script
able to keep Functionality „same look and feel as the old CGI site.

3.5.1 Test Case Specification for CIT “Functionality”

Features to be tested: The feature to be tested will be the scripts ability to
ability to keep Functionality „same look and feel as the old CGI site.

Requirements: Internet Connection, also see SRS 4.2.1.

Expected Behavior: The new site should have the same look and feel as old
site.

Test Case Design: Same as test case 4.6.1 of this document.




                                                                             Page 9 of 23
CON.fusion                                                          Software Testing Plan


Customised Training and Development

3.6    Test Case Design for CTD “Script Plugs into WebCT”
This section describes the specifications of the test case for testing if the
developed script will plug into the third party product WebCT.

3.6.1 Test Case Specification for CTD “Script Plugs into WebCT ”

Features to be tested: Testing for the scripts ability to work along side webCT.

Requirements: Internet Connection, also see SRS 4.2.2.

Expected Behavior: The script should run under the WebCT environment and
should generate pages see testing document 3.4.

Test Case Design: Same as test case 4.7.1 of this document.




                                                                           Page 10 of 23
CON.fusion                                                           Software Testing Plan


Distance Learning

Test Case Design for Solution 1 Distance Learning

Same as all clients

3.7      Test Case Design for Solution 2 Distance Learning “Servlet to Select
Correct Student Information”


This section describes the test case for testing if the servlet is able to select the
correct information for a specific student.

3.7.1 Test Case Specification for Solution 2 Distance Learning “Servlet to
Select   Correct Student Information”

Features to be tested: The feature to be tested will be the ability for the servlet
to select the correct students information out of the database based on there
password and logon.

Requirements: Internet Connection, also see SRS section 4.2.3 (.2)

Expected Behavior: Based on the student‟s password and logon the script
should select and display the relevant student information from the database.

Test Case Design: Same as test case 4.9.1 of this document.


3.8      Case Specification for Solution 2 Distance Learning
“Students ability to sort information”


This section describes the specifications for testing the servlets ability to sort
student marks based on the relevant selections.

3.8.1 Case Specification for Solution 2 Distance Learning
         “Students ability to sort information”

Features to be tested: The servlets ability to sort student marks based on the
relevant selections.

Requirements: Internet Connection, also see SRS section 4.2.3 (.2)

Expected Behavior: The servlet should display the student marks ordered in a
specific way.

Test Case Design: Same as test case 4.10.1 of this document.




                                                                            Page 11 of 23
CON.fusion                                                              Software Testing Plan




3.9     Test Case Design for Solution 3 Distance Learning “Scripts ability to
select the correct file”


In this section we will be testing solution 3 for distance learning, we will be
testing the scripts ability to select the correct file.

3.9.1 Test Case Specification for Distance Learning “Scripts ability to select the
correct file ”

Features to be tested: Is the script able to select the correct file and extract
data form with in that file.

Requirements: Internet connection.

Expected Behavior: Script should show that data has been extracted and it‟s
ready for exporting.

Test Case Design: Same as test case 4.13.1 of this document.


3.10    Test Case Design for Solution 3 Distance Learning “Scripts ability to
imbed information into the correct database”


In this section we will be testing the scripts ability, once the correct file has been
integrated, can the script then format and imbed that information into the correct
database.

3.10.1 Test Case Specification for Distance Learning “Scripts ability to imbed
information into the correct database ”

Features to be tested: once the correct file has been integrated can the script
then format and imbed that information into the correct database.

Requirements: Internet Connection, also see SRS section 4.2.3 (.2)

Expected Behavior: Script should show that the data has been extracted, the
script should then format and imbed it into the SQL Server 7 database database.

Test Case Design: Same as test case 4.14.1 of this document.


3.11    Test Case Design for Solution 3 Distance Learning “Scripts ability a
activate by it self at a specific time”


In this section we will be testing the scripts ability to auto start.

3.11.1 Test Case Specification for Distance Learning “Scripts ability activate by
           it self at a specific time”

Features to be tested: The scripts ability to auto start.

Requirements: Access to internet, also sees SRS section 4.2.3.

Expected Behavior: The script should start to interrogate a specific file and then
format and imbed it into the new database

Test Case Design: Same as test case 4.15.1 of this document.



                                                                               Page 12 of 23
CON.fusion                                                          Software Testing Plan


4. Detailed Functional Test Plan

This section describes the system testing and performance testing test plan.

Standard Environment: The test cases will run under the standard environment
of:
      Internet connection.
      Web browser, Netscape – Internet Explore.
      Access to Tomcat server.

Any other specific hardware and software requirement for the test cases will be
listed in the environment needs section for each test case.



Detailed Functional Test Plan for All Clients

4.1       Test Case Design for All Clients “Provide Dynamic Page”

This section describes the specifications for testing how well the software handles
a users request to the script.

4.1.1 Test Case Specification for All Clients “Provide Dynamic Page”

Features to be tested: The feature to be tested will be the scripts ability to
generate a web page as specified in the SRS.

Requirements: Internet access, also see SRS section 3.2.1 (.3)

Expected Behavior: User should make URL request, this should then activate
the script and a web site should be generated as requirements specify.

Test Case Design:

Test ID                Inputs required       Environment need     Output expected
4.1.1.1                User URL Request      Standard             The servlet should be
                                                                  activated creating a
                                                                  web site based on
                                                                  example in 4.1.1, 4.1.3
                                                                  of SRS


4.2       Test Case Design for All clients “Checking that links work”

This section describes the specifications for testing how well the links on the site
work, do the links take the user to the correct pages.

4.2.1 Test Case Specification for All Clients “Checking that links work”

Features to be tested: Testing for the scripts ability to generate links, links
should then take the user to the respective page.

Requirements: Internet access, also see SRS section 3.2.1 (.3)

Expected Behavior: The user will be required to select a number of links, once
selected the link should take the user to the correct page or download the correct
document.




                                                                           Page 13 of 23
CON.fusion                                                              Software Testing Plan


Test Case Design:

Test ID                 Inputs required            Environment need   Output expected
4.2.1.1                 Active click is made by    Standard           The script should then
                        user to a secure link                         prompt for a password
                                                                      and log on.


4.3       Test Case Design for All Clients “Reading the correct file extension”

This section describes the test case for testing the script ability to recognize the
correct file extension from a config script.

4.3.1 Test Case Specification for All Clients “Reading the correct file extension”

Features to be tested: The feature to be tested will be the scripts ability to
recognize the correct file extension from a config script.

Requirements: Internet Connection, also see SRS 4.2.1.

Expected Behavior: The site should be able to handle file extensions specified in
the config script.

Test Case Design:

Test ID                 Inputs required            Environment need   Output expected
4.3.1.1                 User will have to put a    Standard           The script should then
                        new file extension link                       imbed the file on the
                        .AVI and the script will                      page.
                        have to recognize it.




                                                                               Page 14 of 23
CON.fusion                                                            Software Testing Plan


Computer Information Technology CIT

4.4       Test Case Design for CIT “Document Passwords”

This section describes the specifications for testing if the script can place a
password on a document which has been placed in a folder called secure.

4.4.1 Test Case Specification for CIT “Document Passwords”

Features to be tested: The feature to be tested will be the scripts ability to
prompt for a password if a specific document is requested; if password is
accepted user in this case the teacher should get access to the requested
document.

Requirements: Internet access, also see SRS section 3.2.1 (.3)

Expected Behavior: User should place a document in the specific folder, the link
should then be posted to the web and when clicked should prompt for a
password.

Test Case Design:

Test ID                Inputs required           Environment need    Output expected
4.4.1.1                Active click is made by   Standard            The script should then
                       user to a secure link                         prompt for a password
                                                                     and log on.
4.4.1.2                User is then to enter     Standard            The script should then
                       the ID and Password in                        validate the passwords
                       the test boxes provided                       and then depending on
                                                                     password and log on
                                                                     allow authorized users
                                                                     to view the document.


4.5       Test Case Specification for CIT “MySQL Database not Present ”

This section describes test what happens if the database for password document
access is missing.

4.5.1 Test Case Specification for CIT “MySQL Database not Present”

Features to be tested: The feature to be tested will be not having a present
database for the secure database file access.

Requirements: Internet access

Expected Behavior: User should not be able to access the required document
password.

Test Case Design:

Test ID                Inputs required           Environment need    Output expected
4.5.1.1                Password                  Database does not   The script should then
                                                 exist.              prompt for a password
                                                                     and system log on.




                                                                              Page 15 of 23
CON.fusion                                                           Software Testing Plan



4.6       Test Case Design for CIT “Functionality”

This section describes the test case for testing if the script is able to keep
Functionality „look and feel‟ of the old CGI site.

4.6.1 Test Case Specification for CIT “Functionality”

Features to be tested: The feature to be tested will be the scripts ability to
ability to keep Functionality „same look and feel as the old CGI site.

Requirements: Internet connection, also see SRS section 3.2.1 (.3).

Expected Behavior: The new site should have the same look and feel as old
site.

Test Case Design:

Test ID                Inputs required        Environment need     Output expected
4.6.1.1                User has to make URL   Standard             The script should then
                       request to site                             look the same as the
                                                                   CGI CIT.




                                                                            Page 16 of 23
CON.fusion                                                              Software Testing Plan


Customised Training and Development


4.7       Test Case Design for CTD “Plug into webCT”

This section describes the test case for testing if the new dynamic page
generation tool can plug into webCT

4.7.1 Test Case Specification for CTD “Script Plugs into WebCT ”

Features to be tested: Testing for the scripts ability to work along side webCT.

Requirements: Internet access, also see SRS section 4.2.2 (.2)

Expected Behavior: The script should run under the WebCT environment and
should generate pages see testing document 3.4.

Test Case Design:

Test ID                  Inputs required            Environment need   Output expected
4.7.1.1                  User URL Request           Standard           The servlet should be
                                                                       activated creating a
                                                                       web site based on
                                                                       example in 4.1.3 of
                                                                       SRS


Swinburne Distance Learning

4.8       Test Case Design for Solution 1 Distance Learning

4.8.1 Test Case Specification for Solution 1 Distance Learning

Same as other clients.


4.9       Test Case Design for Solution 2 Distance Learning “Servlet selects
relevant student information”


This section describes the specifications for testing the servlets ability to select
the correct student‟s details from the database.

4.9.1 Test Case Design for Solution 2 Distance Learning “Servlet selects
          relevant student information”

Features to be tested: The servlets ability to select the correct student‟s details
from the database.

Requirements: Internet access, also see SRS section 4.2.3 (.2)

Expected Behavior: The servlet should display the relevant student‟s
information.

Test Case Design:

Test ID                  Inputs required            Environment need   Output expected
4.9.1.1                  Student will have to log   Standard           The logged in users
                         in                                            details should be
                                                                       displayed.




                                                                                Page 17 of 23
CON.fusion                                                               Software Testing Plan


4.10       Test Case Design for Solution 2 Distance Learning “Students ability to
sort information”


This section describes the specifications for testing the servlets ability to sort
student marks based on the relevant selections.

4.10.1 Test Case Design for Solution 2 Distance Learning “Student’s ability to
           sort information”

Features to be tested: The servlets ability to sort student marks based on the
relevant selections.

Requirements: Internet access, also see SRS section 4.2.3 (.2)

Expected Behavior: The servlet should display the student marks ordered in a
specific way.

Test Case Design:

Test ID                   Inputs required            Environment need   Output expected
4.10.1.1                  Student will have to log   Standard           The logged in user
                          in and then ask the                           details should be
                          page to sort marks                            displayed.

4.11       Test Case Design for Solution 2 Distance Learning “Servlet has access
to Students database”


This section describes the specifications for testing the servlets ability to connect
to the database on the server.

4.11.1 Test Case Design for Solution 2 Distance Learning “Servlet has access
           to Students database”

Features to be tested: The servlets ability to connect to the local database.

Requirements: Internet access, Also SRS 4.2.3.

Expected Behavior: The servlet should allow user to login

Test Case Design:

Test ID                   Inputs required            Environment need   Output expected
4.11.1.1                  User will have to log in   Standard           The user should be
                          by supplying username                         able to login.
                          and password.


4.12       Test Case Design for Solution 2 Distance Learning “No connecting to
students database”


This section describes the specifications for testing the servlet with no database
connection

4.12.1 Test Case Design for Solution 2 Distance Learning “No connecting to
           students database”

Features to be tested: Trying to log into the servlet with no database on the
back end.

Requirements: Internet access

Expected Behavior: The servlet should display an error either a pre coded error
or a inbuilt system error.
                                                                                 Page 18 of 23
CON.fusion                                                                    Software Testing Plan




Test Case Design:

Test ID                       Inputs required            Environment need   Output expected
4.12.1.1                      User will have to log in   No database        The logged in user
                                                                            details should be
                                                                            rejected.


4.13       Test Case Design for Solution 3 Distance Learning “Scripts ability to
select the correct file”


In this section we will be testing solution 3 for distance learning, we will be
testing the scripts ability to select the correct file.

4.13.1 Test Case Specification for Solution 3 Distance Learning “Scripts
           ability to select the correct file ”

Features to be tested: Is the script able to select the correct file and extract
data form with in the file.

Requirements: Internet connection.

Expected Behavior: Script should show that data has been extracted and it
ready for exporting.

Test ID                       Inputs required            Environment need   Output expected
4.13.1.1                      Make sure that config      Standard           Script should integrate
                              script is set up                              the information.



4.14       Test Case Design for Solution 3 Distance Learning “Scripts ability to
imbed information into the correct database”


In this section we will be testing solution 3 for distance learning, we will be
testing the scripts ability, once the correct file has been integrated can the script
then format and imbed that information into the correct database.

4.14.1 Test Case Specification for Solution 3 Distance Learning “Scripts
           ability to imbed     information into the correct database”

Features to be tested: once the correct file has been integrated can the script
then format and imbed that information into the correct database?

Requirements: Internet connection, also sees SRS section 4.2.3.

Expected Behavior: The script should show that the data has been extracted
from the script should then format and imbed it into the database.

Test Case Design:

Test ID                       Inputs required            Environment need   Output expected
4.14.1.1                      None                       Standard           Script should format
                                                                            and imbed information
                                                                            into database.




                                                                                      Page 19 of 23
CON.fusion                                                                         Software Testing Plan


4.15       Test Case Design for Solution 3 Distance Learning “Scripts ability
activate by it self at a specific time”


In this section we will be testing solution 3 for distance learning, we will be
testing the scripts ability to auto start.

4.15.1 Test Case Specification for Solution 3 Distance Learning “Scripts
            ability a activate by it self at a specific time”

Features to be tested: The scripts ability to auto start.

Requirements: Access to internet.

Expected Behavior: The script should start to interrogate a specific file and then
format and imbed it into the new database.

Test ID                    Inputs required            Environment need           Output expected
4.15.1.1                   None                       Standard                   Script should active
                                                                                 automatically.




Requirements Traceability

           Requirements       3.1.1   3.1.2   3.1.3
                In SRS
Test Id
4.1.1.1                           X
4.2.1.1                                   X
4.3.1.1                                           X

5.2        Requirements Traceability for CIT.

           Requirements       3.2.1   3.2.2   3.2.3
                 In SRS
Test Id
4.4.1.1                           X
4.4.1.2                           X
4.5.1.1                                   X
4.6.1.1                                           X

5.3        Requirements Traceability for Customised Training and Development.

           Requirements       3.2.1
                 In SRS
Test Id
4.7.1.1                           X

5.4        Requirements Traceability for Swinburne Distance Learning.

           Requirements       3.4.1   3.4.2   3.4.3    3.4.4     3.4.5   3.4.6
                 In SRS
Test Id
4.9.1.1                       X
4.10.1.1                              X
4.12.1.1                                      X
4.13.1.1                                               X
4.14.1.1                                                         X
4.15.1.1                                                                 X




                                                                                           Page 20 of 23
CON.fusion                                                         Software Testing Plan


References
    [1]      CON.fusion, “The SRS document”, 2002
    [2]      CON.fusion, “The Requirements Model”, 2002



Appendix A:            Definitions and Abbreviations

This section describes any general information that helps to understand this
software test document. This section contains an alphabetical listing of all
acronyms, abbreviations, and their meanings as used in this document and a list
of any terms and definitions needed to understand this document.
                Table of Definitions, Acronyms, and Abbreviations
Term/Acronym                 Definition/Description
Software Test Plan           A document that describes test plans and test case
                             specifications for testing the software.
Requirement                  What is need to carry out test plan.

Client acceptance test       What the client will need to see working in order for the test
                             to be successful.
Functional test              Testing specific functions of the project being developed
Functional requirement       A function required need by the application being developed
Non-Functional               A function not required by the application.
requirement
Interface requirement        Requirements for the user interface.
Software Requirements        A document describing the requirements of the proposed
Specifications (SRS)         system from the user‟s view point.
System Testing               The testing of the software application as a whole to see the
                             software works according to its specification. This can be
                             further divided into functional testing and performance
                             testing.

Appendix B:            Review of Test Plan

Criteria                                Yes/No     Severity   Explanation/Action undertaken
                                                              to correct
Testing Structure:
Are testing levels defined                 Yes      Medium    Detailed test plan
                                                              descriptions in sections 2.1, 3
                                                              and 4 of the Software Test
                                                              Plan
Are test support hardware/software         Yes      Medium    J Unit
identified
Are independent reviews planned            Yes      Medium    The test plan is reviewed by
                                                              the testing leader to ensure
                                                              consistency and
                                                              completeness.
Is a schedule shown for testing            No       Medium    The project schedule can be
activities                                                    referred to check the
                                                              schedule for testing activities.
Testing Control:
Are products and documents that            Yes       High     All the relevant deliverables
will be controlled identified                                 are identified through out the
                                                              test plan.



                                                                          Page 21 of 23
CON.fusion                                                  Software Testing Plan




Testing Standards:
Are standards listed for testing        No     Low     Templates supplied by CIT.
activities
Is an organization identified to        Yes    High    CON.fusion
enforce the standards
Is a mechanism identified to map        Yes    High    Refer to Requirements
requirements and specifications to                     Traceability (Section 5)
test cases
Testing Objectives and Priorities:
Is the testing philosophy defined       Yes   Medium   Refer to section 1 and section
                                                         2.1 of the (Software Test
                                                                    Plan)
Is importance of testability relative   Yes   Medium   Hardware/software
to other software characteristics                      requirements mentioned
discussed                                              would need to be set up
                                                       before testing
Documentation:
Is documentation approach               Yes     -      Supplied template is
discussed                                              amended and used
Is each contractually deliverable       Yes    High    Identified in project
testing document identified                            deliverables.
Is the organization responsible for     Yes     -      CON.fusion is responsible for
each contractually deliverable                         testing the software
document shown                                         completely and conducting
                                                       the client acceptance test.




                                                                    Page 22 of 23
CON.fusion                                                       Software Testing Plan


Appendix C: Errors Check List

For Coding and Debugging:

No.     Defect Type                     Description
   1.   Redundant Declarations
        1                               Duplicate variable declarations
   2.   Un-initialised Variables
        4                               Variables used in calculations not initialised
   3.   Defective Loops
        5                               Loops that terminate incorrectly
   4.   Redundant Code
        6                               Removal of these code will not affect the
                                        functionality
   5.  Duplicate Code Blocks
       7                                Similar blocks of code that should be in a method.
   6.  Unused Methods
       8                                Methods that have been declared, but not used.
   7.  Multiple Returns in a Method
       9                                A method that has more than one return statement.
   8.  Unused Input
       1                                User input that is ignored.
       0
   9. 1Poor Design Choices              Non-compliance with OO principles
       1
       Poor Coding in Switch Blocks
   10. 1                                Case statements that do nothing, incorrect break
       2                                statements
       Poor Coding in Loops
   11. 1                                Loops that create unnecessary variables and
       3                                declared variables that have visibility outside the
                                        loop block.
       Poor visibility decisions
   12. 1                                Visibility of methods and variables has not been
       4                                thought in detail. (Inappropriate use of protected,
                                        public and private).

Other Errors:

No.    Defect Type                      Description
   13. Clearly Named (Titled)           When multiple windows are displayed, is the name
       Screens                          of the window properly represented?
   14. Correct Exiting                  Does the window properly close?
   15. Invalid input into password      What happens when invalid input it add to password
       and logon test fields.           and logon screens?
   16. Can the page be implemented      Are the applicants being developed suitable to the
       on to the server?                software and hardware also being implemented?
   17. Do the intended solutions        Are the site being developed viewable on Netscape
       work on all browsers?            and internet explore browsers
   18. Does the Servlet validate uses   Can the servlets validate user‟s login and login out –
       logging in and out?              make sure sessions are not left open.
   19. Do the web pages work on         The web sites have to look similar on the following
       different browsers               browsers
                                                    Microsoft Internet Explorer
                                                    Netscape Navigator
                                                    Mozilla
   20. Does the screen keep its size    When user views the site does the site keep its size
       on different monitors            on different browsers
   21. Links one site work              Make sure that links on the web sites work both
                                        hyper and document based.
   22. Image loading                    Graphics have to load into the correct places as
                                        specified designer.




                                                                        Page 23 of 23