Software Testing: Software Test Documentation Report - University Name

This software test documentation provides a detailed overview of the eStage application's testing process. It includes an introduction to the system, outlining its features and the test approach. The document presents a comprehensive test plan, specifying features to be tested, those excluded, the testing environment, and a traceability matrix. It then details four test cases, each with purpose, inputs, expected outputs, and procedures. These cases cover login, profile updates, module reboots, and user management. The report also incorporates a Gantt chart and budget allocation for the testing phase, along with test results and an incident report, culminating in a conclusion and bibliography. The document adheres to software testing best practices and documentation standards.

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.

4
SOFTWARE TESTING
Business requirement –
The backstage management online software needs to be tested as verification process is
necessary to meet the solution as well as reduction of errors in final or end product. This
software product that has been developed for information management as well as
functionality which the organization requires from the product. It is very important that the
final end product, i.e the software is properly aligned to the requirements of the business.
Apart from that various criteria needs to be met by this information system which requires
evaluation as well as testing software defects. There is a requirement thus to meet the various
test cases as well as test results needs documentation so that in future the information can be
used efficiently for increasing the performance of the system involved in this project.
User acceptance testing – The user acceptance testing needs to be done with the help of some
users who already know about this system and is able to test its usability, at the same time
giving a proper analysis. The final product’s interface needs development so that user does
not encounter problems while accessing the multitude of functions as well as end-to-end
information flow needs rectification for efficient working of system. All main participants of
users acceptance testing’s could be users toward whom whole information system is being
targeted while developing various test cases.
2. TEST PLAN
2.1. Features to be tested
The several certificates which were utilised for developing samples as well as functionalities
of data outputs is to be tested. Various artifacts which needs to be efficiently tested should
also be included into test plan to manage this information system. Documentation strategy of
very high level is to be used while also developing traceability matrix to identify output as
well as all inputs of this information system. Stakeholders modules which are involved into

5
SOFTWARE TESTING
system is also to be individually developed and should be tested while integration of several
system modules on order to identify errors while developing systems.
2.2. Features not to be tested
The several security features which were implemented in information system is to be avoided
to be tested as they are not included into management of configurations while viewing several
controls in this information system. The several risks associated with information system
should also not considered while securing network from any unauthroised access by intruder.
2.3. Testing tools and environment
The test tools is to be selected to detect several faults that may be there in the information
system while tools should be meeting following features which are given below:
● Full or partial monitoring of program codes which should be including the following:
o The simulator in instruction set is used to provide permissions to monitor in
instructional level while also providing trace facilities.
o Animation of several permissions as well as programs to provide
implementation and execution of conditional breakpoints in source level along
with machine code.
o Code report should also be covered.
● Formatted dump or symbolic debugging along with allowing inspections of programs
to identify several errors for any chosen points.
● Benchmark which might be used to compare performance run time.

6
SOFTWARE TESTING
● Performance analysis to highlight hotspots along with resource usage which also
should be highlighted.
2.4. Traceability Matrix
Role Responsibilities Name of the
Resource
System Testers ✔ Planning the exercises that is to given a trial
✔ Execution of experiment
✔ Evaluation of tasks report, IDs of several
mistakes which are there in project
✔ Measurement of exertions which is required
to connect into product testing
✔ Analysis of several aftereffects of these tests.
● Tester_1
● Tester_2
● Tester_1
● Tester_3
● Tester_2
System Developers ✔ To build the products as per necessities of
customers
✔ Cooperate with frameworks analyzers along
with giving inputs in regards with the
usefulness of this framework.
✔ Share information’s as well as aptitude for
several applications they have created
✔ Accept the related blunders along with
resolving it promptly
● Developer_1
● Developer_2
● Developer_1
● Developer_1
System Analysts ✔ Interview all the clients available
✔ Creation of the prerequisite for running
business
✔ Creation of several test situations while
improving the experiments
● Analyst_1
● Analyst_1
● Analyst_2
Users ✔ Description along with evaluation are
necessities of businesses.
✔ Reviewing as well as depicting profiles of
clients
● User_1

