Software Testing Report for ITECH 7409: Online Backstage System

This report provides a comprehensive overview of the software testing process for an online backstage management system (eStage). It includes an introduction to the system, outlining its purpose and functionality, followed by a detailed test plan covering features to be tested and excluded, testing tools and environment, and a traceability matrix. The report presents specific test cases, including login functionality, profile updates, and module reboots, along with expected outputs and pass/fail criteria. A project schedule, Gantt chart, and budget are included to provide a holistic view of the testing effort. The testing approach incorporates unit testing, integration testing, business requirement testing, and user acceptance testing to ensure software quality and user satisfaction. The document is designed to meet the requirements of ITECH 7409 Software Testing course.

Running head: SOFTWARE TESTING
ITECH 7409 Software Testing
Name of the Student
Name of the University
Authors 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..................................................................................................................7
3.1. Case 1........................................................................................................................7
4. Schedule of the project..................................................................................................11
5. Gantt Chart.....................................................................................................................12
6. Budget............................................................................................................................12
Conclusion.........................................................................................................................15
Bibliography......................................................................................................................16

2
SOFTWARE TESTING
1. Introduction
1.1. System Overview
The application of eStage is created for the online backstage management system. The
main design of the system includes role selection of every stakeholders which is related with the
online backstage management system. Users are able to login to the information system by the
selection of roles and passing it to the mechanism of authentication for using all the functionality
of the system. In this system several of options can be selected by the user. Detailed regarding all
the processes can be fetched by the user by selection of all the options appropriately.
Competitors can register to the information system by providing appropriate details of them.
Then several functionalities will be provided to the users with having different types of roles.
Judgment results can be stored within the information system providing scores to the system and
for that login to the system is required.
1.2. Test Approach
Software testing is a complex process and there are different issues that are often
encountered during the testing process. When testing of the software is not proper it affects the
quality of the software, therefore, it is very important to identify proper software testing
methodologies to ensure that software testing is of high quality and it enhances the quality of the
software as well.
Unit testing – unit testing is an important aspect of software testing. It helps in verifying
the associated codes and the logic that has been considered for developing the program for the
software and compare it with the existing structure of the software framework. This testing is

3
SOFTWARE TESTING
done after the development of the software is completed and helps in identifying any issues or
bugs that might effect the security and performance of the software.
Integration testing – the purpose of the integration testing is to analyze the functionality
that has been integrated with the software productive developed in the project. In this testing fast
the software is divided into models and each module is developed separately. Once the
development of those models are completed they are integrated to produce the complete version
of the software. In integration testing compatibility of one module is tested with other modules of
the software so that there is no compatibility issues in the software product. One important aspect
of integration testing is to analyze the performance of the software on different platform so that
the software has no performance issues because of different hardware and software
configuration.
Business requirement – when the software product is developed it is important to identify
if requirement specified by the client has been made or not. Business requirement testing help in
analyzing whether business requirements have been effectively integrated or not. In order to do
this different testing case required to be designed and test the software according to those test
cases. Here in this context the main focus is too execute the test process and document the result
in the testing so that it is easier for the client to manage their information for which the software
is developed.
User acceptance testing – interface of the software is very important as it decide how
effective interruption of the user with the software is if user find it difficult to use the software
due to lack of proper interface then the software development is not successful in order to
identify whether the interface of the software is proper or not a group of user are invited and they
are asked to test the interstate of the software and profile there opinion according to their

4
SOFTWARE TESTING
experience with the software therefore the main application of user acceptance testing is to
analyse the interface and overall experience of using the software from user perspective so that
any issues with the software identified and create a user friendly software so that the final
software that is delivered to the client has no usability issues.
2. TEST PLAN
2.1. Features to be tested
Certificates that are associated with the software development should be tested in the
testing process along with that data samples of the software need to be tested as well the testing
plan should include the important artefacts that are considered for developing the software high-
level plan for the documentation should be developed which needs to be followed by design of a
traceability matrix that helps in documenting issues regarding the software testing process. The
modules that are associated with the stakeholders need to be integrated with the testing process
during the system integration for identifying errors and issues in the system for enhancing the
quality and security of the software to ensure stakeholder satisfaction in this project.
2.2. Features not to be tested
The security of the system is not included in the testing plan as this is not associated with
the management control and information access of the system. However, it should be ensured
that the information system is not accessible without proper authentication and it should require
to login to the system for accessing information.
2.3. Testing tools and environment
Whether performing full or partial monitoring for the software testing, it needs to
consider the following aspects which are important for the testing process:

5
SOFTWARE TESTING
 Simulation of the instruction set that is required to provide permission for executing
monitoring at instruction level
 Program animation and deployment of conditional breakpoint at source level
 Symbolic debugging for identifying and analysing issues with the software
 Development of performance benchmark for analysing and comparing performance of a
