Software Testing: Design, Execution & Analysis

The assignment presents a detailed examination of a software testing project. It outlines the stages involved in the testing process, from initial planning and design to execution and final analysis. The document includes descriptions of various testing methodologies, test plans, reports on testing outcomes, and a comprehensive conclusion summarizing the effectiveness of the testing approach used.

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
a. Main purpose of the test...............................................................................................2
b. Main objectives of the test...........................................................................................2
2. Project Scope...................................................................................................................3
3. Project resources..............................................................................................................4
4. Test Plan with the inclusion of the traceability matrix....................................................5
a. Test Plan design...........................................................................................................5
b. Test Cases....................................................................................................................7
Conclusion.........................................................................................................................10
Bibliography......................................................................................................................11

2
SOFTWARE TESTING
1. Introduction
A test plan is created for the testing the online backstage management system and
different testing strategy is used for the preparation of the project test plan. The unit is described
and the integration of the system with the different levels is important for testing of the system.
A traceability matrix is created for recording the test results. The main purpose of the software
testing is to test the functionality of the system and resolve the errors for increasing the
efficiency of the system.
a. Main purpose of the test
The functionality of the system is required to be analyzed and tested for reviewing the
test case of the system
i. The prerequisite of the task and the data that exists for the advancement of the
undertaking.
ii. Analysis of the business prerequisite and the exchange that are required to be
fundamentally tried.
iii. Strategies and the sorts of testing is required to be chosen for the usage of the testing
design
iv. A testing plan is required to be set up for the correct working of the testing design and
help to build up a quality final result.
b. Main objectives of the test
The report is set up to go about as a base stage for testing the online backstage
administration framework. The principle destinations of the task is to investigate that the project

3
SOFTWARE TESTING
meets the prerequisite of the undertaking and the archive should go about as a rule for the testing
group for testing the usefulness of the framework that are installed as a practical module. The
test archive likewise assesses the nature of the last form item and diminish the quantity of
blunders in the framework.
2. Project Scope
In this area the diverse degree for the advancement of the online backstage administration
framework are examined regarding the in scope and the out extension things.
The fundamental extent of the testing design is that the product is tried in a PC with intel
i5 3rd generation processor and 4 GB Ram. The accompanying tests are done, for example, unit
testing, framework incorporation testing, framework testing and lastly acknowledgment testing.
For playing out each of the test one week time is taken and along these lines the aggregate testing
technique proceeds for 1 month. For proceeding with the test the following areas are tested and
are listed below:
 The login approval of the administrator
 Adding or erasing new client for the framework
 Controlling diverse nodes
 Real time update of the profile of the client
 Add or erasure of the nodes
The execution of the product relies upon the equipment and the stage where it runs and
along these lines it is out of extent of the undertaking. The group of PCs where the product is
focused to run is additionally kept out of degree for testing the product.

4
SOFTWARE TESTING
3. Project resources
The accompanying table is made for appointing roles and duty to the assets associated
with testing of the product application "Online Backstage administration System".
RoleRole Responsibilities Name of the
Resource
System Testers  Planning for the exercises to be tried
 Execution of the experiments
 Evaluation of the task report and ID of the
mistakes in the project
 Measurement of the exertion required to be
connected in the product testing
 Analysis of the after effects of the test.
 Tester_1
 Tester_2
 Tester_1
 Tester_3
 Tester_2
System Developers  To build up the product as per the necessity of
the customer
 Cooperate with the framework analyzer and
give input in regards to the usefulness of the
framework.
 Share information and the aptitude for the
application they created
 Accept the blunders and resolve it promptly
 Developer_1
 Developer_2
 Developer_1
 Developer_1
System Analysts  Interview the clients
 Creation of prerequisite for the business
 Creation of test situation and improvement of
the experiment
 Analyst_1
 Analyst_1
 Analyst_2
Users  Description and evaluating the necessity of
the business
 Reviewing and depicting the profile of the
client
 Testing the acknowledgment of the client
 User_1
 User_2
 User_3
Administrators  Installation of the framework application
 Trouble shooting the equipment and the
product
 Gather data in regards to the framework
where it is running
 Admin_1
 Admin_1
 Admin_2

5
SOFTWARE TESTING
4. Test Plan with the inclusion of the traceability matrix
a. Test Plan design
There are distinctive sorts of test designs, for example, master test design, testing level
particular test design and testing sort particular test design. A project scope is required to be
created for including the risk associated with the development of the project and the test is done
during the preparation of the test plan. The testing level particular test design is taken after for
the readiness of the test report of the online backstage administration framework.
1. Unit Testing- The test is done to check the rationale of the program which is contrasted
and the structure of the program and the learning of the testing group. As a client, unit
testing is not something you will discover in a last outcome it's a sort of testing
performed in the midst of the coding stage. The testing group can just discover that a
potential designer that is utilized uses unit testing in the midst of the progression stage to
ensure your thing has diminished steady bugs.
2. Integration Testing- The whole framework is considered for testing and the usefulness of
the framework is tried by the proposed plan and the detail of the undertaking. The
distinctive segments and the modules made for adding usefulness to the online backstage
administration framework is required to be coordinated and tried for appropriate working
of the entire framework. The framework mix testing is required to be done on different
stage with the end goal that the readied application should chip away at all stages.
3. Business necessity- The test is done to check the prerequisite of the client and meet the
business necessity and increment the productivity of the online backstage administration
framework. The product item created is required to be broke down as indicated by the
business necessity and diverse criteria for playing out the test is required to be produced

