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...........................................................................................................................3
2.1. Features to be tested........................................................................................................3
2.2. Features not to be tested..................................................................................................4
2.3. Testing tools and environment........................................................................................4
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.....................................................................5
3.1.4. Test Procedure..........................................................................................................5
Bibliography...............................................................................................................................7
APPENDIX A. TEST LOGS.....................................................................................................8
A.1. Log for test 1..................................................................................................................8
A.1.1. Test Results.............................................................................................................9
A.1.2. Incident Report......................................................................................................11

2
SOFTWARE TESTING
1. INTRODUCTION
1.1. System Overview
The eStage application is developed for the management of the online backstage and
the application is designed to select the role of the each of the stakeholders associated with
the management of the backstage. The user needs to login into the information system by
selecting the roles and pass the authentication mechanism for using the different features
provided by the system. On successful login the user is redirected to the welcome page and
different links are provided for the different users. The user can select different options such
as home, logoff, competitors, discipline and sections. The user can get the details of all
processes on selecting the appropriate option and use the system wisely. The competitors can
register into the information system with all their details and the different functionality are
provided for each of the users with different roles. Like the stage manager can move the
competitor, withdraw or change the sequence of the competitors. The results or the
judgement can also be recorded in the information system by logging into the system and
inputting the scores and the results for the management of the information and automatically
distribute the results to the competitors.
1.2. Test Approach
For proceeding with the testing of the software application different approach must be
evaluated and the best approach should be selected for the testing the developed online
backstage management system. The limitation of the project is needed to be identified by
analysing the scope and objective of the project. The test document is prepared by following
the below testing on the developed information system.
Unit Testing – The unit testing is performed for the verification of thee codes and the logics
used for the development of the programs and it is compared with the current structure of the

3
SOFTWARE TESTING
framework. It is performed in the final stage of the software development for reducing the
errors and the bugs in the end product.
Integration Testing – It is used for testing the functionality of the developed software
product and it is done by developing the software into different modules and integrating it
with each other for finding its compatibility with the other module. For proceeding with the
system integration testing it should be evaluated in different platform such that it can run on
different hardware and software configuration.
Business requirement – The testing of the online backstage management software should be
done for the verification of the requirement meet by the solution and reduce the errors in the
final software product developed for the management of the information and functionality
required by the organization. The software product should be aligned with the business
requirement and the different criteria that should be meet by the information system should
be evaluated and tested for management of the defects in the final software. Different test
case should be designed and the test results should be documented for troubleshooting the
information system and increasing its efficiency.
User acceptance testing – A group of friendly users should be involved in the testing of the
information system and the main objective of this testing is to analyse the usability of the
information system. The interface of the final product should be developed such that thee
user does not face any difficulty for finding the different function and end to end flow of the
information should be identified such that the errors can be mitigated. The main participant of
the user acceptance testing can be the users for whom the information system is targeted and
different test case should be developed.
2. TEST PLAN
2.1. Features to be tested