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
Introduction......................................................................................................................................2
System Overview.........................................................................................................................2
Test Approach..............................................................................................................................2
TEST PLAN....................................................................................................................................5
Features to be tested.....................................................................................................................5
Features not to be tested..............................................................................................................5
Functional and Non-Functional Requirement of the System:.....................................................5
Testing tools and environment.....................................................................................................6
Traceability Matrix......................................................................................................................7
TEST CASES..................................................................................................................................9
Case 1...........................................................................................................................................9
3.1.1. Purpose..........................................................................................................................9
3.1.2. Inputs.............................................................................................................................9
3.1.3. Expected outputs & Pass/Fail Criteria...........................................................................9
3.1.4. Test Procedure...............................................................................................................9
Bibliography..................................................................................................................................12
APPENDIX A. TEST LOGS.........................................................................................................14
A.1. Log for test 1......................................................................................................................14
A.1.1. Test Results.................................................................................................................15
A.1.2. Incident Report...........................................................................................................17

2
SOFTWARE TESTING
Introduction
System Overview
The development of eStage application has been done to manage online backstage as well
as designing of application has been done in a manner so that selection of role of every
stakeholder in relation with the backstage management can be done. The user has to login into
the system. This logging in can be done by selection of roles and also passing the authentication
mechanism to use different features provided by system. After achieving a successful login, user
is then redirected to welcome page as well as different links needs to be provided by various
users. The user has the liberty to select various kinds of options like logoff, home, competitors,
sections and discipline. The user can gather all different kinds of processes by selection of
appropriate option, then make a decision to use it appropriately. The registration process can also
be done by competitors in case of information system with all details as well as different
functionality can be provided. For example, the competitor can be moved by the stage manager,
withdrawn or change their sequence. The judgements or the results can also be put into the
information system by process of login, then entering the scores as well as the results to manage
the information and also automatically distribute the competitor’s results.
Test Approach
To proceed with the software application testing, various kind of approach needs to be
evaluated so that the best approach can be selected. The best approach for testing purposes of
online system for backstage management selection will occur. The drawbacks of this project
requires to be identified to analyse scope as well as objective for this project. The preparation of
test document is done by following testing on developed information system.

3
SOFTWARE TESTING
Unit Testing – This testing is being performed so that three codes can be verified as well as
program logistics development can take place and also it can be compared to that of the current
framework structure. This testing is only performed at the ending or the last stage so that errors
as well as bugs can be removed from the final product.
Integration Testing – This testing has been used to test the functionality of this software product
that has been developed, this is done by segregating the software into various modules as well
as integrating it altogether. to find it's compatibility with respect to others. To go forward with
the testing of system integration, it requires evaluation in various platforms so that it can be run
on the various hardware as well as software configuration,
Business requirement – This testing is done by for the management software for online
backstage. it needs to be done, so that verification for need of software could be met. This will
help in reduction of errors in final product which has been developed to manage information as
well as functionality by this organization. This software product needs alignment with that of the
business requirement as well as different criteria that needs to be met by the information system.
the system requires evaluation so that defects presents in final software can be detected.
Designing of different test cases is important and also test results needs documentation for
meeting future troubleshooting problems. This will improve efficiency as well as efficacy of the
system.
User acceptance testing – To perform this testing a group of friendly users are required who will
aid in information system testing. The primary objective of this testing is involvement in
information system testing as well as analysis of information system usability. The final
product’s interface needs to be developed. this should be done so that in future the user faces no
difficulty for understanding various function as well as the information flow from one part of the