specific module chosen for the software testing process
 Performance analysis for identifying hotspots and resource consumption of the software
2.4. Traceability Matrix
Role Responsibilities Name of the resource
System testers Testing activities Planning
Execution of the testing plan
The task report evaluation
Measurement of the exertion
measurement needed for the
product testing
Examination of the after effects
associated with the test
Tester_1
Tester_2
Tester_1
Tester_3
Tester_2
System developers To develop program according
to the consumer requirement
Analyse framework and provide
Developer_1

6
SOFTWARE TESTING
review of the framework and its
application in the testing
process
Sharing testing information
Recognize issues and resolve it
without delay
Developer_2
Developer_1
Developer_1
System analysts Interview with the consumers
Prerequisite created required for
the business
Creation of test situation
created for improving the
accuracy of the experiment
Analyst_1
Analyst_1
Analyst_2
Users Explanation and assessing the
requirement as identified for the
business
Analyzing and describing the
profile that is associated with
the client
Acknowledging the testing
process of the client
User_1
User_2

7
SOFTWARE TESTING
User_3
Administrators Installing the framework
required for the application
Identifying the issues with the
equipment and the product
through troubleshooting
Collect data regarding the
framework on which the
software is running
Admin_1
Admin_1
Admin_2
3. TEST CASES
3.1. Case 1
3.1. Case 1
Tc-1 use case- login
3.1.1. Purpose
The purpose of the testing is to ensure there is no error while users are trying to login to the
system for accessing its various functionalities.
3.1.2. Inputs
The users need to select the dropdown menu and from there they need to select the login option.
After that they should provide correct username and password to login into the system.

8
SOFTWARE TESTING
3.1.3. Expected outputs &pass/fail criteria
After the user is successfully logged in to the system, the system should redirect the user to
welcome page where a welcome message is shown to the user after the login is successful. The
system should allow the user to access various functionalities base on their roles and
responsibility that the information system integrate. Once a role is selected by the user, the
system should redirect them to an appropriate link that is associated with that role.
There should be no mismatch between the role selected and the link that the system redirects the
users to for ensuring that the system performs accurately according to the requirements.
3.1.4. Test procedure
In order to ensure that the testing process is effective and of standard quality, the information
system should be divided into various modules and each of these modules required to be testing
separately so that it is possible to identify issues with the system and thus it is easier to modify
those issues as well. Each of the component should be tested with equal priority and this include
testing for software usability, performance and maintainability aspect as well as security aspect
of the software. Issues in one module has a significant impact on the overall performance of the
software.
The testing procedure is described in details in this context:
Use case id Description
Uc_1 Login module
Uc_2 Update profile module
Uc_3 Reboot module

9
SOFTWARE TESTING
Uc_4 Add or delete user module
Uc_5 Add or delete node module
Uc_6 Power up module
The test case is provided in the above table and the description of the test case is provided
in the following table:
Test case Use case id Description Result
Tc-1 Uc-1 The user from the
dropdown list require to
select the role
The username and the
password authentication
is tested, system access
granted
Tc-2 Uc-2 Information from the
system is edited and
updated view for profile
selection provided
A pop up message is
displayed on successfully
updating the system and
ask the user for
confirming and returning
back to the profile page of
the user.
Tc-3 Uc-3 The reboot option
clicked and the
A pop up message
generated after

10
SOFTWARE TESTING
associated nodes that are
linked with system
provided as a list of
nodes
completion of rebooting
after which the machine is
ready to control different
programs.
Tc-4 Uc-4 It is require to manage
add and delete action for
the system so that data is
added and deleted by the
system properly
A pop up message
displayed which confirms
successful creation of the
user
Tc-5 Uc-5 Admin after clicking on
nodes button required to
choose add/delete node
option
Confirmation screen is
exhibited which verifies
addition and deletion of
nodes successfully
Tc-6 Uc-6 Admin clicks on the red
power button after
clicking on the nodes
button, after listing of
the node buttons
A message is showed on
startup and the button
colour becomes green for
providing confirmation
for the activity
Tc-7 Uc-7 Admin select the account
option for listing user
menus which is
associated with the
Users list created with
their name and the types.

11
SOFTWARE TESTING
online back stage
management system
4. Schedule of the project
Task Activity Completion date
Creating the test plan for the
project
Document for test plan
version 1.0
13/05/2019
Designing the test environment Hardware and software
components
20/05/2019
Documenting and executing of
the test case
Collection, document for test
plan version 1.0, test result
document
27/05/2019
Analysis of the errors and
tracking the changes in the
plan that needs to be executed
Unit testing results document 03/05/2019
Integration testing Document for test plan v 1.0 10/05/2019
Project acceptance Document for test plan v 1.0 17/05/2019

