Software Testing: Test Plan, Test Scenario, Test Case, Traceability Matrix

This article discusses software testing and its various aspects such as test plan, test scenario, test case, and traceability matrix. It also covers required hardware and software, testing tools, and more. The article is relevant for ITECH 7409 Software Testing course at any college or university.

ASSIGNMENT
OF
ITECH 7409 SOFTWARE TESTING
ACKNOWLEDGEMENT
1

We wish to express our sincere gratitude to our respected teacher for given us the
opportunity to undertake our project.
We also like to thank our mentors and friends for their kind co-operation and
encouragement with which we able to complete our project.
TABLE OF CONTENTS
2

INTRODUCTION…………………..………………………………………………………….. 4
TEST PLAN…………...……………………………………………………………………….. 4
TEST SCENARIO……………………….…………………………………………………….. 4
TEST CASE…………….……………………………………………………………………… 4
TRACEABILITY MATRIX…………………………………………………………………… 5
MASTER TEST PLAN…………..…………………………………………………………….. 5
TEST SCOPE……………………...…………………………………………………………… 5
TESTING CONFIGURATION MATRIX…………………………………………………….. 5
REQUIRED SOFTWARE AND HARDWARE……………………...……………………….. 6
TESTING PREPARATION……...……………………………………………………………. 6
LEVEL TEST PLAN……………………………….………………………………………….. 6
TEST CLASSES AND OVERAL TEST CONDITION………………….…………………… 6
TEST ITEMS AND IDENTIFIERS…………………………………………………………… 7
SOFTWARE TESTING TOOLS……………………………………………………………… 7
CONCLUSION………………………………………………………………………………… 8
References……………………………………………………………………………………… 9
3

1 Introduction
In online backstage management system RSSS Royal South Street Software are used to
build the application. The RSSS gives organization support to run the application. It mainly used
for competition activities regarding testing. The goal of OBMS is to mainly reduce the problems
and also the data are improved by the dynamic process. It seems like paper based system by the
user but it actually transfers information from wireless to modules
It may include test plan, test case, development, operation, etc. The documentation
involves the artifacts of the testing activities that have been developed before the software. This
helps to estimate the requirements for testing, coverage of testing, and tracing. This description
includes the artifacts such as test scenario, test case, traceability matrix etc.
SOLUTION
2 Test plan
4

Test plan are used to test the outline of the application that ensure the current strategy, it
includes use of resources, testing environment, testing activities that are scheduled, testing
limitations. The responsibility of the test plan is to give the quality assurance.
3 Test Scenario
Test scenario are applied from one end to another end to ensure correct behavior of the
process. We can apply more than one test scenario in some specified location because it may
require repetitive execution. They may produce different results when we apply test cases. The
test scenario and test case have major difference, In test scenario it contains many step for its
execution but in the case of test case it has only one step that are used as interchange. From the
developer or users perspective, test scenario are the test cases, it also provides many test case and
flow, that should be executed. The output are depends upon previous output.
4 Test Case
Test case usually refers set of conditions that should be executed to satisfy the
requirements correctly. These test cases can help to find defects and problems in the system or
application. Then the tester will perform appropriate actions to remove the defects in the system.
Then only tester can ensure the correct behavior of the system.
5 Traceability Matrix
Traceability matrix also called as requirement traceability matrix. It is a table in software
development life cycle are used to trace the requirements. In forward and backward tracing are
also used. In traceability matrix defined templates are used. The test case are linked with each of
the RTM document requirements. It also include the Bug ID and requirements that are linked
with the test case. The purpose of the matrix is to check whether it is matched with given
requirements or not, find the bug from the root causes, SDLC has different phases that have to
trace document during in this development.
Requirements Module name Application names Description
5

1 Registration User The user must give the data for
registration.
2 Login Logon, logout,
Authentication
The register user can login with the
system they the gives the user name
and password.
3 Files as
imported
User Admin The user can open the file that
needed files in the system.
6 Master Test Plan
This is used to define the outline of the test plan, it must be approved and reviewed by the
representative of the technical and project representative of the business. During the execution
any changes are common to test plan and the project of the testing phase must be update and re
produced the parties.
EFFORTS OF UNIT TEST PLAN
Business
requirements
Module name Members Efforts
1 Competitor Tester 3 hrs
2 Login Tester 2 hrs
3 Import file Tester 1 hrs
SCHEDULE FOR INTEGRATION
Business
requirements
System Schedule on status
1 Print reports 28-05-2018 Complete
2 Examine results 28-05-2018 Scheduled
3 Backup 29-05-2018 complete
6

