Software Test Documentation

This document provides an overview of the software testing process for the eStage application, including the system overview, test approach, test plan, test cases, and traceability matrix. It also includes information on the functional and non-functional requirements of the system, testing tools and environment, and a bibliography.

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

4
SOFTWARE TESTING
system to another. This also helps in identification as well as minimization of errors. The users
could be main participants for testing of user’s acceptance for whom this information system
have been targeted towards along with developing various different test cases.
The following are the resources identified for the development of online backstage management
system
RoleRole Responsibilities Resource Name(s)
System Tester  Create a plan for testing activity
 Test case execution
 Project report execution and error
identification
 Identify effort needed for testing software
 Test result analysis
Software
Developer
 To analyze the requirement and develop the
software
 Cooperation with the testing team and provide
feedback against the system functionality
 Knowledge sharing and expertise sharing for
the development of the application
 Error acceptance and resolving immediately
System Analyst  Interviewing users
 Requirement development for the business
 Development of test case scenario and test
cases
User  Review and describing business requirement
 Describing and review user profile
 Acceptance test of the customer
Administrator  System application installation
 Software and hardware troubleshooting
 Information gathering about the system

5
SOFTWARE TESTING
TEST PLAN
Features to be tested
All certificates which were used to develop various functionality as well as samples of data
inputs have to be tested. All artifacts which needs to be thoroughly tested have to be included
into test plan so as to manage this information system. Documentation strategy of high level have
to be utilized along with development of traceability matrix in order to identify output as well as
input of this information system. All modules related with stakeholders who are involved in this
system have to be developed on individual basic and test should be done integration of system
modules in order to identify errors which might have occurred while developing the system.
Features not to be tested
All security features which have been implemented in information system should refrain from
testing as it has been not included with management of configuration along with viewing control
of information system. The risk related with information system is to be avoided while securing
this network solution from any unauthorized access.
Functional and Non-Functional Requirement of the System:
This system of the online backstage management consisting various of functional and
non-functional requirements. In the following section this functional and non-functional
requirement of the system is discussed.
Functional Requirement:
The admin of the user must be able to execute the following requirement which are
important for the system.
1. Adding User: Admin must be able to add new user to the system.

6
SOFTWARE TESTING
2. Data Update: Admin must be able to update the information system.
3. Deleting User: Admin must be able to delete existing users of the system.
4. Inquiry Members: Admin must be able to view the details of the current enrolled users to
the system.
5. Inquiry Issuance: Admin of the system must be able to inquiry about all the information
stored in the database.
6. Information Checking: Admin must be able to check any type of issue with the
information.
7. User Permission: Admin will be able to grant or deny any type of requests of the users.
8. Information Protection: Admin of the system must be able protect any type of
information in the database from the users.
9. Adding Nodes: Admin must be able to add new node to the system.
10. Deleting Nodes: Admin must be able to delete existing node of the system.
Non-Functional Requirement:
1. Database Safety: Database can crash due to various of reasons including manual errors
and virus attack. Thus backup of the database must be taken regularly.
2. Quality of the Software: The utilized software in this case must be user friendly so that all
of the users can use this system without any type of problem.
3. Hardware Constrains: Sufficient hardware must be used, so that it can handle all of the
operation of the database.
Testing tools and environment
The selection of test tools has to be done to detect any unknown fault. These tools should be able
to meet features which have been listed below:

7
SOFTWARE TESTING
● Program codes monitoring, be it full or partial should be including the following:
o The use of instruction set stimulators to provide permission for monitoring of
instruction level along with providing trace facility.
o The animations of programs as well as permission to provide execution through
step by step. Conditional breakpoint should also be implemented at source level
as well as machine code.
o Code report should also be covered.
● Formatted dump or symbolic debugging along with allowing inspections of several
programs to identify errors for chosen point.
● Using benchmark to compare run time performances.
● Performances should be analyzed to highlight hotspots along with usage of several
resources.
Traceability Matrix
REQUIREMENTS TRACEABILITY MATRIX
Project Name: Testing of OBMS Estage Application
Business
Requirements Doc
Functional Specification Doc Test
Case
Doc
Business
Requirem
Business
Requirem
Functiona
l
Functional
Requirement / Use
Priorit Test
Case
Executi
on
Defec