12
SOFTWARE TESTING
5. Gantt Chart
6. Budget
Tas
k Name
Durat
ion
St
art
Fini
sh
Predecess
ors
Cost
Testi
ng OBMS
Estage
Application
138
days
Tu
e 28-05-19
Thu
05-12-19
$25,800
.00
Re
quirement
analysis and
Specificatio
n
12
days
Tu
e 28-05-19
We
d 12-06-19
$1,000.
00
De
velopment
3 days Th
u 13-06-
Mo
n 17-06-19
1 $750.00

13
SOFTWARE TESTING
of
traceability
Matrix
19
De
velopment
of test Case
25
days
Tu
e 18-06-19
Mo
n 22-07-19
2 $1,800.
00
Te
st case
review
7 days Tu
e 23-07-19
We
d 31-07-19
3 $450.00
Int
egrating
review
comment
for each of
the test case
7 days Th
u 01-08-
19
Fri
09-08-19
4 $300.00
Ste
p execution
for the test
cases
7 days M
on 12-08-
19
Tue
20-08-19
5 $350.00
Ide
ntifying the
status as
Pass or Fail
7 days W
ed 21-08-
19
Thu
29-08-19
6 $450.00

14
SOFTWARE TESTING
Ide
ntify the
cause of
failure of
the test case
30
days
Fri
30-08-19
Thu
10-10-19
7 $1,800.
00
Se
nding status
of test to the
team lead
on daily
basis
20
days
Fri
11-10-19
Thu
07-11-19
8 $17,800
.00
Te
st case
execution
completed
for the test
cases
20
days
Fri
08-11-19
Thu
05-12-19
9 $1,100.
00
Conclusion
Software testing has an essential role in quality software development. It helps in
identifying issues regarding the software and resolve this issues before the final version of the
software is delivered to the client. Now quality software testing should be well planned and
specific strategies are required to be followed. The fast requirement of software testing is to
design a software testing plan. Once the plane is developed and approved the actual testing

15
SOFTWARE TESTING
process needs to be executed. The result and issues identified in the testing process should be
documented and a test log should be prepared in this context. The next and final step of the
testing process is to prepare a synopsis report the main objective of this testing process is to
deliver requirements which are specified in the testing plan and the result and findings should be
presented in a logical way so that those results are quantifiable and measurable. This steps are
required to be followed in proper sequence ensure quality software testing process required to
deliver quality software to the client that is consistent with business requirement as specified
during the software development project.

16
SOFTWARE TESTING
Bibliography
Dalal, S., & Hooda, S. (2018). ASPECT-ORIENTED SOFTWARE TESTING TECHNIQUES:
A REVIEW. International Journal of Advanced Research in Computer Science, 9(2),
211.
Garcia, B. (2017). Mastering Software Testing with JUnit 5: Comprehensive guide to develop
high quality Java applications. Packt Publishing Ltd.
Garousi, V., & Mäntylä, M. V. (2016). A systematic literature review of literature reviews in
software testing. Information and Software Technology, 80, 195-216.
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.
Giacomozzi, C., & Martelli, F. (2017). Health software: a new CEI Guide for software
management in medical environment. Annali dell'Istituto superiore di sanita, 52(4), 524-
529. Sadath, L., & Nair, R. (2019, April). Oncological Inspired Techniques for Intelligent
Software Testing. In 2019 Amity International Conference on Artificial Intelligence
(AICAI) (pp. 327-333). IEEE.
Hambling, B., Thompson, G., Williams, P., Samaroo, A., & Morgan, P. (2015). Software testing:
an ISTQB-BCS certified tester foundation guide. BCS Learning & Development.
Houston, S. M. (2017). Software Testing. In The Project Manager's Guide to Health Information
Technology Implementation (pp. 77-86). Productivity Press.
Melo, S. M., de Souza, S. D. R. S., de Souza, P. S. L., & Carver, J. C. (2017, October). How to
test your concurrent software: an approach for the selection of testing techniques.

17
SOFTWARE TESTING
In Proceedings of the 4th ACM SIGPLAN International Workshop on Software
Engineering for Parallel Systems (pp. 42-43). ACM.
Rosero, R. H., Gómez, O. S., & Rodríguez, G. (2016). 15 years of software regression testing
techniques—A survey. International Journal of Software Engineering and Knowledge
Engineering, 26(05), 675-689.
Sethi, A., 2017. A Review Paper On Levels, Types & Techniques in Software
Testing. International Journal of Advanced Research in Computer Science, 8(7).
Shinner, M., Matthews, E. F., & Goldblum, B. L. (2019). FIER: Software for Analytical
Modeling of Delayed Gamma-Ray Spectra Installation Guide and Reference
Manual. University of California, Berkeley.
Wang, S., Ali, S., Yue, T., Li, Y., & Liaaen, M. (2016, May). A practical guide to select quality
indicators for assessing pareto-based search algorithms in search-based software
engineering. In 2016 IEEE/ACM 38th International Conference on Software Engineering
(ICSE) (pp. 631-642). IEEE.