6
SOFTWARE TESTING
for testing the usefulness of the framework. The experiment is required to be outlined and
the aftereffects of the test is required to be checked for following and dealing with the
deformities of the last programming item.
4. User acknowledgment testing- The test is required to be performed by a gathering of
cordial client and the destinations of this testing is that the client desire is required to be
met. It is the last period of the testing and it is performed before propelling the product in
the market. The principle focus for playing out the client acknowledgment testing is
approval of the conclusion to end stream of the business. The client acknowledgment test
condition is isolated from the ordinary test condition and the members of the client
acknowledgment testing are the customer and the focused on end clients.
The previously mentioned tests are performed by making an experiment. The
experiments are created and appeared in the table underneath:
Use case
ID
Description
UC_1 Login module
UC_2 Update Profile module
UC_3 Reboot module
UC_4 Add or delete user module
UC_5 Add or Delete node module
UC_6 Power up module

7
SOFTWARE TESTING
b. Test Cases
Test Case
ID
Description
Test_001 Login module
Test_002 Update Profile module
Test_003 Reboot module
Test_004 Add or delete user module
Test_005 Add or Delete node module
Test_006 Power up module
The test case is defined in the above table and the following table is created for adding
the description of the test case and the use case along with the results.
Test
Case
Use
Case
ID
Description Result
Test_00
1
UC_1 The client is required to
enter a username and
password in the
information system
The validation of the username and
the password is checked and the
client is allowed to get to the
framework
Test_00
2
UC_2 The data dwelling in the
data framework is altered
and the view is refreshed
A fly up message is shown on
effectively refreshing the
framework and approach the client

8
SOFTWARE TESTING
for determination of the
profile segment of the
client
for affirming and returning back to
the profile page of the client.
Test_00
3
UC_3 The reboot alternative is
required to be clicked and
the hubs connected with
framework ought to be
recorded as a hub list.
A fly up message is required to be
created in the wake of rebooting is
done and status of the machine
winds up noticeably prepared for
taking care of various projects.
Test_00
4
UC_4 Include and erase choice
is required to be overseen
by the framework
administrator and control
the operation of the
clients.
A fly up message shows up when a
client account is created
successfully
Test_00
5
UC_5 Administrator taps on
hubs catch and chooses
include/erase hub choice
Affirmation screen is shown
checking that the nodes are
included/erased
Test_00
6
UC_6 Administrator taps the
hubs catch, once the hubs
are recorded, taps on the
Red power catch
A message is shown on startup and
button is activated
Test_00 UC_7 To list the client menus A dropdown list of the clients are

9
SOFTWARE TESTING
7 the administrator can tap
on the records choice put
in the online back stage
administration
framework.
produced with their name and the
sorts.
5. Schedule of the project
Task Activity Completion Date
Creation of the
project test plan
Test Plan document
Version 1.0
13/08/2017
Development of the
test environment
Hardware and software
elements
20/08/2017
Recording and
execution of the test
case
Collection, Test Plan
Document version 1.0, Test
Result Document
27/08/2017
Analysis of the
errors and tracking
the changes in the
plan to be enforced
Unit Testing Results
Document
03/08/2017
Integration testing Test Plan Document V 10/09/2017

10
SOFTWARE TESTING
Task Activity Completion Date
1.0
Project acceptance Test Plan Document V
1.0
17/09/2017
Conclusion
For the making of the test design distinctive advances are required to be taken after, for
example, the depiction of the test plan which is additionally separated into portrayal of the test
strategy and depiction of the experiment. The subsequent stage is the execution of the testing and
putting away the occurrence of the report and make a test log. The last advance is the making of
a synopsis test report. The principle objectives of the report are to fulfill necessities that are
portrayed in the test design and introduce a quantifiable, reasonable and repeatable testing
technique. The different usefulness of the segments of the present variant of the product are
assessed and the mistakes happening in the framework are settled for advancement of a quality
programming item.

11
SOFTWARE TESTING
Bibliography
Böhme, M., & Paul, S. (2016). A probabilistic analysis of the efficiency of automated software
testing. IEEE Transactions on Software Engineering, 42(4), 345-360.
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.
Hass, A. M. (2014). Guide to advanced software testing. Artech House.
Jorgensen, P. C. (2016). Software testing: a craftsman’s approach. CRC press.
Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.
Lewis, W. E. (2016). Software testing and continuous quality improvement. CRC press.
Mathur, A. P. (2013). Foundations of Software Testing, 2/e. Pearson Education India.
opencodez. (2017). 4 steps to create Requirement Traceability Matrix (RTM) - Free Sample to
download - opencodez. [online] Available at: http://www.opencodez.com/software-
testing/create-requirement-traceability-matrix-rtm-free-sample-download.htm [Accessed
26 Sep. 2017].
Schultz, J. L. (2015). Software Testing Guide to Ensure Effective and Efficient Health
Information Technology Testing (Doctoral dissertation, The College of St. Scholastica).

12
SOFTWARE TESTING
Sharma, C., Sabharwal, S., & Sibal, R. (2014). A survey on software testing techniques using
genetic algorithm. arXiv preprint arXiv:1411.1154.
Sharma, C., Sabharwal, S., & Sibal, R. (2014). A survey on software testing techniques using
genetic algorithm. arXiv preprint arXiv:1411.1154.
Traceability matrix – Scripting Logic. (2017). Scriptinglogic.com. Retrieved 26 September 2017,
from http://scriptinglogic.com/software-testing/manual-testing/traceability-matrix/