8
SOFTWARE TESTING
ent ID# ent /
Business
Use case
Requirem
ent ID#
Case y ID# Status t#
BR_1 Reservati
on
Module
FR_1 One Way booking
of tickets
High TC#0
1
TC#0
2
pass
FR_2 Two way booking
of ticket
TC#0
3
TC#0
4
pass
FR_3 Multiple booking of
tickets
High TC#0
5
TC#0
6
Fail Defec
t#
4623
BR_2 Payment
Module
FR_4 using Payment
Gateway
High TC#0
07
TC#0
08
pass
FR_5 using Credit points High TC#0
9
pass
FR_6 using Netbanking Mediu
m
TC#1
0
pass

9
SOFTWARE TESTING
TC#1
1
TEST CASES
Case 1
TC-1 Use Case- Login
3.1.1. Purpose
These tests are performed so that users would not face errors during the time of logging in the
system.
3.1.2. Inputs
Dropdown list have to be utilized for selecting the users and also to input the passwords to
logging in the system while using information system to manage backstage program.
3.1.3. Expected outputs & Pass/Fail Criteria
The users have to login in the information system after which it would be redirected in welcome
page which is there for this information system. Different responsibility as well as roles should
be the driving force to use this information system by its users. After this, they could even be
redirected to certain specific links which would depend entirely on user’s responsibility and
roles.
3.1.4. Test Procedure
To design test plans, the components of information systems has to be divided in various
components along with defining the various testing procedures. These testing has to be divided
in Non-functional and Functional testing. For developing specific methodology various

10
SOFTWARE TESTING
methodologies have to be followed along with proceeding with test plans. The performance as
well as scalability of information system have to be identified in order to test security constraints.
The failures as well as defects have to be identified while also considering performance,
usability, security and maintainability of this information system as even a minute defect
information system could cause failure in information system.
The identification of faults should be done while developing information system while fixing the
faults in order to review the requirements. To test the final software, a summary has to be created
while including various functionalities of components so that all the related quality issues could
also be identified in final software.
Gantt Chart
Budget
Task Name Duration Start Finish Cost
Testing of Online
backstage
management
development process
35 days Mon
05/20/19 Fri 07/05/19 $3,050.00

11
SOFTWARE TESTING
Completing the test
plan 5 days Mon
05/20/19 Fri 05/24/19 $1,200.00
Preparing the testing
environment 5 days Mon
05/27/19 Fri 05/31/19 $500.00
Record and
executing test cases 7 days Mon
06/03/19
Tue
06/11/19 $500.00
Submitting errors
and tracking the
system modification
5 days Wed
06/12/19
Tue
06/18/19 $250.00
Integration testing 6 days Wed
06/19/19
Wed
06/26/19 $500.00
Report to Test
Engineer 1 days Thu
06/27/19
Thu
06/27/19 $50.00
Report to Test
Manager 1 days Fri 06/28/19 Fri 06/28/19 $50.00
Client acceptance 5 days Sat 06/29/19 Fri 07/05/19 $0.00

