Software Test Documentation

Running head: SOFTWARE TESTING
Software Test Documentation
Name of the Student
Name of the University
Author’s Note

1
SOFTWARE TESTING
Table of Contents
1. INTRODUCTION..................................................................................................................2
1.1. System Overview............................................................................................................2
1.2. Test Approach.................................................................................................................2
2. TEST PLAN...........................................................................................................................4
2.1. Features to be tested........................................................................................................4
2.2. Features not to be tested..................................................................................................4
2.3. Testing tools and environment........................................................................................4
2.4. Traceability Matrix..........................................................................................................5
3. TEST CASES.........................................................................................................................5
3.1. Case 1..............................................................................................................................5
3.1.1. Purpose.....................................................................................................................5
3.1.2. Inputs........................................................................................................................5
3.1.3. Expected outputs & Pass/Fail Criteria.....................................................................6
3.1.4. Test Procedure..........................................................................................................6
4. Gantt Chart.............................................................................................................................7
5. Budget....................................................................................................................................7
Bibliography.............................................................................................................................10
APPENDIX A. TEST LOGS...................................................................................................12
A.1. Log for test 1................................................................................................................12
A.1.1. Test Results...........................................................................................................12
A.1.2. Incident Report......................................................................................................14

2
SOFTWARE TESTING
1. INTRODUCTION
1.1. System Overview
The application of eStage has been developed to manage online backstage while the
design of the application is made such that it would be able to select roles of each
stakeholders which have been associated with various managements of backstage. Users of
this system have to login in information system through selection of specific roles while also
passing authentication mechanism to use various features which are provided by this system.
When the user is login successfully, users are automatically redirected to welcome page in
which various links are provided accordingly to different users. The users could also select
various options like logoff, home, discipline, sections and competitors. All details could be
accessed by users by selection of appropriate options and also choosing system more wisely.
Registrations in the information system could be done by competitors through their details
after which various functionalities would be provided to every users having different roles.
Stage managers could also move competitors, change or withdraw sequences for competitors.
The results as well as judgements could be recorded as well in information systems through
logging into systems and inputting scores as well as results for managing information along
with automatically distributing results to its competitors.
1.2. Test Approach
In order to proceed with testing of software applications, various different approaches
should be evaluated so that selection of best approach could be done in order to test online
backstage system for management. The project limitation has been identified through analysis
on objective as well as scope of this project. The documents of test have been prepared
through analyzing below testing on developed information systems.

3
SOFTWARE TESTING
Unit Testing – In order to verify three codes as well as logics which are utilised for
developing programs, unit testing have to be performed after which it has to be compared
with current structure in that framework. For reducing bugs as well as errors in final report, it
is to be performed in final stages of software development.
Integration Testing – In order to test functionalities of developed software,
integration testing is done. This is done through the development of software in various
modules along with integration of this testing with other findings so that compatibility could
be found with other modules. Evaluation should be done with various platforms so that it
would be able to run in different software as well as hardware configurations.
Business requirement – Different test case should be designed and the test results
should be documented for troubleshooting the information system and increasing its
efficiency. The tests of this online backstage software for management have to be done to
verify requirements meets through solutions along with reducing errors in final product of
software which is being developed for managing functionality as well as information which
are required by organizations. All products of this software is to align with business
requirements. An evaluation has to be done on different criteria that needs to be met by
information systems. Tests should also be conducted to manage defects in final software.
User acceptance testing – While testing, friendly users should also be encouraged to
get involve who would also be helpful in analysing usability of this information system. The
final product interface has to be developed in such a way in which these users would not face
difficulties in finding various different functions. Information flow through end to end is to
be analysed spot error and steps should be taken to mitigate them. The important participants
of the testing of user’s acceptance are actual users who would be using this information
system, therefore rest cases have to be developed.