7 Test Scope
The main scope of the project is used to provide the description at high level for the
business process. And it also includes what should be tested and the testing type that we have to
apply. Master test plan is the main part of the testing. Each application has focus on the thing
which has been described and test the features. The stakeholder of the information are provided
in this part and show the testing activities what they should be done about product of project and
can give the feedback about developer and the suggestions, engineers etc.
8 Testing Configuration Matrix
It have number of configuration and platforms that are need to support the application,
and the configuration have to be collaborate with the testing matrix. The project must have
different thing for configuration. For example in one project it may have browsers and windows
and in other project it may have components and the required version may have the correct
function. By the configuration we have shown the environment of the configuration by the
parameter of the work. If the configuration has supported officially, it may look like more
expensive by other system.
9 Required Hardware and software
By the scope of testing and the configurations needed for the test, it requires resources of
hardware and software to complete the test. The software licenses have to include for the testing
and also for virtual users they need to load and test the performance. We can ask the simulator
and stubs in this place that may be require for testing.
10 Testing preparations
In this phase we make preparation that needed for testing and then we can do the test. It
have high review for every test plan and to compare the scope of the testing. In testing they have
many levels and stages that should be divided among operations. That may provide the
information about expected time lines and the criteria about entry and exit point.
11 Level Test Plan
In level test plan they specify the goals, requirements and the activities for a particular
testing. In many of the project, they have many levels for testing that needs several resources
7

from functions. By preparing separate plan for different process is the good result of the level
test plan. It may have many test plans with respect to levels that required for the documentation
usage and to list the contents.
12 Test Classes and Overall Test Conditions
In this category, it recall the particular test level that has specified nature. It defines the
basic scope. For example this particular level provide the required description as follows.
1. The attributes of the desired test have to analyze each and every component.
2. The integration test have to exercise the interfaces and the invention.
3. The requirements must focus the goal of the test.
4. Acceptance test has the attributes of the focus.
13 Test items and identifiers
It identifies the items and process that should be tested under testing activities It also
identify the procedure which we can perform when certain processes are transferred from one
environment to other.
It provide the requirements of the testing activities that practice with the test levels by the
current test cases and test procedure.
14 Software testing tools
In today’s environment, there are plenty of software testing tools are available. But its very
difficult to determine best software tools for our project.
There are several categories available on testing tools. Some of them given below,
1. Test management tools
2. Load testing tools
3. Automated testing tools
4. Defect tracking tools
5. Mobile testing tools
8

6. API Testing tools
7. Security testing tools
Test management tools help for end to end test cycle
Best example for test management tool was Complete
It mainly used for enterprise level applications. And also working with methodologies like
agile and devops (modern development methodologies). It can be used to identify high risk
issues.
Load testing tools helps to test application or test based on its performance.
Good example for automated testing tools was Squish
It is the GUI test automation tools. More than 3000 companies prefer this kind of
automation tool for testing their applications. It also called cross-platform tool. Its support all
major GUI technologies. Its support major platforms like desktop, mobile, web and embedded
platforms. Selenium also another best example for automated testing tools.
15 Conclusion
In online backstage management system testing is the major part. In the process of testing
activities, several types of testing available to detect the error and also to correct the software. By
this report, the OBMS has tested using various testing schedule, efforts of unit testing and
traceability matrix that are user provided.
In this document we describe the testing objectives and approaches for the testing. It
includes the master test plan, level test plan etc. software documentation is the major part of the
development. After the code implementation there are various documentation available for each
process.
9

References
Al-Zahrani, B. (2016). Reliability test plan based on Dagum distribution. International Journal
Of Advanced Statistics And Probability, 4(1), 75. doi: 10.14419/ijasp.v4i1.6165
Chen, Y. (2015). SPR as solution of action plan in China's master plan innovation. Habitat
International, 50, 300-309. doi: 10.1016/j.habitatint.2015.08.001
Ebola master plan unveiled. (2014). New Scientist, 223(2977), 4. doi: 10.1016/s0262-
4079(14)61322-1
10

Franker, K., & James, D. (2016). The Course Development Plan: Macro-Level Decisions and
Micro-Level Processes. New Directions For Higher Education, 2016(173), 43-53. doi:
10.1002/he.20178
Hilton Sydney Floor Plan - Level 3. (2014). Asia-Pacific Journal Of Clinical Oncology, 10, 11-
11. doi: 10.1111/ajco.12236_3
Lee, Y. (2011). A test plan to measure metamaterial performances. Adelphi, MD: Army
Research Laboratory.
Maksymova, I. (2017). Master plan geospatial profile data set model analysis. Sciencerise, 7(0),
48-53. doi: 10.15587/2313-8416.2017.106679
United States. National Nuclear Security Administration. (2013). Test plan. Washington, D.C.
Whittaker, J. (2012). The 10-Minute Test Plan. IEEE Software, 29(6), 70-77. doi:
10.1109/ms.2012.25
Whittaker, J. (2012). The 10-Minute Test Plan. IEEE Software, 29(6), 70-77. doi:
10.1109/ms.2012.25
11