12
SOFTWARE TESTING
Bibliography
Aleti, A., Moser, I., & Grunske, L. (2017). Analysing the fitness landscape of search-based
software testing problems. Automated Software Engineering, 24(3), 603-621.
Arcuri, A. (2018). An experience report on applying software testing academic results in
industry: We need usable automated test generation. Empirical Software
Engineering, 23(4), 1959-1981.
Beyer, D. (2019, April). International competition on software testing (Test-Comp).
In International Conference on Tools and Algorithms for the Construction and Analysis
of Systems (pp. 167-175). Springer, Cham.
Böhme, M., & Paul, S. (2015). A probabilistic analysis of the efficiency of automated software
testing. IEEE Transactions on Software Engineering, 42(4), 345-360.
Briand, L., Nejati, S., Sabetzadeh, M., & Bianculli, D. (2016, May). Testing the untestable:
model testing of complex software-intensive systems. In Proceedings of the 38th
international conference on software engineering companion(pp. 789-792). ACM.
Considine, C., Crowley, S., Gardner, G., Shannon, C., Kwinn, M. J., Henderson, S. J., &
Santamaria, P. (2016, April). Architecting a development and testing plan for the Army's
common operating environment: Applying agile systems of systems development to army
network acquisition. In Systems Conference (SysCon), 2016 Annual IEEE (pp. 1-6).
IEEE.
Garousi, V., & Mäntylä, M. V. (2016). When and what to automate in software testing? A multi-
vocal literature review. Information and Software Technology, 76, 92-117.

13
SOFTWARE TESTING
Hass, A. M. (2014). Guide to advanced software testing. Artech House.
Leicht, N., Blohm, I., & Leimeister, J. M. (2017). Leveraging the power of the crowd for
software testing. IEEE Software, 34(2), 62-69.
Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.
Schultz, J. L. (2015). Software Testing Guide to Ensure Effective and Efficient Health
Information Technology Testing (Doctoral dissertation, The College of St. Scholastica).
Sharma, C., Sabharwal, S., & Sibal, R. (2014). A survey on software testing techniques using
genetic algorithm. arXiv preprint arXiv:1411.1154.

14
SOFTWARE TESTING
APPENDIX A. TEST LOGS
A.1. Log for test 1
Task Artifacts Projected
Completion
Completing the test
plan
Test Plan document Version
1.0
14/05/2019
Preparing the
testing environment
Hardware and software
elements
21/05/2019
Record and
executing test cases
Collection of artefacts,
Documentation of test plan and
documenting test results
28/05/2019
Submitting errors
and tracking the
system modification
Documenting unit Test Results 04/06/2019
Integration testing Preparing the Test Plan
Document v 1.0
11/06/2019
Client acceptance Test Plan Document V 1.0 17/06/2019
A.1.1. Test Results
Test Use Description Result

15
SOFTWARE TESTING
Case Case
ID
TC-1 UC-1 The dropdown list and the
user is needed to be
selected from dropdown
option.
The validation checking is done by
comparing the password and
username of the user
TC-2 UC-2 Editing the information
residing in the
information system
selecting profile for
modifying and updating
data in the information
system
A message is popped out after the
completion of the update and
asking for confirmation from the
user.
TC-3 UC-3 The system is needed to
be rebooted and the user
should have the option to
manage the nodes
connected in the network
such that the list of nodes
are generated.
A message is popped out after
completing the reboot process and
status of the machine is needed to
be shared with the user for the
management of different
functionality
TC-4 UC-4 Management of addition
and deletion option is
A message is popped after
successfully creating the user

16
SOFTWARE TESTING
necessary by the
administrator for
controlling different
operation.
profile
TC-5 UC-5 Addition/ Modification
and Deletion option is
needed to be present in
the system such that the
administrator can easily
manage the system
A confirmation is displayed to the
administrator for a second step
verification about the user input
TC-6 UC-6 The option for listing the
nodes connected in the
network and the
information system is
needed to be listed for
management of the nodes
A message shown listing the nodes
and they are grouped according to
the functionality
TC-7 UC-7 User menu and different
options available for
managing the profiles are
needed to be managed for
the backstage
management
The username and their details are
listed with their types and
functionality

17
SOFTWARE TESTING
A.1.2. Incident Report
For performing the test, the test personnel are needed to be involved and a notification is needed
to be generated for the following needs:
● Generating notification for the software development team such that the errors are
eliminated
● Testing rules are defined for the other personnel
● Generating notification for the individual for performing usability test
An incident report is generated for the director and the directors are notified with the means
of email and the contact information is needed to be embedded in the report along with the
details given below:
● Contact information of the test team
● Description of the incident
● Effort status and determining the incident cause.