7
SOFTWARE TESTING
✔ Testing several acknowledgment made by
client
● User_2
● User_3
Administrators ✔ Installing the framework applications
✔ Troubleshooting products as well as the
equipment’s.
✔ data gathering of framework where ever it
may be running.
● Admin_1
● Admin_1
● Admin_2
3. TEST CASES
3.1. Case 1
TC-1 Use Case- Login
3.1.1. Purpose
The testing is done considering no errors is face by users in the time of logging information
system.
3.1.2. Inputs
Dropdown list is utilized to select the users while input the related password to log in the
system, utilizing information system to manage backstage programs
3.1.3. Expected outputs & Pass/Fail Criteria
Information system should be logged in by users while redirecting them to welcome page in
the information systems. various roles are utilized to be used by users in this information
system and they should be redirected toward various separate links which depends on
responsibility and roles of these users.

8
SOFTWARE TESTING
3.1.4. Test Procedure
To design test plans, several components which are there in information system is to be
divided in various components while defining procedures of testing. The main test has to be
bifurcated in non-functional as well as functional testing’s. Various methodology has been
followed to develop specific methodology while proceeding with test plans. The performance
as well as scalability of information system is to be identified to test several security
constraints. The various failures as well as defects has to be identified while considering
performance, usability, maintainability and securities of information system. System defects
could also cause failures in information system.
3.2. Case 2
TC-2 Use Case- Update Profile
3.2.1. Purpose
The test is performed for identifying the problems faced during login and editing the
information available in the information system.
3.2.2. Inputs
The edit option is used for editing or modifying the information that is previously inputted by
the user and updating the system with latest information.
3.2.3. Expected outputs & Pass/Fail Criteria
A confirmation message is needed to be displayed before performing the final update and
they are needed to be redirected for updating the information.
3.2.4. Test Procedure
The test plan is performed by involving different users and modifying the data with valid and
invalid data for identifying the performance of the information system against the different

9
SOFTWARE TESTING
set of data. The result of the output of the query is needed to be tested with different data and
different methodology is used for modification and updating the data.
3.3. Case 3
TC-3 Use Case- Reboot Module
3.3.1. Purpose
The testing is done for identifying that all the features and functional modules gets
automatically started after performing the reboot.
3.3.2. Inputs
The reboot option is needed to be available to the admin and no other users of the information
system should not be able to reboot the system.
3.3.3. Expected outputs & Pass/Fail Criteria
After performing the reboot the admin and the other user needed to re login with their
username and password for getting access of their portal.
3.3.4. Test Procedure
The reboot is made from the admin account and all the functionality of the system is tested
for identifying that the functional modules starts automatically and it is done multiple times
such that positive result is obtained all the times.
3.4. Case 4
TC-4 Use Case- Add/Delete User
3.4.1. Purpose
New volunteers can be hired for the management of the system and thus for the management
of the information they are needed to be registered with the information system and new

10
SOFTWARE TESTING
accounts are needed to be created. In case any of the stakeholders leaves their account is
needed to be deleted such that they cannot have access of the information system.
3.4.2. Inputs
The admin account should have the functionality of creating new account and management of
the existing account such that the information system is balanced with users and old user
information are needed to be deleted such that the information system are secured from
external agents. An unique user name is needed to be inputted with the details of the roles and
functionality for creating the new account.
3.1.3. Expected outputs & Pass/Fail Criteria
IF the username already exists the new account cannot be created and an error message is
displayed for using unique username. The forgotten name is needed to be recovered and this
option is unavailable and the functionality is needed to be added.
3.1.4. Test Procedure
New account is opened with unique username and password and same names are tried for
opening another account. The error message is received and the files are created under each
of the account. On deleting the account, it is tried to keep the files and archive it as backup
and old files.
Experiment is conducted to perform tests which are mentioned previously. The results of
experiment have been written below.
Use case ID Description
UC_1 Login module
UC_2 Update Profile module

11
SOFTWARE TESTING
UC_3 Reboot module
UC_4 Add or delete user module
UC_5 Add or Delete node module
UC_6 Power up module
The several test cases have been defined in above as well as following tables has been created
to add test case description along with use case and result.
Test
Case
Use
Case
ID
Description Result
TC-1 UC-1 Dropdown list is to be
utilized for selecting role
of users.
The validation of password and
username is checked while granting
user to have access of system.