Software Test Documentation for eStage Backstage Management System

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.................................................................................................................3
2. TEST PLAN...........................................................................................................................4
2.1. Features to be tested........................................................................................................4
2.2. Features not to be tested..................................................................................................5
2.3. Testing tools and environment........................................................................................5
2.4. Traceability Matrix..........................................................................................................5
3. TEST CASES.........................................................................................................................6
3.1. Case 1..............................................................................................................................6
3.1.1. Purpose.....................................................................................................................7
3.1.2. Inputs........................................................................................................................7
3.1.3. Expected outputs & Pass/Fail Criteria.....................................................................7
3.1.4. Test Procedure..........................................................................................................7
3.2. Case 2..............................................................................................................................7
3.2.1. Purpose.....................................................................................................................8
3.2.2. Inputs........................................................................................................................8
3.2.3. Expected outputs & Pass/Fail Criteria.....................................................................8
3.2.4. Test Procedure..........................................................................................................8
3.3. Case 3..............................................................................................................................8
3.3.1. Purpose.....................................................................................................................8

2
SOFTWARE TESTING
3.3.2. Inputs........................................................................................................................8
3.3.3. Expected outputs & Pass/Fail Criteria.....................................................................9
3.3.4. Test Procedure..........................................................................................................9
3.4. Case 4..............................................................................................................................9
3.4.1. Purpose.....................................................................................................................9
3.4.2. Inputs........................................................................................................................9
3.1.3. Expected outputs & Pass/Fail Criteria.....................................................................9
3.1.4. Test Procedure........................................................................................................10
4. Gantt Chart...........................................................................................................................12
5. Budget..................................................................................................................................13
Test Results......................................................................................................................14
Incident Report.................................................................................................................15
Conclusion................................................................................................................................16
Bibliography.............................................................................................................................18
1. INTRODUCTION
1.1. System Overview
This application eStage has been developed to manage the backstage online as well as the
designing is done in selection of role of every stakeholder who is associated with backstage
management. There is a need for the user to access the information system by logging into it
with selection of roles. The user can use the various features of the system by passing the
authentication mechanism. When a user successfully logs in, he is redirected to welcome

3
SOFTWARE TESTING
page as well various links provided by a multitude of users. The user has a variety of options
to select like home, discipline, competitors, logoff as well as sections. Information about all
the processes can be obtained by the user on selection of appropriate option. The competitors
by putting in all the details can register in to the information system, they can also access
various functions with all those roles of different variety. It is similar to the stage manager
moving, withdrawing or changing the competitor sequence. The judgement results can also
be entered into this information system so that they can be used efficiently for future
purposes.
1.2. Test Approach
Different kinds of approaches need to be evaluated in case of software application testing.
After all the approaches has been evaluated, the nest among them needs to be selected to
develop backstage online management system. For any project, it is important to identify its
limitations, similarly in this project too it needs to be identified. This identification is done
with the help of scope analysis as well as project objective. The preparation of test document
is done by following certain testing methods given below.
Unit Testing – This testing is done for code verification in this project as well as
development of logics so that it can be compared with the pre-existing framework. This is an
important testing to be performed as it is the last stage to develop software to reduce any
errors as well as bugs for the final product.
Integration Testing – The integration testing is used for testing functionality of the software
product that has been developed. This testing is done by segregating the product into different
modules and then assimilating it all together so that each module is compatible with each
other. To achieve this, another platform is required to be used so that it can be checked
whether it could be run on different hardware as well as software configuration.